This is a Beta feature, you might not see this feature in your platform yet. Contact your CSM or our support team to learn more if you want to join the Beta.
Trigger | What it does | Key parameters |
Company Added to List | Starts the workflow when a company is added to a selected list. Runs once per company. Works with all lists you have access to, including system lists such as CRM Connected , CRM Possible Matches , and CRM Open Opportunities . | List |
Contact Added to List | Starts the workflow when a contact is added to a selected list. Runs once per contact. Works with all lists you have access to, including system lists such as CRM Connected and CRM Possible Matches . | List |
Scheduled – Daily | Runs once per day at a set time. | Time |
Scheduled – Weekly | Runs once per week on a set day. | Day of week, Time |
Scheduled – Monthly | Runs once per month on a set day. | Day of month, Time |
The workflow creator must have at least Viewer access to any list used in a trigger.
Actions for Companies
List Actions
Add Company to List – Adds the company to a list. Ignored if already present.
Remove Company from List – Removes the company from a list. Ignored if not present.
Move Company to Another List – Removes from source, adds to target. Always removes from source even if the company already exists on the target.
Lists are often part of broader automation strategies. Common examples include:
Adding a company from a Web Visitors feed into a list when it visits the pricing page, so it can be:
enriched,
scored,
used as an input for campaigns,
or pushed to your CRM.
Grouping companies that require manual follow-up by your sales or CS team.
Collecting companies that match a certain behavioral or scoring threshold for further processing.
All list actions require the workflow creator to have write access to the relevant list(s).
Tag Actions
Add Tag to Company – Applies a tag to the company. Ignored if the tag already exists.
Remove Tag from Company – Removes a tag from the company. Ignored if the tag doesn't exist.
Tags are ideal for lightweight classification, routing, and triggering further automation. Example use cases include:
Marking companies as “processed” after passing a certain workflow stage
Tagging accounts for team ownership, such as “EMEA team” or “US East”
Indicating companies that require follow‑up with tags like “review” or “needs attention”
Adding a tag that triggers another workflow or marketing automation step
Labeling companies entering a specific segment or behavioral pattern
Cleaning up temporary or processing‑related tags after a workflow completes
Removing qualification or disqualification tags when company status changes
Resetting tags before a new lifecycle or scoring process
Undoing previous tagging to avoid conflicting categorizations
Integration Actions
Send Company to Webhook – Posts the company as a JSON payload to an external endpoint. Useful for connecting to Make.com, n8n, internal tools, or custom pipelines. Payload format
Send Company to Slack – Posts a formatted company summary to a chosen Slack channel. Great for alerting sales or notifying teams about high-value matches. Can also be used to create lightweight collaboration workflows without needing a CRM integration
CRM Actions
Requires your CRM to be connected under Settings → Account → Integrations.
Create Company in CRM – Creates a new CRM record. Ignored if the company is already connected.
Set Custom Value on CRM Record – Updates a specific field on an existing CRM record. Runs only if the company is already connected.
Create CRM Task – Creates a task in the CRM assigned to a user or team.
Create CRM Opportunity – Creates a new opportunity linked to the company.
Typical use cases include:
Transferring calculated scores, e.g. fit score, intent score, or AI‑generated qualification
Updating custom fields based on workflow decisions
Synchronizing segmentation or lifecycle states with the CRM
Notifying sales to review a newly qualified lead
Creating reminder tasks based on company activity or scoring changes
Triggering manual review steps within automated processes
Automatically creating opportunities for high‑intent or high‑score leads
Starting pipeline tracking when key conditions are met (e.g., product demo requested)
Ensuring no qualified sales opportunity is missed due to manual delays
Data Actions
Enrich Company – Fills one or more custom fields on the company using AI-driven logic. Can generate scores, Yes/No values, text, numbers, or contact suggestions.
Configuration options:
Strategy: Always generate value (every execution workflow runs the enrichment), or only generate if the field is empty.
Custom Fields: Select existing fields or create new ones.
Each field can have its own enrichment logic depending on its type.
Common use cases: Lead scoring, company classification, finding relevant contacts, preparing data before CRM sync, and enabling downstream automation.
Tip: When using enrichment to find contacts, enable Find more contact details to optionally enrich those contacts with additional email addresses or phone numbers.
Actions for Contacts
List Actions
Add Contact to List – Adds the contact. Ignored if already present.
Remove Contact from List – Removes the contact. Ignored if not present.
Move Contact to Another List – Removes from source, adds to target.
All list actions require write access to the relevant list(s).
Integration Actions
Send Contact to Webhook – Sends the contact as a JSON payload to an external endpoint (Make.com, n8n, custom tools, etc.).
CRM Actions
Requires your CRM to be connected under Settings → Account → Integrations.
Create Contact in CRM – Creates a contact record. Ignored if already connected.
Set Custom Value on CRM Record – Updates a specific CRM field on a linked contact record.
Actions Without Input Data
These actions fetch or generate records rather than operating on an existing one. Typically used at the start of a workflow or in scheduled workflows.
Target Actions
Sync Saved Search to Company List – Keeps a company list in sync with a Target saved search. Adds new matches, removes those that no longer qualify.
Sync Saved Search to Contact List – Same concept for contacts.
We recommend syncing to a company list first, then using workflow enrichment to identify the right contacts. This produces cleaner, more targeted data.
List Actions (Record Retrieval)
Get a List of Companies – Loads companies from a list and feeds them into the workflow — one execution per company. Use a view to apply filters, sorting, and limits. Parameters: List name, View (optional), Number of records.
Get a List of Contacts – Same concept for contacts.
Use company lists as your primary structure and use enrichment to surface the best contacts from those companies.