This page provides you with instructions on how to extract data from Autopilot and load it into Snowflake. (If this manual process sounds onerous, check out Stitch, which can do all the heavy lifting for you in just a few clicks.)
Autopilot is a visual tool that allows marketers to track the customer journey of their prospects. Some of the information stored in Autopilot can be valuable input for business analytics, but getting the information into a data warehouse can be a chore.
Snowflake is a data warehouse solution that is entirely cloud based. It's a managed service. If you don't want to deal with hardware, software, or upkeep for a data warehouse you're going to love Snowflake. It runs on the wicked fast Amazon Web Services architecture using EC2 and S3 instances. Snowflake is designed to be flexible and easy to work with where other relational databases are not. One example of this is the query execution. Snowflake creates virtual warehouses where query processing takes place. These virtual warehouses run on separate compute clusters, so querying one of these virtual warehouses doesn't slow down the others. If you have ever had to wait for a query to complete, you know the value of speed and efficiency for query processing.
Getting data out of Autopilot
Autopilot exposes data through a REST API, which developers can use to extract information. Each API call must contain an API authentication key. To get the API key for your Autopilot account:
- Log in at https://login.autopilothq.com
- Go to Settings > Autopilot API
- Click "Generate"
- Copy the API key
You must use the API key in every method call, in a header called
Once you have an API key, you can use a GET method to retrieve data via the API. For example, to retrieve a batch of 100 contacts, call
The call returns a JSON object with two or three properties as a reply:
total_contacts: the total number of contacts
contacts: the current batch of 100 contacts
bookmark: if there are more contacts on the list, the bookmark allows you to access the next group of contacts via another GET call.
Each Autopilot contact may have any or all of 26 standard fields, along with any custom fields you may have defined.
Preparing data for Snowflake
Depending on the structure that you data is in, you may need to prepare it for loading. Take a look at the supported data types for Snowflake and make sure that the data you've got will map neatly to them. If you have a lot of data, you should compress it. Gzip, bzip2, Brotli, Zstandard v0.8 and deflate/raw deflate compression types are all supported.
One important thing to note here is that you don't need to define a schema in advance when loading JSON data into Snowflake. Onward to loading!
Loading data into Snowflake
Easier and faster alternatives
If all this sounds a bit overwhelming, don’t be alarmed. If you have all the skills necessary to go through this process, chances are building and maintaining a script like this isn’t a very high-leverage use of your time.
Thankfully, products like Stitch were built to solve this problem automatically. With just a few clicks, Stitch starts extracting your Autopilot data via the API, structuring it in a way that is optimized for analysis, and inserting that data into your Snowflake data warehouse.