Lesson 2: Connect Your Apps
Centralizing your tools in one place allows for better segmentation and more targeted marketing.
One of the best things you can do to set the foundation of success with Autopilot is to integrate all of your data sources and tools. This might include applications you’re using for analytics, customer relationship management, building landing pages, and other tools you’d like to connect with your automation software.
In this lesson, you’ll learn how to connect Autopilot with:
Connect Salesforce with Autopilot
Autopilot’s native integration with Salesforce CRM makes it easy to import Lead, Contact, and Account data in one click. You can choose to bi-directionally sync either a selection or all of your leads, contacts and accounts data as records. This means if you update a record in one system, it will automatically update in the other system.
Syncing with Salesforce CRM allows you to use the customer data within Salesforce in your segmentation as well as take advantage of built-in Salesforce triggers, actions, and conditions in your journeys.
For some inspiration on how to use Autopilot and Salesforce together, refer to these articles:
- 3 Must-Have Marketing Automation Journeys using Salesforce
- 9 Lead Nurturing Tips for Peeps Without a Fully Baked Sales Process
How to set up the Salesforce integration
Step 1. To connect Autopilot to Salesforce, access “Settings” > “Salesforce Sync”.
When prompted, log in to Salesforce. We recommend having a Salesforce administrator connect, as other roles may not have the necessary permissions.
Step 2. Configure your sync preferences. By default, Autopilot will sync all Salesforce Leads, Contacts, and Accounts. We recommend this because it gives you easy access to your entire Salesforce database in Autopilot.
However, if you’d prefer to only sync a selection of your Salesforce database, choose the “Selectively Sync Leads, Contacts and Accounts” option. For each object this allows you to:
- sync all records
- only sync records that meet your criteria (e.g. status is not “junk”) OR
- not sync any records
You can add multiple criteria using the “+” button. These criteria are joined by “AND”. For example, the criteria below would sync leads whose:
- status is open AND
- country is not Australia
You can put an OR between your criteria by using commas. For example, the criteria below would sync leads whose:
- status is open OR working AND
- country is not Australia
Autopilot will then sync with Salesforce every 10 minutes, checking for records that meet, or no longer meet, your criteria.
If you’re using selective sync, an important decision to consider is what should happen when a record no longer meets your sync criteria.
You can choose to either:
- Remove the record from Autopilot. In this case, the record will be permanently deleted from Autopilot and will stop progressing through any journeys they had been added to. If the record meets your sync criteria again in the future, they will be added as a new record in Autopilot and no data associated with the previously deleted record will be restored (e.g. history of the emails they had been sent).
- Keep the record in Autopilot. In this case, the record will remain in Autopilot, but will no longer be synced with Salesforce. This means that they will be removed from the Salesforce list they previously belonged to (e.g. the “Salesforce Leads” list). Use this option if you’d prefer to retain the record’s data in Autopilot (e.g. history of the emails they had been sent), and for them to continue to progress through any journeys they had been added to.
Finally, choose whether you want to customize your field mappings. By default, Autopilot will sync all standard Salesforce fields. However, if you have custom fields you’d like to sync, select “Custom field mappings”. Note that you can change your field mappings later.
You’ll then be given a preview of your sync preferences. After ensuring everything is correct, click “Sync with Salesforce”.
Once the sync is complete, you’ll see two new lists in the “Contacts” tab, which contain the Salesforce Leads and Contacts you chose to sync.
The Salesforce Accounts that you chose to sync (if any) will be available under the “All Companies” list.
Learn more about Autopilot’s contact and company records (and their Salesforce equivalents) here. For more information regarding Autopilot’s Salesforce integration and answers to frequently asked questions, refer to the Salesforce section of our Knowledge Base.
Use Zapier to connect your marketing stack
Zapier is a tool that allows you to easily connect and automate tasks between the apps you use, without the need for a developer. With 800+ integrated apps, including Autopilot, you can stitch together any tools in Zapier’s directory by creating a Zap.
A Zap combines triggers and actions from one application to another, like “contact added” or “unsubscribe contact”. For example, those not using Salesforce could make a Zap to automatically add contacts from another CRM to a list in Autopilot that acts as the trigger for a journey.
There are an infinite number of use cases using Autopilot and Zapier. Some of the apps we see connected most often include Pipedrive, Calendly, Eventbrite, GoToWebinar, Shopify, and LiveChat, for example.
Explore Autopilot’s Zapbook here. You can also check out how other Autopilot customers are using Zapier:
- Setting up a Webinar Using GoToWebinar, Instapage, and Autopilot
- How LiveChat Increased Email Engagement by 360%
- A Tool That Makes Sales More Efficient
How to connect Zapier
Much like Autopilot, there are triggers and actions within Zapier. Triggers define what causes the Zap to fire, while actions define what happens when the Zap fires. Below is a summary of all the triggers and actions available for Autopilot:
- Contact Removed From List
- Contact Unsubscribes
- Contact Added
- Contact Added to List
- Unsubscribe Contact
- Delete Contact
- Add Contact
- Add Contact to List
Each Zap configuration will be slightly different depending on the apps, triggers, and actions you choose. In this example, we’ve outlined how to leverage the “Add Contact” action.
Step 2. Click “Make a Zap” to build an automation from scratch.
Or click the button below to be guided through the setup step-by-step. For the sake of this example, we’ve chosen a Wufoo form.
Step 3. Choose a trigger app. Connect your Wufoo account and select the form you’d like to capture.
Step 4. For the action app, choose Autopilot.
In order to connect your Autopilot account, Zapier will then ask you for your Autopilot key. (Don’t worry. You will only need to do this the first time you set up a Zap with Autopilot.) To get this key, log in to Autopilot. Next, go to “Settings”, then “App Connections”, and finally click “Zapier”.
In this example, once you’ve turned the Zap on, Autopilot will automatically capture your form submissions and add them to your chosen list.
Autopilot uses email addresses to determine if contacts are the same. If they don’t yet exist in Autopilot’s contact database, they’ll be added as a new contact. If they’re already a contact, the existing record will be updated with any new information from the form submission.
Step 5. Once your Zap is live, you can trigger a journey based on newly synced data using smart segments or by adding contacts to a list. If you choose option two, be sure to configure the list trigger to add contacts who are added to the list in future.
For example, this journey sends an email to people who submit a Wufoo form:
Connect Segment with Autopilot
Segment helps you collect customer data and route it to hundreds of tools, including Salesforce, Optimizely, Mixpanel, and Autopilot.
Most Autopilot customers use Segment to track milestone moments within their application. For example, here at Autopilot we capture key events that signal user activation, like importing a spreadsheet, adding the tracking code, or publishing a journey. This behavioral data can then be used to trigger new journeys or influence a customer’s existing journey.
You can also push this data to analytics applications, such as Mixpanel or Heap, to easily graph in-product user behavior, track adoption, and identify where users are stagnating throughout their journey.
Learn more about how we use Segment at Autopilot.
How to connect Segment
Step 1. To connect Segment, navigate to “Settings” in Autopilot. Then, click Segment under “App Connections”:
Step 2. Once you’ve clicked “Connect to Segment”, you’ll be asked for the write key.
You can locate the write key in Segment under source settings. Go to “Workspace”, then “Select Main Source”, then “Settings”, then “API Keys”:
Copy the write key into Autopilot and click save.
Step 3. In Segment, under “Sources”, select “Integrations”, then search for Autopilot:
Once you’ve selected Autopilot, you will see a right side panel will pop up. Choose “Settings” in the panel.
Step 4. Configure the integration in Segment by clicking the “API Key” field. You will need to enter your API key.
After connecting to Segment in Autopilot, you can find the API Key here:
Step 5. Save, enable, and close the Segment integration.
Step 6. In order for Segment to work correctly and associate contacts into your database, you will need to configure your field mappings. To do this, click “Field Mappings” in “Settings” > Segment.
Important notes for mapping Segment fields to Autopilot
By default, we require an email address in the “Identify” field. This allows us to have at least one form of communication with the contact.
We also recommend including an email address in the “Track Events” field. This ensures that if we receive the “Identify” and the “Track Events” data out of order, we’ll know which contact to associate the event with.
Configure each Segment property to match the corresponding Autopilot field.
“Property” in this context is used as a general term for a “trait” in the case of an Identify and a “property” in the case of a Track. Track properties will always take priority if there’s a matching Track and Identify property.
It’s also important to note that your Segment property might be email_address as opposed to email. Check the event Identify traits before setting this up.
When you’re finished, remember to click “Update Field Mappings” on the right-hand side to save your changes.
Implementing an operational Segment journey
After connecting Segment to Autopilot and mapping your fields over, there is one last recommended step: creating an operational Segment journey to manage all of the Track Events you want to capture within Autopilot. Having one central place to make any necessary changes to your Segment integration is the main benefit of creating such a journey.
Until you’ve published these Segment triggers, we will not capture Track Events, so be sure to get this up and running!
Step 1. Understand which Track Events are important and what the expected behavior should be when someone takes that step.
In this example, we want to understand whenever someone:
- Logs into Autopilot
- Signs up for a free trial
- Publishes a journey
- Converts to a paying customer
To start, you can simply add contacts to a list or update a field. There doesn’t need to be any external action taken. This is about getting the information feeding into Autopilot so you have a foundation to build off of.
Step 2. Drag and drop the triggers onto the canvas, and configure each trigger using the appropriate Track Event.
Step 3. Because this journey is being used as a central hub, contacts should then be redirected to other journeys (e.g., to be nurtured), where other needed operational steps will happen.
To continue with the above example, once added to a list, our free trialists and new customers are added to different onboarding tracks. Those who have published a journey will have their total number of journeys incremented, plus one. Plus, the last login date will be updated for any users who log in.
Next, add the necessary shapes to the canvas and configure. Once you’re ready, publish and test to make sure everything has been captured correctly.
Now that you’ve configured the connection, follow these next steps:
Connect Slack with Autopilot
Slack is a platform for team communication. The integration with Autopilot makes it possible to add automated Slack notifications to any journey and, in turn, build better internal team alignment through transparency and real-time responses to customers in need. The possibilities are vast:
- Marketers can keep tabs on marketing performance and important milestones, such as new signups, asset downloads, website visits, or email clicks
- Sales teams can get notifications when hot leads are assigned or new customers make a purchase
- Support agents can collect customer feedback in real time and act quickly on new user challenges, such as customers failing to complete important milestones
- Product managers can focus on user adoption and product engagement by tracking key in-app events as they happen
Autopilot fully supports Slack’s styling, such as bolding text, adding emojis, or outputting images or GIFs—which makes rallying around the customer that much more fun.
How to connect Slack
Step 1. Within Autopilot, access “Settings” > “App Connections” > Slack.
Step 2. Click “Connect to Slack”, then follow the login steps on Slack’s website.
That’s it! Once connected, you can begin to use Slack notifications within your journeys. For tips and tricks on adding GIFs (as well as how to customize these messages), read through our knowledge base article here.
Connect Recurly with Autopilot
Recurly provides subscription management software for thousands of businesses worldwide. The Autopilot integration with Recurly allows you to track when someone makes a change to their subscription. You can create both internal and external process journeys to trigger when these updates are made.
How to connect Recurly
Step 1. Navigate to “Settings” > “App Connections” > Recurly.
Step 2. Copy the Webhook URL from within Autopilot, then open your Recurly account.
Step 3. In Recurly, click on “Webhooks” (which can be found on the bottom-left side of the navigation panel).
Step 4. Click “Configure” in the upper-right hand corner.
Step 5. Paste the webhook URL you copied from Autopilot, then click “Update Configuration”.
Step 6. Much like our Salesforce and Segment integrations, you will need to map the fields from Recurly to Autopilot. This can be done by clicking into the “Field Mappings” section within Autopilot under “Settings” > “App Connections” > Recurly.
Click “Add Field” to see the available Recurly fields. Next, determine where these fields will live within Autopilot.
As part of this process, you can create any custom fields that are needed. Just be sure to click “Update Recurly Mapping” before exiting to save any changes that are made.
Once complete, you can use the Recurly trigger to begin a journey.
This journey might build an internal process of notifying your team, place new customers in the appropriate onboarding journey, or even gather feedback when customers cancel. It’s up to you.
Connect Twilio with Autopilot
Twilio’s native integration with Autopilot allows you to send personalized SMS messages as easily as sending automated emails. All Autopilot plans include 250 text messages per month for free. To send text messages beyond the monthly limit, connect a custom Twilio account. By doing so, you’ll also benefit from advanced functionality, including:
- Control over the phone number your messages send from
- The ability to receive replies to your messages
- Direct access to Twilio’s delivery logs and their support team
How to connect Twilio
Step 1. Within Autopilot, access “Settings” > “App Connections” > Twillio. If you don’t yet have a Twilio account, create one here first.
Step 2. When you connect a Twilio account, you’ll be asked to provide your AccountSID and AuthToken.
Step 3. Once you’ve connected your account, you’ll need to select a phone number (from those you’ve purchased or ported to Twilio) for each send SMS action before publishing your journey.
To read more best practices and configuration tips, check out our knowledge base article on sending SMS messages.
Connect your app with the Autopilot API
The Autopilot REST API is another channel for updating your contacts with the most relevant information. It can also be used to trigger journeys off of key events.
Here are a few examples of how the API can be leveraged:
- Send leads from Autopilot into your own app
- Add contacts from your app into Autopilot
- Trigger Autopilot journeys from your app
- Keep unsubscribes synced between Autopilot and your app
- Add updates to Autopilot’s activity feed
- Enhance contact profiles with custom fields and other data from your app
- Get data from your app into and out of Salesforce using Autopilot’s deep integration
For information and documentation on how to configure the API integration, check out our developer documentation here.
Lesson 3: Centralize Your Contact Database
You’ve spent serious time and money acquiring contacts. Now let’s get them into Autopilot. You’ve built a contact database of thousands (or even millions) of contacts—leads collected from advertising, sales ...Go to next lesson