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.
Overview
With the right workflow setup, you can go from a company being added to a list all the way to having fully enriched contacts created in your CRM automatically. This is done by chaining together a series of actions that handle enrichment, organization creation, and contact creation in sequence.
The workflow described in this article follows this logic:
A trigger fires when a company meets a set condition (e.g., added to a list)
The company is enriched to find associated contacts
A CRM organization is created for the company
Contacts are retrieved from the company's custom fields
Those contacts are created in your CRM
How the Workflow Works
Trigger — Company Added to a List
The workflow starts when a defined event occurs — for example, when a company is added to a specific list. This is what sets the automation in motion.
You can use any supported trigger that fits your use case, such as a company entering a list based on a filter or being manually added.
Action 1 — Enrich Company
Once the trigger fires, the first action enriches the company. During this step, the system identifies 1–5 contacts associated with the company and stores them in a custom field on the company record.
These contacts are held in the custom field and passed forward to later steps in the workflow.
For example: "Use the prompt 'Find marketing decision makers' and save the found contacts to the custom field "Marketing Decision Makers".
Please note: The contacts found during enrichment are stored in the company's custom fields. They are not yet created in your CRM at this stage — this happens in a later action.
Action 2 — Create CRM Organization
Next, the workflow creates the company as an Organization in your CRM using your configured Outgoing Field Mapping.
If the company is already connected to a CRM entity, this step is automatically skipped preventing duplicate organizations from being created.
Please note: Make sure your Outgoing Field Mapping is set up before running this workflow. This determines which company fields are sent to your CRM. For more information, see Customize the Information Sent to Your CRM article.
Action 3 — Get Contacts from Company Custom Fields
This action retrieves the contacts that were stored during the Enrich Company step. It reads directly from the company's custom fields at the point the workflow is triggered.
This step acts as the bridge between enrichment and CRM contact creation; it prepares the contact data so it can be passed to the final action. I.e. the workflow passes information from one place to another, in a company workflow, that information is the company. WIth this action step number 3 we are passing the contact rather than the company.
Action 4 — Create Contact in CRM
Finally, the workflow creates each contact in your CRM using the data retrieved in the previous step.
This means that by the end of the workflow, your CRM will have:
The company created as an Organization (or skipped if already connected)
Up to 5 contacts created and linked to that Organization
Workflow Summary
Step | Action | What Happens |
Trigger | Company added to list | Workflow is initiated |
Action 1 | Enrich Company | Contacts found and stored in custom fields |
Action 2 | Create CRM Organization | Company created in CRM (skipped if already connected) |
Action 3 | Get Contacts from Custom Fields | Contacts retrieved from custom fields (see CRM integrations for more information) |
Action 4 | Create Contact in CRM | Each contact is created in your CRM |
Things to Keep in Mind
Your CRM must be connected before running this workflow. If no integration is active, the CRM actions will not execute.
Outgoing Field Mapping for your CRM must be configured to control what data is sent to the CRM Organization.
The Enrich Company step returns contacts depending on the data available. If no contacts are found, subsequent contact-creation steps will not run.
This workflow is designed to avoid creating duplicates, so if a company is already linked to a CRM entity, the Create CRM Organization step is skipped automatically.
--
Questions, comments, feedback? Please let us know by contacting our support team via the chat or by sending us an email at support@leadfeeder.com.