---
title: "Folk CRM connector: setup and compatibility | Stacksync"
description: "Folk CRM integration guide: plan Companies and People, record identity, setup, and compatibility."
canonical: https://www.stacksync.com/connectors/folk-crm
last_modified: 2026-09-15
---

CRM · Two-way sync platform

# Folk CRM integration.

> For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md

Connect your Folk CRM workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Companies, People and Groups.

Set this up from Claude or ChatGPT

- Review your systems with an integration engineer
- Get a scoped implementation and validation plan

Technical workflow review

## Bring one workflow. Leave with a technical plan.

An engineer will assess the required records, access method, and read/write operations before recommending an implementation.

- **People**
- **Companies**
- **Groups**

**What to bring** Bring a sample record, the other system, and the change your team needs to automate.

[Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=folk-crm)

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

- Gladia Case study
- IDEXX
- MedPro Migrated from MuleSoft
- Eko Case study
- Ubicloud
- Vimeo
- Codility Migrated from Celigo
- ACERTUS Migrated from Heroku Connect
- Syringa Migrated from Matillion
- Truora
- Streaam Case study
- SEAL SQ
- Rinsed Migrated from Fivetran
- IA Capital Group Case study
- Meter
- Golden Pear Funding Migrated from Celigo

Record types

## Folk CRM records to discuss.

These Folk CRM record examples help scope a technical review. They are not a list of verified Stacksync operations.

People

Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.

Companies

Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.

Groups

Keep group IDs and membership relationships separately from group names.

### See 3 more record examples

Custom fields

Identify this record type and the operation you need to review with Stacksync.

Notes

Identify this record type and the operation you need to review with Stacksync.

Reminders

Identify this record type and the operation you need to review with Stacksync.

Connection setup

## Folk CRM connection requirements.

Review Folk CRM access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion.

### Prepare access and scope for the engineering review

- Identify the Folk CRM account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Folk CRM, including read/write support, authentication, and initial-load limits.

Integration design

## Match records and fields for your Folk CRM integration.

Choose the owner of customer details, qualification, and commercial status separately. A customer update, a won deal, and an approved order represent different business decisions.

Use these design questions to prepare a representative record and the business rules your integration must preserve.

### Explore record matching and field-mapping checks

Folk CRM **Source record ID** Keep the account and record type

Record matching **Source ID ↔ destination ID** Link the same record across systems

Selected destination **Destination record ID** Preserve its local key and rules

*Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.*

Match the same record in both systems

Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.

Load related records in the right order

Resolve parent organizations, business units, and currency references before dependent transactions.

### Mapping checks by record type

#### Companies

Confirm object support with Stacksync

Identity

Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.

Fields to consider

Source record ID · Legal or display name · Business-unit reference · Lifecycle status

Related records to resolve first

Resolve parent organizations, business units, and currency references before dependent transactions.

Test before going live

Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.

#### People

Confirm object support with Stacksync

Identity

Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.

Fields to consider

Source person ID · Display name · Email address · Organization reference · Consent state

Related records to resolve first

Resolve the organization relationship and any owner or consent references required by the destination.

Test before going live

Test an email change, two records sharing an email, and a person associated with multiple organizations.

#### Groups

Confirm object support with Stacksync

Identity

Keep group IDs and membership relationships separately from group names.

Fields to consider

Source group ID · Member references · Tenant reference · Group type

Related records to resolve first

Resolve user and tenant identities before membership changes.

Test before going live

Test removed membership, nested groups, and equal group names in different tenants.

[Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer.

Setup and validation

## Validate the Folk CRM integration in four steps.

A changed contact detail updates the existing person; a sales-state change reaches only the downstream process approved to act on it.

### View the four setup tests and expected results

1. ### Verify Folk CRM credentials and resource scope

   After confirming an implementation path, validate the selected access method with the intended account, region or workspace, and resource scope. Record the credential owner and renewal procedure, then demonstrate access to one selected object.

   **Expected result:** The selected resource is accessible through the approved credential, with the renewal and revocation procedure assigned to an owner.
2. ### Test record matching for Companies

   Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.

   **Expected result:** A changed contact detail updates the existing person; a sales-state change reaches only the downstream process approved to act on it.
3. ### Test the operation your workflow needs

   Review one Folk CRM record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration.

   **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair.
4. ### Test recovery and name the support owner

   For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity.

   **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors.

[Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live.

Troubleshooting

## Troubleshoot your Folk CRM integration.

### Diagnose record matching, delayed changes, and rejected operations

A Folk CRM record appears under the wrong destination record

Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Resolve parent organizations, business units, and currency references before dependent transactions. Repair the ID relationship before repeating the operation.

The first load looks correct but later results differ

Confirm the selected Folk CRM implementation’s change-detection method for Companies, People and Groups. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture.

One operation succeeds while another is rejected

Check the specific Folk CRM object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available.

[Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded.

[Review your Folk CRM workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=folk-crm)

## Folk CRM integration guides

- [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist)
- [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations)

FAQ

## Folk CRM connector FAQ

### How should I plan an integration with Folk CRM?

Choose the owner of customer details, qualification, and commercial status separately. A customer update, a won deal, and an approved order represent different business decisions. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

### Can the Folk CRM connector write changes back?

Write-back support is not established for this connection. Review the Folk CRM records and fields you need with a Stacksync engineer, then test the required operation with a representative record.

### Which identifiers should I preserve for Folk CRM data?

Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.

### Which related records should I load first for Folk CRM?

Resolve parent organizations, business units, and currency references before dependent transactions.

### How do I validate Folk CRM changes after the initial load?

Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only. A changed contact detail updates the existing person; a sales-state change reaches only the downstream process approved to act on it.

### What will we cover in a Folk CRM integration demo?

Start with one workflow and a sample record from Companies, People and Groups. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.

AI assistant

## Set up Folk CRM from Claude or ChatGPT

Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.

### 1. Add the Stacksync MCP server

Server URL

`https://mcp.stacksync.com/mcp`

#### In Claude

1. Open Customize → Connectors, select + Add, then Add custom connector.
2. Name it Stacksync and enter https://mcp.stacksync.com/mcp.
3. Select Connect, sign in to Stacksync and choose your workspace.

#### In ChatGPT

1. Open Settings → Apps → Advanced settings and turn on Developer mode.
2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.

##### Set up Codex or Claude Code

#### Codex

```
codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksync
```

Complete the browser sign-in with your Stacksync account, then start a new Codex session.

#### Claude Code

```
claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp
```

Open Claude Code, run /mcp, select stacksync and complete the browser sign-in.

Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.

Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp).

### 2. Ask your assistant

> Create a sync between my Folk CRM and another app or database.

#### Also from the same chat

You can also ask for workflows and AI agents (Genies) that use Folk CRM. The assistant checks what each app supports, for example:

- “Build a workflow that messages our team in Slack when a Folk CRM record changes.”
- “Create a Genie that answers questions about our Folk CRM data in Slack.”

#### What happens next

- Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat.
- Gives you a secure sign-in link for each app it connects; you open it and sign in to that app.
- Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first.

New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant.

## Explore Folk CRM connections

Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair.

### Start with these integration guides

- [Cvent and Folk CRM](https://www.stacksync.com/integrations/cvent-and-folk-crm)
- [Folk CRM and Microsoft 365](https://www.stacksync.com/integrations/folk-crm-and-microsoft-365)
- [Folk CRM and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/folk-crm-and-microsoft-dynamics-365-sales)
- [Folk CRM and Okta](https://www.stacksync.com/integrations/folk-crm-and-okta)
- [Folk CRM and Hibob](https://www.stacksync.com/integrations/folk-crm-and-hibob)
- [Aircall and Folk CRM](https://www.stacksync.com/integrations/aircall-and-folk-crm)
- [Folk CRM and Google Sheets](https://www.stacksync.com/integrations/folk-crm-and-google-sheets)
- [Folk CRM and Outreach](https://www.stacksync.com/integrations/folk-crm-and-outreach)

### CRM · 32

- [Folk CRM and 6sense](https://www.stacksync.com/integrations/6sense-and-folk-crm)
- [Folk CRM and Affinity](https://www.stacksync.com/integrations/affinity-and-folk-crm)
- [Folk CRM and Attio](https://www.stacksync.com/integrations/attio-and-folk-crm)
- [Folk CRM and Chorusai](https://www.stacksync.com/integrations/chorusai-and-folk-crm)
- [Folk CRM and Clearbit](https://www.stacksync.com/integrations/clearbit-and-folk-crm)
- [Folk CRM and Close](https://www.stacksync.com/integrations/close-and-folk-crm)
- [Folk CRM and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-folk-crm)
- [Folk CRM and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-folk-crm)
- [Folk CRM and Freshsales](https://www.stacksync.com/integrations/folk-crm-and-freshsales)
- [Folk CRM and Freshworks CRM](https://www.stacksync.com/integrations/folk-crm-and-freshworks-crm)
- [Folk CRM and Gong](https://www.stacksync.com/integrations/folk-crm-and-gong)
- [Folk CRM and Gorgias](https://www.stacksync.com/integrations/folk-crm-and-gorgias)
- [Folk CRM and HubSpot](https://www.stacksync.com/integrations/folk-crm-and-hubspot)
- [Folk CRM and Infor CRM](https://www.stacksync.com/integrations/folk-crm-and-infor-crm)
- [Folk CRM and Insightly](https://www.stacksync.com/integrations/folk-crm-and-insightly)
- [Folk CRM and Intercom](https://www.stacksync.com/integrations/folk-crm-and-intercom)
- [Folk CRM and Kommo](https://www.stacksync.com/integrations/folk-crm-and-kommo)
- [Folk CRM and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/folk-crm-and-microsoft-dynamics-365-sales)
- [Folk CRM and Outreach](https://www.stacksync.com/integrations/folk-crm-and-outreach)
- [Folk CRM and Pipedrive](https://www.stacksync.com/integrations/folk-crm-and-pipedrive)
- [Folk CRM and Salesforce](https://www.stacksync.com/integrations/folk-crm-and-salesforce)
- [Folk CRM and Salesloft](https://www.stacksync.com/integrations/folk-crm-and-salesloft)
- [Folk CRM and SAP Sales Cloud](https://www.stacksync.com/integrations/folk-crm-and-sap-sales-cloud)
- [Folk CRM and Seismic](https://www.stacksync.com/integrations/folk-crm-and-seismic)
- [Folk CRM and Shopify](https://www.stacksync.com/integrations/folk-crm-and-shopify)
- [Folk CRM and SugarCRM](https://www.stacksync.com/integrations/folk-crm-and-sugarcrm)
- [Folk CRM and Veeva CRM](https://www.stacksync.com/integrations/folk-crm-and-veeva-crm)
- [Folk CRM and Vtiger CRM](https://www.stacksync.com/integrations/folk-crm-and-vtiger-crm)
- [Folk CRM and Xactly](https://www.stacksync.com/integrations/folk-crm-and-xactly)
- [Folk CRM and Zoho CRM](https://www.stacksync.com/integrations/folk-crm-and-zoho-crm)
- [Folk CRM and Zoho SalesIQ](https://www.stacksync.com/integrations/folk-crm-and-zoho-salesiq)
- [Folk CRM and ZoomInfo](https://www.stacksync.com/integrations/folk-crm-and-zoominfo)

### ERP · 24

- [Folk CRM and Acumatica](https://www.stacksync.com/integrations/acumatica-and-folk-crm)
- [Folk CRM and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-folk-crm)
- [Folk CRM and Cin7](https://www.stacksync.com/integrations/cin7-and-folk-crm)
- [Folk CRM and Dynamics 365 Business Central](https://www.stacksync.com/integrations/folk-crm-and-microsoft-dynamics-365-business-central)
- [Folk CRM and Epicor ERP](https://www.stacksync.com/integrations/epicor-erp-and-folk-crm)
- [Folk CRM and Infor LN](https://www.stacksync.com/integrations/folk-crm-and-infor-ln)
- [Folk CRM and Infor M3](https://www.stacksync.com/integrations/folk-crm-and-infor-m3)
- [Folk CRM and Linnworks](https://www.stacksync.com/integrations/folk-crm-and-linnworks)
- [Folk CRM and Microsoft Dynamics GP](https://www.stacksync.com/integrations/folk-crm-and-microsoft-dynamics-gp)
- [Folk CRM and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/folk-crm-and-microsoft-dynamics-nav)
- [Folk CRM and NetSuite](https://www.stacksync.com/integrations/folk-crm-and-netsuite)
- [Folk CRM and Odoo](https://www.stacksync.com/integrations/folk-crm-and-odoo)
- [Folk CRM and Plex ERP](https://www.stacksync.com/integrations/folk-crm-and-plex-erp)
- [Folk CRM and QAD ERP](https://www.stacksync.com/integrations/folk-crm-and-qad-erp)
- [Folk CRM and Sage 100](https://www.stacksync.com/integrations/folk-crm-and-sage-100)
- [Folk CRM and Sage 300](https://www.stacksync.com/integrations/folk-crm-and-sage-300)
- [Folk CRM and Sage Intacct](https://www.stacksync.com/integrations/folk-crm-and-sage-intacct)
- [Folk CRM and Sage X3](https://www.stacksync.com/integrations/folk-crm-and-sage-x3)
- [Folk CRM and SAP](https://www.stacksync.com/integrations/folk-crm-and-sap)
- [Folk CRM and SAP Business ByDesign](https://www.stacksync.com/integrations/folk-crm-and-sap-business-bydesign)
- [Folk CRM and SAP Business One](https://www.stacksync.com/integrations/folk-crm-and-sap-business-one)
- [Folk CRM and SAP S/4HANA](https://www.stacksync.com/integrations/folk-crm-and-sap-s4hana)
- [Folk CRM and Syspro](https://www.stacksync.com/integrations/folk-crm-and-syspro)
- [Folk CRM and TikTok Shop](https://www.stacksync.com/integrations/folk-crm-and-tiktok)

### Database · 11

- [Folk CRM and Airtable](https://www.stacksync.com/integrations/airtable-and-folk-crm)
- [Folk CRM and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-folk-crm)
- [Folk CRM and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-folk-crm)
- [Folk CRM and Firebase](https://www.stacksync.com/integrations/firebase-and-folk-crm)
- [Folk CRM and MongoDB](https://www.stacksync.com/integrations/folk-crm-and-mongodb)
- [Folk CRM and MySQL](https://www.stacksync.com/integrations/folk-crm-and-mysql)
- [Folk CRM and Neo4j](https://www.stacksync.com/integrations/folk-crm-and-neo4j)
- [Folk CRM and PostgreSQL](https://www.stacksync.com/integrations/folk-crm-and-postgresql)
- [Folk CRM and SAP HANA](https://www.stacksync.com/integrations/folk-crm-and-sap-hana)
- [Folk CRM and SQL Server](https://www.stacksync.com/integrations/folk-crm-and-sql-server)
- [Folk CRM and Supabase](https://www.stacksync.com/integrations/folk-crm-and-supabase)

### Data warehouse · 8

- [Folk CRM and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-folk-crm)
- [Folk CRM and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-folk-crm)
- [Folk CRM and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-folk-crm)
- [Folk CRM and BigQuery](https://www.stacksync.com/integrations/bigquery-and-folk-crm)
- [Folk CRM and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-folk-crm)
- [Folk CRM and Databricks](https://www.stacksync.com/integrations/databricks-and-folk-crm)
- [Folk CRM and Google Cloud Platform](https://www.stacksync.com/integrations/folk-crm-and-google-cloud-platform)
- [Folk CRM and Snowflake](https://www.stacksync.com/integrations/folk-crm-and-snowflake)

### Business productivity · 26

- [Folk CRM and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-folk-crm)
- [Folk CRM and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-folk-crm)
- [Folk CRM and Asana](https://www.stacksync.com/integrations/asana-and-folk-crm)
- [Folk CRM and Braze](https://www.stacksync.com/integrations/braze-and-folk-crm)
- [Folk CRM and Campfire](https://www.stacksync.com/integrations/campfire-and-folk-crm)
- [Folk CRM and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-folk-crm)
- [Folk CRM and Docusign](https://www.stacksync.com/integrations/docusign-and-folk-crm)
- [Folk CRM and Front](https://www.stacksync.com/integrations/folk-crm-and-front)
- [Folk CRM and Gainsight](https://www.stacksync.com/integrations/folk-crm-and-gainsight)
- [Folk CRM and Google Sheets](https://www.stacksync.com/integrations/folk-crm-and-google-sheets)
- [Folk CRM and Ironclad](https://www.stacksync.com/integrations/folk-crm-and-ironclad)
- [Folk CRM and Klaviyo](https://www.stacksync.com/integrations/folk-crm-and-klaviyo)
- [Folk CRM and Lusha](https://www.stacksync.com/integrations/folk-crm-and-lusha)
- [Folk CRM and Microsoft 365](https://www.stacksync.com/integrations/folk-crm-and-microsoft-365)
- [Folk CRM and Microsoft Dynamics 365](https://www.stacksync.com/integrations/folk-crm-and-microsoft-dynamics-365)
- [Folk CRM and Monday](https://www.stacksync.com/integrations/folk-crm-and-monday)
- [Folk CRM and Notion](https://www.stacksync.com/integrations/folk-crm-and-notion)
- [Folk CRM and Quip](https://www.stacksync.com/integrations/folk-crm-and-quip)
- [Folk CRM and SendGrid](https://www.stacksync.com/integrations/folk-crm-and-sendgrid)
- [Folk CRM and ServiceMax](https://www.stacksync.com/integrations/folk-crm-and-servicemax)
- [Folk CRM and ServiceNow](https://www.stacksync.com/integrations/folk-crm-and-servicenow)
- [Folk CRM and Smartsheet](https://www.stacksync.com/integrations/folk-crm-and-smartsheet)
- [Folk CRM and SysAid](https://www.stacksync.com/integrations/folk-crm-and-sysaid)
- [Folk CRM and Twilio](https://www.stacksync.com/integrations/folk-crm-and-twilio)
- [Folk CRM and Wrike](https://www.stacksync.com/integrations/folk-crm-and-wrike)
- [Folk CRM and Zendesk](https://www.stacksync.com/integrations/folk-crm-and-zendesk)

### Accounting and finance · 12

- [Folk CRM and Adyen](https://www.stacksync.com/integrations/adyen-and-folk-crm)
- [Folk CRM and Anaplan](https://www.stacksync.com/integrations/anaplan-and-folk-crm)
- [Folk CRM and BILL](https://www.stacksync.com/integrations/bill-and-folk-crm)
- [Folk CRM and Braintree](https://www.stacksync.com/integrations/braintree-and-folk-crm)
- [Folk CRM and Chargebee](https://www.stacksync.com/integrations/chargebee-and-folk-crm)
- [Folk CRM and Coupa](https://www.stacksync.com/integrations/coupa-and-folk-crm)
- [Folk CRM and Navan](https://www.stacksync.com/integrations/folk-crm-and-navan)
- [Folk CRM and QuickBooks](https://www.stacksync.com/integrations/folk-crm-and-quickbooks)
- [Folk CRM and Ramp](https://www.stacksync.com/integrations/folk-crm-and-ramp)
- [Folk CRM and Recurly](https://www.stacksync.com/integrations/folk-crm-and-recurly)
- [Folk CRM and Stripe](https://www.stacksync.com/integrations/folk-crm-and-stripe)
- [Folk CRM and Zuora](https://www.stacksync.com/integrations/folk-crm-and-zuora)

### AI · 4

- [Folk CRM and Autopilot](https://www.stacksync.com/integrations/autopilot-and-folk-crm)
- [Folk CRM and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-folk-crm)
- [Folk CRM and OpenAI](https://www.stacksync.com/integrations/folk-crm-and-openai)
- [Folk CRM and Pinecone](https://www.stacksync.com/integrations/folk-crm-and-pinecone)

### Analytics · 6

- [Folk CRM and Adobe Analytics](https://www.stacksync.com/integrations/adobeanalytics-and-folk-crm)
- [Folk CRM and Microsoft Power BI](https://www.stacksync.com/integrations/folk-crm-and-microsoft-power-bi)
- [Folk CRM and Mixpanel](https://www.stacksync.com/integrations/folk-crm-and-mixpanel)
- [Folk CRM and Pendo](https://www.stacksync.com/integrations/folk-crm-and-pendo)
- [Folk CRM and Splunk](https://www.stacksync.com/integrations/folk-crm-and-splunk)
- [Folk CRM and Tableau](https://www.stacksync.com/integrations/folk-crm-and-tableau)

### Communications · 6

- [Folk CRM and Aircall](https://www.stacksync.com/integrations/aircall-and-folk-crm)
- [Folk CRM and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-folk-crm)
- [Folk CRM and Gmail](https://www.stacksync.com/integrations/folk-crm-and-gmail)
- [Folk CRM and Infobip](https://www.stacksync.com/integrations/folk-crm-and-infobip)
- [Folk CRM and RingCentral](https://www.stacksync.com/integrations/folk-crm-and-ringcentral)
- [Folk CRM and Zoom](https://www.stacksync.com/integrations/folk-crm-and-zoom)

### E-commerce · 6

- [Folk CRM and Akeneo](https://www.stacksync.com/integrations/akeneo-and-folk-crm)
- [Folk CRM and BigCommerce](https://www.stacksync.com/integrations/bigcommerce-and-folk-crm)
- [Folk CRM and EasyPost](https://www.stacksync.com/integrations/easypost-and-folk-crm)
- [Folk CRM and Magento](https://www.stacksync.com/integrations/folk-crm-and-magento)
- [Folk CRM and Shipwire](https://www.stacksync.com/integrations/folk-crm-and-shipwire)
- [Folk CRM and Shopware](https://www.stacksync.com/integrations/folk-crm-and-shopware)

### Human resources · 11

- [Folk CRM and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-folk-crm)
- [Folk CRM and Greenhouse](https://www.stacksync.com/integrations/folk-crm-and-greenhouse)
- [Folk CRM and Hibob](https://www.stacksync.com/integrations/folk-crm-and-hibob)
- [Folk CRM and Jobvite](https://www.stacksync.com/integrations/folk-crm-and-jobvite)
- [Folk CRM and Lever](https://www.stacksync.com/integrations/folk-crm-and-lever)
- [Folk CRM and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/folk-crm-and-oracle-fusion-cloud-hcm)
- [Folk CRM and Paylocity](https://www.stacksync.com/integrations/folk-crm-and-paylocity)
- [Folk CRM and SmartRecruiters](https://www.stacksync.com/integrations/folk-crm-and-smartrecruiters)
- [Folk CRM and Success Factors](https://www.stacksync.com/integrations/folk-crm-and-success-factors)
- [Folk CRM and UKG Pro](https://www.stacksync.com/integrations/folk-crm-and-ukg-pro)
- [Folk CRM and UKG Ready](https://www.stacksync.com/integrations/folk-crm-and-ukg-ready)

### Marketing · 8

- [Folk CRM and Bingads](https://www.stacksync.com/integrations/bingads-and-folk-crm)
- [Folk CRM and Cvent](https://www.stacksync.com/integrations/cvent-and-folk-crm)
- [Folk CRM and Demandbase](https://www.stacksync.com/integrations/demandbase-and-folk-crm)
- [Folk CRM and Eloqua](https://www.stacksync.com/integrations/eloqua-and-folk-crm)
- [Folk CRM and Iterable](https://www.stacksync.com/integrations/folk-crm-and-iterable)
- [Folk CRM and Marketo](https://www.stacksync.com/integrations/folk-crm-and-marketo)
- [Folk CRM and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/folk-crm-and-salesforce-marketing-cloud)
- [Folk CRM and Twitter Ads](https://www.stacksync.com/integrations/folk-crm-and-twitter-ads)

### Security and identity · 6

- [Folk CRM and Active Directory](https://www.stacksync.com/integrations/active-directory-and-folk-crm)
- [Folk CRM and Auth0](https://www.stacksync.com/integrations/auth0-and-folk-crm)
- [Folk CRM and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-folk-crm)
- [Folk CRM and JumpCloud](https://www.stacksync.com/integrations/folk-crm-and-jumpcloud)
- [Folk CRM and Okta](https://www.stacksync.com/integrations/folk-crm-and-okta)
- [Folk CRM and OneLogin](https://www.stacksync.com/integrations/folk-crm-and-onelogin)

### Storage · 4

- [Folk CRM and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-folk-crm)
- [Folk CRM and Box](https://www.stacksync.com/integrations/box-and-folk-crm)
- [Folk CRM and Egnyte](https://www.stacksync.com/integrations/egnyte-and-folk-crm)
- [Folk CRM and SharePoint](https://www.stacksync.com/integrations/folk-crm-and-sharepoint)

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](https://www.stacksync.com/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](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more

## Connect the systems your business runs on. Build your next workflow with Stacksync.

[Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)
