This guide walks you through how to export personalized content and insights from Autobound to Salesforce. You’ll learn how to set up custom fields in Salesforce to store campaign data, run the export from Autobound, and configure downstream workflows for sequencing in other systems.
1. Set Up Custom Fields in Salesforce
To store personalized Autobound content (such as emails, call scripts, LinkedIn steps) in Salesforce, create custom fields on the Contact (and/or Lead) object. You'll want 1 custom field that will be used to designate which sequence to add contacts to, and 10 fields used for pushing content.
How to Create Custom Fields in Salesforce:
Navigate to Salesforce Setup:
Log in to Salesforce.
Click the gear icon (⚙️) in the top right and select Setup.
Find the Contact Object:
In the left sidebar, go to Object Manager.
Find and click on Contact (or Lead, if preferred).
Add a New Field:
In the Contact setup, go to Fields & Relationships.
Click New.
Select the Field Type:
Choose Text Area (Long)
Name the Field:
Set up your Campaign Name Field and call it "Autobound Campaign Name". Make it a Text Area field.
Set up your content fields:
Use a clear naming convention, such as:
Autobound Content 1 (Text Area)
Autobound Content 2 (Text Area)
Autobound Content 3 (Text Area)
Repeat up to 10.
Field-Level Security & Layout:
Set field visibility as needed and add each new field to your Contact (or Lead) page layout.
Tip:
Consistent naming and correct field types make mapping and downstream syncing much easier.
1.5 Exporting as a Lead vs. Contact (CSV Uploads Only)
By default, Autobound maps exported records to the Contact object in Salesforce. If you uploaded your contacts via CSV and want to export them as Leads instead, you need to include an sf_object column in your CSV before uploading it to Autobound.
How to set this up:
Open your CSV file before uploading it to Autobound.
Add a new column with the header
sf_objectPopulate every row in that column with the value
LeadUpload the CSV to Autobound and proceed with your campaign as normal.
When configuring your export mapping, map the
sf_objectfield to the corresponding Salesforce field.
Important: The sf_object column must be present in the original CSV at the time of upload. It cannot be added after the fact. If you uploaded without it and need to export as Leads, you will need to create a new campaign with a corrected CSV file.
Troubleshooting
"Salesforce default object field is set to Contact, but the workflow column is set to Lead" This error means the sf_object column was not included in the uploaded CSV. Create a new campaign using a CSV that includes the sf_object column populated with Lead.
Duplicate rule blocking Lead creation If your Salesforce org has a duplicate rule called Standard_Rule_for_Leads_with_Duplicate_Contacts active, it will block Lead creation when a matching Contact already exists. To fix it: go to Salesforce Setup > search for Duplicate Rules > find that rule > change the action from Block to Allow.
Note this is a global change, so flag it with your Salesforce admin before making it.
2. Set Up the Export in Autobound
In your Autobound campaign, click the Action button (top right) and select Export.
Choose Export to Salesforce and select your connected Salesforce account.
Map Autobound fields (e.g., step bodies, subjects, other insights) to the corresponding custom fields you created in Salesforce.
Make sure to also map email, which serves as the unique identifier so the correct Contact/Lead is updated.
Review all mappings to ensure every sequence step is assigned to the correct custom field.
Tip: For best formatting, map the HTML version of Autobound content when available.
3. Run the Export and Verify Data
Run the export in Autobound.
Autobound will push content and insights to the custom fields you created in Salesforce.
Go to a sample Contact/Lead in Salesforce and verify the data appears as expected in each custom field.
4. Syncing and Sequencing in Downstream Systems
Now that your personalized content is in Salesforce, you can push it to any connected platform that supports sequencing and is integrated with Salesforce (like Outreach, HubSpot, Marketo, or your own email engine).
Map Custom Fields to the Downstream System
When integrating Salesforce with another platform, make sure the custom fields you created in Salesforce (for each content step’s subject/body) are also mapped to fields in the downstream system.
This ensures Autobound’s content syncs and populates dynamically in your downstream sequence or cadence templates.
Create Sequence Templates in the Downstream System
In your downstream tool, set up sequence or cadence templates that insert dynamic field variables referencing the Salesforce custom fields (e.g.,
{autobound_content_1}for Salesforce merge fields).
Set Up Workflow Triggers for Automated Sending
Option 1: Trigger from Salesforce
Use Salesforce Flow or Process Builder to create a trigger: when any of the mapped custom fields are populated or updated by Autobound, the prospect is automatically added to the appropriate sequence in your downstream tool.
Option 2: Trigger from the Downstream System
Many platforms (like Outreach or HubSpot) let you set up triggers on their end—listening for changes to mapped custom fields from Salesforce and enrolling prospects in sequences automatically when those fields update.
Best Practice:
Keep owner/contact assignment fields in sync between Salesforce and the downstream system to ensure messages are sent from the right sender.
If the owner field isn’t already updated in your downstream platform, consider mapping the relevant user email field from Salesforce, and setting up an automation to assign the correct owner before sequencing.
Result:
With automation in place, prospects are automatically added to sequences in your downstream system, and your sequence templates will be populated with Autobound-generated content—assuming the variable fields are inserted correctly.
Tip:
To see how users set up workflow automation and downstream sequencing in Outreach and HubSpot—including field mapping and automated triggers—review these examples: