« Previously: Adding Steps to a Flow
Once you've cleansed and enriched your lead data, you'll want to deliver it to a recipient's email/file/system so it is actionable.
Whether you're delivering to a recipient's CRM/Marketing automation system, Email, Batch file, or some other custom HTTP endpoint, you'll need to connect the dots from LeadConduit to your destination for at least some of the data.
LeadConduit has Built-in Integrations with a variety of services that automatically map a basic set of standard fields. e.g. First Name, Last Name, Email, Phone, etc.
If you are collecting a more verbose set of data, or want to pass along information from the data enrichment services, you'll need to set up Outbound Field Mapping for that data, covered in the next section.
In the LeadConduit flow editor, you select the Integration to deliver to from the list of Add Recipient options.
- LeadConduit Account Holders
- LeadConduit Built-in Integrations
- Custom HTTP Recipients
LeadConduit Account Holders
Selecting a LeadConduit account holder from the list of Recipients will allow you to deliver leads from your flow to another account holder’s flow. Reach out to the account holder for the relevant Submission Docs.
LeadConduit Built-in Integrations
LeadConduit has Built-in Integrations with a variety of systems. The following example uses MailChimp's Add Member action, but the principles are the same with any Built-in Integration.
Select the Add a Recipient option in your flow. Scroll down past the Account and Custom recipients to find the list of available Integrations.
Once you select the MailChimp integration, you’ll be prompted to give this Recipient a name that you'll recognize for the specific purpose it is performing. You'll also want to note whether these leads are going to your account, or someone else's.
It is important to understand that Recipient describes the who or what is receiving this data (a client, an email list), and an Integration describes how you are sending this data - which integration you are using (HTTP POST integration, Salesforce integration, MailChimp integration, etc.).
Next, complete the integration setup. For MailChimp, this involves submitting your API Key and selecting the relevant list.
If you stopped right there, the Built-in Integration would automatically map and send the following fields from LeadConduit to MailChimp :
- First Name
- Last Name
- IP Address
Each Built-in Integration has a set of standard fields it will automatically map between LeadConduit and the Recipient. You can find the standard fields for the integration you are using at http://docs.leadconduit.com/
Once you've created this recipient, you'll have access to it in your drop-down menu as a custom recipient going forward. It will continue to use the MailChimp integration or whatever integration you've configured.
Outbound Field Mapping is covered in more detail in the next section.
Custom HTTP Recipients
LeadConduit won't always have a Built-In Integration for the Recipient receiving your leads. When that's the case, create a Custom HTTP Recipient.
From the Steps section of the flow editor, select Add Recipient. You can add a Custom Recipient on the initial screen.
Or at the bottom of the list of Recipients.
Select one of the custom HTTP recipient integrations from the drop-down menu. These integrations are indicated by a generic orange logo.
Once you've selected an integration, you'll need to use your Submission Docs to map the data from LeadConduit to the Destination (Outbound Field Mapping).
NOTE: Often the ActiveProspect team will get the Submission Docs from you during your onboarding project and configure the Custom Integration for you.
Next : Outbound Field Mapping »