Skip to content
AI ⇄ CRM

Autopilot to Folk CRM integration — real-time, two-way sync

Keep Autopilot and Folk CRM in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Autopilot and Folk CRM

Write what Autopilot computes onto the contacts, accounts, and deals in Folk CRM, and feed Folk CRM's records back into Autopilot, in real time and in both directions.

Autopilot turns data into something a revenue team can act on: scores, classifications, summaries, and embeddings. But the customers those results describe live in Folk CRM, where reps and marketers actually work. Intelligence that stays inside Autopilot rarely reaches the record where a decision gets made, and Autopilot is only as sharp as the data it sees, which is also held in Folk CRM.

Stacksync connects Custom Fields, Smart Segments, Journeys (Triggers), Activities in Autopilot to Companies, Groups, Custom fields, Notes in Folk CRM with bi-directional, real-time sync. Records and fields from Folk CRM flow into Autopilot as the material it scores, indexes, or enriches, and the values Autopilot produces flow back onto the matching contact, account, or deal in Folk CRM, field by field, within seconds. There is no batch export in the middle and no glue code to maintain.

Because the mapping is field-level, you choose exactly which attributes cross and in which direction, so Folk CRM stays the record of the customer while Autopilot stays where the computation happens.

Common use cases

  • 01 Stream Activities into a warehouse so opens, clicks, and journey steps sit next to product and revenue data for lifecycle reporting.
  • 02 Upsert Contacts from a CRM or product database into Autopilot so new signups and profile changes flow into email and SMS journeys without manual CSV imports.
  • 03 Keep folk and a billing or customer success tool aligned on company records as deals close.
  • 04 Sync folk people and companies with a marketing or outbound tool so outreach lists stay current.

Common sync patterns

Where Autopilot scores or ranks records: results on the CRM record

Lead scores, fit ratings, or priority computed in Autopilot land as fields on the matching contact or account in Folk CRM, so reps sort and act on them without leaving the CRM.

Where Autopilot classifies or tags: labels sync onto the record

Categories, sentiment, or intent produced in Autopilot attach to the right contact, account, or deal in Folk CRM, keeping segmentation current as new data arrives.

Where Autopilot indexes records for retrieval: Folk CRM keeps it fresh

Contacts, accounts, and notes from Folk CRM sync into Autopilot as they change, so embeddings or search stay aligned with the live CRM instead of a stale export.

What you can sync between Autopilot and Folk CRM

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Autopilot objects Folk CRM objects How this pairing syncs
Custom Fields User-defined contact properties (string, number, date, boolean); discovered so field keys map cleanly to destination columns. Custom fields Group-scoped attributes that receive enriched or computed values from external systems. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Contacts Core people records (email, name, custom fields, list and segment membership); upserted two-way as the primary sync object. Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. Contacts is specific to Autopilot and Groups to Folk CRM — each maps to any object or custom field on the other side.
Lists Static contact lists; membership is readable per list and writable by adding or removing contacts. Notes Free-text context attached to people and companies, readable for reporting. Lists is specific to Autopilot and Notes to Folk CRM — each maps to any object or custom field on the other side.
Smart Segments Rule-based dynamic audiences; membership is computed by Autopilot, so it is read-only over the API. Reminders Follow-up items that can be created from external triggers. Smart Segments is specific to Autopilot and Reminders to Folk CRM — each maps to any object or custom field on the other side.
Journeys (Triggers) Automation journeys; a contact can be added to a journey via its trigger endpoint to start automated email or SMS sequences. People Contact records; the primary entity synced with outreach and enrichment tools. Journeys (Triggers) is specific to Autopilot and People to Folk CRM — each maps to any object or custom field on the other side.
Activities Per-contact activity and event history (opens, clicks, journey steps); read-only feed used for engagement reporting. Companies Organization records linked to people and kept aligned with billing or CS systems. Activities is specific to Autopilot and Companies to Folk CRM — each maps to any object or custom field on the other side.

How changes propagate between Autopilot and Folk CRM

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Autopilot Folk CRM Interval-based propagation

DetectionStacksync polls Autopilot for changes on an incremental schedule, reading only records changed since the previous pass. No CDC.

DeliveryEach detected change is written to Folk CRM through its API, with automatic retries and rate-limit backoff.

Folk CRM Autopilot Sub-second propagation

DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a fallback.

DeliveryEach detected change is written to Autopilot through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Autopilot: The REST API is capped at 100 requests/minute per account; exceeding it returns HTTP 429. Enterprise plans can request a higher limit. Contact writes accept an array for bulk upsert, and list and segment reads paginate via a bookmark cursor.
  • Folk CRM: Subject to the platform's API rate limits.
What ships with Autopilot ⇄ Folk CRM

Connect Autopilot and Folk CRM for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Autopilot–Folk CRM connection.

Real-time

Two-way sync

Changes in Autopilot or Folk CRM instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Autopilot or Folk CRM data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Autopilot or Folk CRM record.

Observability

Monitoring

Track your Autopilot ⇄ Folk CRM sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Autopilot and Folk CRM.

How the Autopilot and Folk CRM connectors work

Autopilot

Integration surface
REST API (Autopilot v1); Autopilot rebranded to Ortto in 2021 and the newer Ortto API co-exists with the legacy Autopilot endpoints
Authentication
Per-account API key sent in the autopilotapikey request header (generated in account settings); requests use Content-Type application/json against https://api2.autopilothq.com/v1/
Change detection
No CDC; incremental sync polls the /contacts endpoint with bookmark cursor pagination and updated timestamps. Journey webhook actions can push specific contact events, but there is no general change-subscription webhook, so polling is the reliable path.
Capabilities
read · write
Rate limits
The REST API is capped at 100 requests/minute per account; exceeding it returns HTTP 429. Enterprise plans can request a higher limit. Contact writes accept an array for bulk upsert, and list and segment reads paginate via a bookmark cursor.
Autopilot setup guide

Folk CRM

Integration surface
REST API
Authentication
API key (Bearer token)
Change detection
Webhook subscriptions for record events, with polling of list endpoints as a fallback
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits
How it works

How to connect Autopilot to Folk CRM — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Autopilot and Folk CRM with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Autopilot connected
    Folk CRM connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Autopilot and Folk CRM objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Autopilot ⇄ Folk CRM
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Autopilot Folk CRM
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Autopilot and Folk CRM integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 389 integrations available for Autopilot and Folk CRM.

Popular · 7 of 389
All Autopilot integrations All Folk CRM integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own