Release Status | Coming Soon | Availability | Free |
Status Page | Autopilot Status Page | Default Historical Sync | 1 year |
Whitelist Tables/Columns | Unsupported/Unsupported | Default Replication Frequency | 30 minutes |
Full Table Endpoints | 4 | Incremental Endpoints | 0 |
Destination Incompatibilities | None |
Connecting Autopilot
Connecting your Autopilot data to Stitch is a four-step process:
- Retrieve your Autopilot API Key
- Add Autopilot as a Stitch Data Source
- Define the Historical Sync
- Define the Replication Frequency
Retrieving Your Autopilot API Key
- Sign into your Autopilot account.
- Click the gear (Settings) icon on the left side of the page.
- In the Settings menu, click Autopilot API.
- If you haven’t used the API before, you’ll need to generate a new key. Click the Generate button.
- Your API Key will display.
Make sure you keep this key safe, as it has access to your Autopilot account. If at any time your key is lost or compromised, you can click the Regenerate button to generate a new key. Remember to also update the key in Stitch or you’ll encounter connection issues.
Add Autopilot as a Stitch Data Source
- On the Stitch Dashboard page, click the Add an Integration button.
-
Click the Autopilot icon.
-
Enter a name for the integration. This is the name that will display on the for the integration; it’ll also be used to create the schema in your data warehouse.
For example, the name “Stitch Autopilot” would create a schema called
stitch_Autopilot
in the data warehouse. This schema is where all the tables for this integration will be stored. - In the API Key field, paste your Autopilot API Key.
Defining the Historical Sync
The Sync Historical Data setting will define the starting date for your Autopilot integration. This means that data equal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to sync data beyond Autopilot’s default setting of 1 year. For a detailed look at historical syncs, check out the Syncing Historical SaaS Data article.
Define the Replication Frequency
The Replication Frequency controls how often Stitch will attempt to replicate data from your Autopilot integration. By default the frequency is set to 30 minutes, but you can change it to better suit your needs.
Before setting the Replication Frequency, note that:
- The more often Autopilot is set to replicate, the higher the number of replicated rows.
-
The number of rows in the source may not equal the number of rows replicated by Stitch. Tables that use Full Table Replication will result in a higher number of replicated rows.
- If you’re using a data warehouses that doesn’t natively support nested structures, you’ll see a higher number of replicated rows due to the de-nesting Stitch performs.
To help prevent overages, we recommend setting the Replication Frequency to something less frequent - like 6 hours instead of 30 minutes. For tips on reducing your row count, check out the Reducing Your Row Count section of our Billing Guide.
After selecting a Replication Frequency, click Save Integration.
Autopilot’s Intial Sync
After you finish setting up Autopilot, you might see its Sync Status show as Pending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial sync for the integration. This may take some time to complete.
Autopilot Schema
Stitch's Autopilot integration includes these tables:
autopilot_contacts
Replication Method: Full Table
Primary Key: contact_id
Contains Nested Structures?:
Yes
autopilot_contacts
table contains about the contacts in your Autopilot account.autopilot_contacts & Nested Structures
This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.
These items are marked with a *
autopilot_contacts Attributes
While we try to include everything Autopilot has here, this may not be a full list of attributes. Refer to Autopilot's documentation for a full list and description of each attribute.
Contact ID (
contact_id
)First Name
Last Name
Company
Company Priority
Email Address
Employee Range (min/max)
First Conversion Time
First Visit Time
Industry
Lead Source
Mailing Address
Phone Number
Status
Title
Type
Unsubscribe details
Website
Created At
Updated At
autopilot_lists
Replication Method: Full Table
Primary Key: list_id
Contains Nested Structures?:
No
autopilot_lists
table contains about the available lists in your Autopilot account.autopilot_lists Attributes
While we try to include everything Autopilot has here, this may not be a full list of attributes. Refer to Autopilot's documentation for a full list and description of each attribute.
List ID (
list_id
)Title
autopilot_smart_segments
Replication Method: Full Table
Primary Key: segment_id
Contains Nested Structures?:
Yes
autopilot_smart_segments
table contains about the smart segments in your Autopilot account.autopilot_smart_segments & Nested Structures
This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.
These items are marked with a *
autopilot_smart_segments Attributes
While we try to include everything Autopilot has here, this may not be a full list of attributes. Refer to Autopilot's documentation for a full list and description of each attribute.
Segment ID (
segment_id
)Title
autopilot_smart_segments_contacts
Replication Method: Full Table
Primary Key: segment_id:contact_id
Contains Nested Structures?:
No
autopilot_smart_segments_contacts
table contains segment and contact pairs. In other words, the segments your contacts are associated with.autopilot_smart_segments_contacts Attributes
While we try to include everything Autopilot has here, this may not be a full list of attributes. Refer to Autopilot's documentation for a full list and description of each attribute.
Segment ID
Contact ID
Related | Troubleshooting |
Questions? Feedback?
Did this article help? If you have questions or feedback, please reach out to us.