--- title: "Lemlist connector: setup and compatibility | Stacksync" description: "Lemlist integration guide: plan Campaigns and Leads, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/lemlist last_modified: 2026-09-15 --- Business productivity · Two-way sync platform # Lemlist 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 Lemlist workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Campaigns, Leads and Activities. 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. - **Campaigns** - **Leads** - **Activities** **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=lemlist) ## 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 ## Lemlist records to discuss. These Lemlist record examples help scope a technical review. They are not a list of verified Stacksync operations. Campaigns Keep campaign ID, channel/account context, and separate audience membership IDs. Leads Retain the lead ID and record its relationship to any converted contact or company. Activities Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. ### See 3 more record examples Unsubscribes Identify this record type and the operation you need to review with Stacksync. Webhooks Identify this record type and the operation you need to review with Stacksync. Team Members Identify this record type and the operation you need to review with Stacksync. Connection setup ## Lemlist connection requirements. Review Lemlist 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 Lemlist account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Lemlist, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Lemlist integration. Choose the object and business event that matter to the workflow. Separate record updates from side effects such as notifications, approvals, and file creation. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Lemlist **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 Keep campaign ID, channel/account context, and separate audience membership IDs. Load related records in the right order Resolve contact/audience identities and channel-account references. ### Mapping checks by record type #### Campaigns Confirm object support with Stacksync Identity Keep campaign ID, channel/account context, and separate audience membership IDs. Fields to consider Source campaign ID · Channel reference · Status · Audience references · Measurement window Related records to resolve first Resolve contact/audience identities and channel-account references. Test before going live Test a removed audience member, a paused campaign, and one campaign reported across multiple channels. #### Leads Confirm object support with Stacksync Identity Retain the lead ID and record its relationship to any converted contact or company. Fields to consider Source lead ID · Qualification status · Owner reference · Conversion reference Related records to resolve first Resolve owner and campaign references and decide how conversion changes the identity relationship. Test before going live Convert a test lead after the first load and verify that it does not create a duplicate person or orphan its activity. #### Activities Confirm object support with Stacksync Identity Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. Fields to consider Source event ID · Event type · Occurred-at time · Related record ID · Payload version Related records to resolve first Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID. Test before going live Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior. [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 Lemlist integration in four steps. An update reaches the intended record, preserves its relationships, and performs each approved side effect once. ### View the four setup tests and expected results 1. ### Verify Lemlist 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 Campaigns Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a removed audience member, a paused campaign, and one campaign reported across multiple channels. **Expected result:** An update reaches the intended record, preserves its relationships, and performs each approved side effect once. 3. ### Test the operation your workflow needs Review one Lemlist 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 Lemlist integration. ### Diagnose record matching, delayed changes, and rejected operations A Lemlist record appears under the wrong destination record Keep campaign ID, channel/account context, and separate audience membership IDs. Resolve contact/audience identities and channel-account references. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Lemlist implementation’s change-detection method for Campaigns, Leads and Activities. 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 Lemlist 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 Lemlist workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=lemlist) ## Lemlist 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 ## Lemlist connector FAQ ### How should I plan an integration with Lemlist? Choose the object and business event that matter to the workflow. Separate record updates from side effects such as notifications, approvals, and file creation. 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 Lemlist connector write changes back? Write-back support is not established for this connection. Review the Lemlist records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Lemlist data? Keep campaign ID, channel/account context, and separate audience membership IDs. ### Which related records should I load first for Lemlist? Resolve contact/audience identities and channel-account references. ### How do I validate Lemlist changes after the initial load? Test a removed audience member, a paused campaign, and one campaign reported across multiple channels. An update reaches the intended record, preserves its relationships, and performs each approved side effect once. ### What should I include when estimating Lemlist integration costs? Estimate the number of Campaigns, Leads and Activities records, the history to load, ongoing changes, and required environments. Include API access, the integration service, destination storage or processing, and the work to maintain mappings and recover from errors. Review current provider pricing against that workload, including any account or API upgrades. AI assistant ## Set up Lemlist 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 Lemlist and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Lemlist. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Lemlist record changes.” - “Create a Genie that answers questions about our Lemlist 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 Lemlist 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 - [Attio and Lemlist](https://www.stacksync.com/integrations/attio-and-lemlist) - [Lemlist and Pipedrive](https://www.stacksync.com/integrations/lemlist-and-pipedrive) - [Google Sheets and Lemlist](https://www.stacksync.com/integrations/google-sheets-and-lemlist) - [HubSpot and Lemlist](https://www.stacksync.com/integrations/hubspot-and-lemlist) - [Lemlist and Slack](https://www.stacksync.com/integrations/lemlist-and-slack) - [Lemlist and Salesforce](https://www.stacksync.com/integrations/lemlist-and-salesforce) - [Lemlist and Zoho CRM](https://www.stacksync.com/integrations/lemlist-and-zoho-crm) - [Lemlist and Microsoft 365](https://www.stacksync.com/integrations/lemlist-and-microsoft-365) ### CRM · 32 - [Lemlist and 6sense](https://www.stacksync.com/integrations/6sense-and-lemlist) - [Lemlist and Affinity](https://www.stacksync.com/integrations/affinity-and-lemlist) - [Lemlist and Apollo.io](https://www.stacksync.com/integrations/apollo-io-and-lemlist) - [Lemlist and Attio](https://www.stacksync.com/integrations/attio-and-lemlist) - [Lemlist and Chorusai](https://www.stacksync.com/integrations/chorusai-and-lemlist) - [Lemlist and Clearbit](https://www.stacksync.com/integrations/clearbit-and-lemlist) - [Lemlist and Close](https://www.stacksync.com/integrations/close-and-lemlist) - [Lemlist and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-lemlist) - [Lemlist and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-lemlist) - [Lemlist and Freshsales](https://www.stacksync.com/integrations/freshsales-and-lemlist) - [Lemlist and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-lemlist) - [Lemlist and Gong](https://www.stacksync.com/integrations/gong-and-lemlist) - [Lemlist and HubSpot](https://www.stacksync.com/integrations/hubspot-and-lemlist) - [Lemlist and Infor CRM](https://www.stacksync.com/integrations/infor-crm-and-lemlist) - [Lemlist and Insightly](https://www.stacksync.com/integrations/insightly-and-lemlist) - [Lemlist and Intercom](https://www.stacksync.com/integrations/intercom-and-lemlist) - [Lemlist and Kommo](https://www.stacksync.com/integrations/kommo-and-lemlist) - [Lemlist and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/lemlist-and-microsoft-dynamics-365-sales) - [Lemlist and Outreach](https://www.stacksync.com/integrations/lemlist-and-outreach) - [Lemlist and Pipedrive](https://www.stacksync.com/integrations/lemlist-and-pipedrive) - [Lemlist and Salesforce](https://www.stacksync.com/integrations/lemlist-and-salesforce) - [Lemlist and Salesloft](https://www.stacksync.com/integrations/lemlist-and-salesloft) - [Lemlist and SAP Sales Cloud](https://www.stacksync.com/integrations/lemlist-and-sap-sales-cloud) - [Lemlist and Seismic](https://www.stacksync.com/integrations/lemlist-and-seismic) - [Lemlist and Shopify](https://www.stacksync.com/integrations/lemlist-and-shopify) - [Lemlist and SugarCRM](https://www.stacksync.com/integrations/lemlist-and-sugarcrm) - [Lemlist and Veeva CRM](https://www.stacksync.com/integrations/lemlist-and-veeva-crm) - [Lemlist and Vtiger CRM](https://www.stacksync.com/integrations/lemlist-and-vtiger-crm) - [Lemlist and Xactly](https://www.stacksync.com/integrations/lemlist-and-xactly) - [Lemlist and Zoho CRM](https://www.stacksync.com/integrations/lemlist-and-zoho-crm) - [Lemlist and Zoho SalesIQ](https://www.stacksync.com/integrations/lemlist-and-zoho-salesiq) - [Lemlist and ZoomInfo](https://www.stacksync.com/integrations/lemlist-and-zoominfo) ### ERP · 6 - [Lemlist and Acumatica](https://www.stacksync.com/integrations/acumatica-and-lemlist) - [Lemlist and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-lemlist) - [Lemlist and Deposco](https://www.stacksync.com/integrations/deposco-and-lemlist) - [Lemlist and Körber WMS](https://www.stacksync.com/integrations/korber-wms-and-lemlist) - [Lemlist and Odoo](https://www.stacksync.com/integrations/lemlist-and-odoo) - [Lemlist and SAP](https://www.stacksync.com/integrations/lemlist-and-sap) ### Database · 13 - [Lemlist and Airtable](https://www.stacksync.com/integrations/airtable-and-lemlist) - [Lemlist and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-lemlist) - [Lemlist and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-lemlist) - [Lemlist and Firebase](https://www.stacksync.com/integrations/firebase-and-lemlist) - [Lemlist and IBM Db2](https://www.stacksync.com/integrations/ibm-db2-and-lemlist) - [Lemlist and MariaDB](https://www.stacksync.com/integrations/lemlist-and-mariadb) - [Lemlist and MySQL](https://www.stacksync.com/integrations/lemlist-and-mysql) - [Lemlist and Oracle DB](https://www.stacksync.com/integrations/lemlist-and-oracle-db) - [Lemlist and Postgres Heroku](https://www.stacksync.com/integrations/lemlist-and-postgres-heroku) - [Lemlist and PostgreSQL](https://www.stacksync.com/integrations/lemlist-and-postgresql) - [Lemlist and SAP HANA](https://www.stacksync.com/integrations/lemlist-and-sap-hana) - [Lemlist and Scaleway Postgres](https://www.stacksync.com/integrations/lemlist-and-scaleway-postgres) - [Lemlist and SQL Server](https://www.stacksync.com/integrations/lemlist-and-sql-server) ### Data warehouse · 9 - [Lemlist and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-lemlist) - [Lemlist and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-lemlist) - [Lemlist and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-lemlist) - [Lemlist and BigQuery](https://www.stacksync.com/integrations/bigquery-and-lemlist) - [Lemlist and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-lemlist) - [Lemlist and Databricks](https://www.stacksync.com/integrations/databricks-and-lemlist) - [Lemlist and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-lemlist) - [Lemlist and Rockset](https://www.stacksync.com/integrations/lemlist-and-rockset) - [Lemlist and Snowflake](https://www.stacksync.com/integrations/lemlist-and-snowflake) ### Business productivity · 30 - [Lemlist and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-lemlist) - [Lemlist and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-lemlist) - [Lemlist and Asana](https://www.stacksync.com/integrations/asana-and-lemlist) - [Lemlist and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-lemlist) - [Lemlist and Customer.io](https://www.stacksync.com/integrations/customer-io-and-lemlist) - [Lemlist and Docusign](https://www.stacksync.com/integrations/docusign-and-lemlist) - [Lemlist and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-lemlist) - [Lemlist and Front](https://www.stacksync.com/integrations/front-and-lemlist) - [Lemlist and FullEnrich](https://www.stacksync.com/integrations/full-enrich-and-lemlist) - [Lemlist and Gainsight](https://www.stacksync.com/integrations/gainsight-and-lemlist) - [Lemlist and GitHub](https://www.stacksync.com/integrations/github-and-lemlist) - [Lemlist and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-lemlist) - [Lemlist and Ironclad](https://www.stacksync.com/integrations/ironclad-and-lemlist) - [Lemlist and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-lemlist) - [Lemlist and Lusha](https://www.stacksync.com/integrations/lemlist-and-lusha) - [Lemlist and Microsoft 365](https://www.stacksync.com/integrations/lemlist-and-microsoft-365) - [Lemlist and Microsoft Dynamics 365](https://www.stacksync.com/integrations/lemlist-and-microsoft-dynamics-365) - [Lemlist and Microsoft Teams](https://www.stacksync.com/integrations/lemlist-and-microsoft-teams) - [Lemlist and Monday](https://www.stacksync.com/integrations/lemlist-and-monday) - [Lemlist and Notion](https://www.stacksync.com/integrations/lemlist-and-notion) - [Lemlist and Quip](https://www.stacksync.com/integrations/lemlist-and-quip) - [Lemlist and Resend](https://www.stacksync.com/integrations/lemlist-and-resend) - [Lemlist and SendGrid](https://www.stacksync.com/integrations/lemlist-and-sendgrid) - [Lemlist and ServiceMax](https://www.stacksync.com/integrations/lemlist-and-servicemax) - [Lemlist and Slack](https://www.stacksync.com/integrations/lemlist-and-slack) - [Lemlist and Smartsheet](https://www.stacksync.com/integrations/lemlist-and-smartsheet) - [Lemlist and SysAid](https://www.stacksync.com/integrations/lemlist-and-sysaid) - [Lemlist and Twilio](https://www.stacksync.com/integrations/lemlist-and-twilio) - [Lemlist and Wrike](https://www.stacksync.com/integrations/lemlist-and-wrike) - [Lemlist and Zendesk](https://www.stacksync.com/integrations/lemlist-and-zendesk) ### Accounting and finance · 14 - [Lemlist and Adyen](https://www.stacksync.com/integrations/adyen-and-lemlist) - [Lemlist and BILL](https://www.stacksync.com/integrations/bill-and-lemlist) - [Lemlist and Braintree](https://www.stacksync.com/integrations/braintree-and-lemlist) - [Lemlist and Chargebee](https://www.stacksync.com/integrations/chargebee-and-lemlist) - [Lemlist and Coupa](https://www.stacksync.com/integrations/coupa-and-lemlist) - [Lemlist and Hyperline](https://www.stacksync.com/integrations/hyperline-and-lemlist) - [Lemlist and Navan](https://www.stacksync.com/integrations/lemlist-and-navan) - [Lemlist and Pigment](https://www.stacksync.com/integrations/lemlist-and-pigment) - [Lemlist and Ramp](https://www.stacksync.com/integrations/lemlist-and-ramp) - [Lemlist and Recurly](https://www.stacksync.com/integrations/lemlist-and-recurly) - [Lemlist and Rillet](https://www.stacksync.com/integrations/lemlist-and-rillet) - [Lemlist and Stripe](https://www.stacksync.com/integrations/lemlist-and-stripe) - [Lemlist and Workday](https://www.stacksync.com/integrations/lemlist-and-workday) - [Lemlist and Zuora](https://www.stacksync.com/integrations/lemlist-and-zuora) ### AI · 4 - [Lemlist and Autopilot](https://www.stacksync.com/integrations/autopilot-and-lemlist) - [Lemlist and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-lemlist) - [Lemlist and OpenAI](https://www.stacksync.com/integrations/lemlist-and-openai) - [Lemlist and Pinecone](https://www.stacksync.com/integrations/lemlist-and-pinecone) ### Communications · 1 - [Lemlist and Gmail](https://www.stacksync.com/integrations/gmail-and-lemlist) ### Developer tools · 9 - [Lemlist and Azure Service Bus](https://www.stacksync.com/integrations/azure-service-bus-and-lemlist) - [Lemlist and Datadog](https://www.stacksync.com/integrations/datadog-and-lemlist) - [Lemlist and Jira](https://www.stacksync.com/integrations/jira-and-lemlist) - [Lemlist and JMS](https://www.stacksync.com/integrations/jms-and-lemlist) - [Lemlist and LDAP](https://www.stacksync.com/integrations/ldap-and-lemlist) - [Lemlist and New Relic](https://www.stacksync.com/integrations/lemlist-and-newrelic) - [Lemlist and Opsgenie](https://www.stacksync.com/integrations/lemlist-and-opsgenie) - [Lemlist and PagerDuty](https://www.stacksync.com/integrations/lemlist-and-pagerduty) - [Lemlist and RabbitMQ](https://www.stacksync.com/integrations/lemlist-and-rabbitmq) ### Human resources · 11 - [Lemlist and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-lemlist) - [Lemlist and Greenhouse](https://www.stacksync.com/integrations/greenhouse-and-lemlist) - [Lemlist and Hibob](https://www.stacksync.com/integrations/hibob-and-lemlist) - [Lemlist and Jobvite](https://www.stacksync.com/integrations/jobvite-and-lemlist) - [Lemlist and Lever](https://www.stacksync.com/integrations/lemlist-and-lever) - [Lemlist and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/lemlist-and-oracle-fusion-cloud-hcm) - [Lemlist and Paylocity](https://www.stacksync.com/integrations/lemlist-and-paylocity) - [Lemlist and SmartRecruiters](https://www.stacksync.com/integrations/lemlist-and-smartrecruiters) - [Lemlist and Success Factors](https://www.stacksync.com/integrations/lemlist-and-success-factors) - [Lemlist and UKG Pro](https://www.stacksync.com/integrations/lemlist-and-ukg-pro) - [Lemlist and UKG Ready](https://www.stacksync.com/integrations/lemlist-and-ukg-ready) ### Security and identity · 6 - [Lemlist and Active Directory](https://www.stacksync.com/integrations/active-directory-and-lemlist) - [Lemlist and Auth0](https://www.stacksync.com/integrations/auth0-and-lemlist) - [Lemlist and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-lemlist) - [Lemlist and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-lemlist) - [Lemlist and Okta](https://www.stacksync.com/integrations/lemlist-and-okta) - [Lemlist and OneLogin](https://www.stacksync.com/integrations/lemlist-and-onelogin) ### Storage · 4 - [Lemlist and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-lemlist) - [Lemlist and Box](https://www.stacksync.com/integrations/box-and-lemlist) - [Lemlist and Egnyte](https://www.stacksync.com/integrations/egnyte-and-lemlist) - [Lemlist and SharePoint](https://www.stacksync.com/integrations/lemlist-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/)