Select contacts from list
Starts the workflow with the contacts already in one of your saved lists. It’s the most common starting point when you’ve already built the list you want to run a workflow against — through search, a CSV import, or manual curation.
Settings: List (required) — the list of contacts to start the workflow with.
Output: the list’s contacts, ready for the next step.
Select companies from list
Starts the workflow with the companies already in one of your saved lists. Use it the same way as its contact counterpart, for account-based workflows.
Settings: List (required) — the list of companies to start the workflow with.
Output: the list’s companies, ready for the next step.
Select contacts
Starts the workflow with contacts you pick manually, one by one, instead of a whole list. Good for quick one-off runs against a specific handful of contacts.
Settings: Contacts (required) — the specific contacts to start the workflow with.
Output: the selected contacts, ready for the next step.
Select companies
Starts the workflow with companies you pick manually, one by one, instead of a whole list. Good for quick one-off runs against a specific handful of companies.
Settings: Companies (required) — the specific companies to start the workflow with.
Output: the selected companies, ready for the next step.
Import contact
Creates (or matches, if one already exists) contacts from a contact payload — one object per contact, sent as a single object or an array of them, similar to a row in a CSV import. Each contact needs at minimum a LinkedIn URL, or a first name, last name, and company name. The resulting contacts flow into the next steps as if they had been selected.
Settings: Contact payload (required) — the contact data to create or match.
Output: the imported contacts, ready for the next step.
This step is auto-managed. It’s added automatically (and locked) when a webhook trigger declares a contact
payload input, and removed automatically if that input is removed. You can’t add or remove it manually.
Import company
Creates (or matches, if one already exists) companies from a company payload — one object per company, sent as a single object or an array of them, similar to a row in a CSV import. Each company needs at minimum a LinkedIn company URL or a company name. The resulting companies flow into the next steps as if they had been selected.
Settings: Company payload (required) — the company data to create or match.
Output: the imported companies, ready for the next step.
This step is auto-managed. It’s added automatically (and locked) when a webhook trigger declares a company
payload input, and removed automatically if that input is removed. You can’t add or remove it manually.