--- title: "Lusha connector: setup and compatibility | Stacksync" description: "Lusha integration planning: Person Profiles, Company Profiles and Email Addresses. Compatibility, identity, dependencies, and validation." canonical: https://www.stacksync.com/connectors/lusha last_modified: 2026-09-15 --- Business productivity · Two-way sync platform # Lusha 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 Lusha workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Person Profiles, Company Profiles and Email Addresses. 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. - **Person Profiles** - **Company Profiles** - **Email Addresses** **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=lusha) ## 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 ## Lusha records to discuss. These Lusha record examples help scope a technical review. They are not a list of verified Stacksync operations. Person Profiles Identify this record type and the operation you need to review with Stacksync. Company Profiles Identify this record type and the operation you need to review with Stacksync. Email Addresses Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Phone Numbers Identify this record type and the operation you need to review with Stacksync. Prospecting Results Identify this record type and the operation you need to review with Stacksync. Bulk Enrichment Requests Identify this record type and the operation you need to review with Stacksync. Connection setup ## Lusha connection requirements. Review Lusha 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 Lusha account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Lusha, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Lusha 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 Lusha **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 Request a representative record and its documented stable identifier. Define the owning account/workspace and the business meaning of one record before creating a cross-system lookup. Load related records in the right order List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. ### Mapping checks by record type #### Person Profiles, Company Profiles and Email Addresses Confirm object support with Stacksync Identity Request a representative record and its documented stable identifier. Define the owning account/workspace and the business meaning of one record before creating a cross-system lookup. Fields to consider Source record identifier · Account or workspace · Required business values · Related record identifiers Related records to resolve first List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. Test before going live Demonstrate how an existing record is found after a label change, and how a related record is resolved when its parent is missing. [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 Lusha 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 Lusha 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 Person Profiles, Company Profiles and Email Addresses Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Demonstrate how an existing record is found after a label change, and how a related record is resolved when its parent is missing. **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 Lusha 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 Lusha integration. ### Diagnose record matching, delayed changes, and rejected operations A Lusha record appears under the wrong destination record Request a representative record and its documented stable identifier. Define the owning account/workspace and the business meaning of one record before creating a cross-system lookup. List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Lusha implementation’s change-detection method for Person Profiles, Company Profiles and Email Addresses. 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 Lusha 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 Lusha workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=lusha) ## Lusha 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 ## Lusha connector FAQ ### How should I plan an integration with Lusha? 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 Lusha connector write changes back? Write-back support is not established for this connection. Review the Lusha records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Lusha data? Request a representative record and its documented stable identifier. Define the owning account/workspace and the business meaning of one record before creating a cross-system lookup. ### Which related records should I load first for Lusha? List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. ### How do I validate Lusha changes after the initial load? Demonstrate how an existing record is found after a label change, and how a related record is resolved when its parent is missing. An update reaches the intended record, preserves its relationships, and performs each approved side effect once. ### What should I include when estimating Lusha integration costs? Estimate the number of Person Profiles, Company Profiles and Email Addresses 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 Lusha 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 Lusha and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Lusha. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Lusha record changes.” - “Create a Genie that answers questions about our Lusha 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 Lusha 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 - [Lusha and Salesforce](https://www.stacksync.com/integrations/lusha-and-salesforce) - [HubSpot and Lusha](https://www.stacksync.com/integrations/hubspot-and-lusha) - [Lusha and Outreach](https://www.stacksync.com/integrations/lusha-and-outreach) - [Attio and Lusha](https://www.stacksync.com/integrations/attio-and-lusha) - [Gong and Lusha](https://www.stacksync.com/integrations/gong-and-lusha) - [Lusha and Pipedrive](https://www.stacksync.com/integrations/lusha-and-pipedrive) - [Lusha and Snowflake](https://www.stacksync.com/integrations/lusha-and-snowflake) - [Lusha and Zoho CRM](https://www.stacksync.com/integrations/lusha-and-zoho-crm) ### CRM · 40 - [Lusha and Affinity](https://www.stacksync.com/integrations/affinity-and-lusha) - [Lusha and Apollo.io](https://www.stacksync.com/integrations/apollo-io-and-lusha) - [Lusha and Attio](https://www.stacksync.com/integrations/attio-and-lusha) - [Lusha and Chorusai](https://www.stacksync.com/integrations/chorusai-and-lusha) - [Lusha and Clari](https://www.stacksync.com/integrations/clari-and-lusha) - [Lusha and Close](https://www.stacksync.com/integrations/close-and-lusha) - [Lusha and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-lusha) - [Lusha and Creatio CRM](https://www.stacksync.com/integrations/creatio-crm-and-lusha) - [Lusha and DealCloud](https://www.stacksync.com/integrations/dealcloud-and-lusha) - [Lusha and Folk CRM](https://www.stacksync.com/integrations/folk-crm-and-lusha) - [Lusha and Freshsales](https://www.stacksync.com/integrations/freshsales-and-lusha) - [Lusha and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-lusha) - [Lusha and Gladly](https://www.stacksync.com/integrations/gladly-and-lusha) - [Lusha and Gong](https://www.stacksync.com/integrations/gong-and-lusha) - [Lusha and HubSpot](https://www.stacksync.com/integrations/hubspot-and-lusha) - [Lusha and Infor CRM](https://www.stacksync.com/integrations/infor-crm-and-lusha) - [Lusha and Insightly](https://www.stacksync.com/integrations/insightly-and-lusha) - [Lusha and Intercom](https://www.stacksync.com/integrations/intercom-and-lusha) - [Lusha and Kommo](https://www.stacksync.com/integrations/kommo-and-lusha) - [Lusha and Kustomer](https://www.stacksync.com/integrations/kustomer-and-lusha) - [Lusha and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/lusha-and-microsoft-dynamics-365-sales) - [Lusha and Nimble](https://www.stacksync.com/integrations/lusha-and-nimble) - [Lusha and Nutshell](https://www.stacksync.com/integrations/lusha-and-nutshell) - [Lusha and Oracle CX Sales](https://www.stacksync.com/integrations/lusha-and-oracle-cx-sales) - [Lusha and Outreach](https://www.stacksync.com/integrations/lusha-and-outreach) - [Lusha and Pipedrive](https://www.stacksync.com/integrations/lusha-and-pipedrive) - [Lusha and Salesforce](https://www.stacksync.com/integrations/lusha-and-salesforce) - [Lusha and Salesloft](https://www.stacksync.com/integrations/lusha-and-salesloft) - [Lusha and SAP Sales Cloud](https://www.stacksync.com/integrations/lusha-and-sap-sales-cloud) - [Lusha and Seismic](https://www.stacksync.com/integrations/lusha-and-seismic) - [Lusha and Shopify](https://www.stacksync.com/integrations/lusha-and-shopify) - [Lusha and Streak CRM](https://www.stacksync.com/integrations/lusha-and-streak-crm) - [Lusha and SugarCRM](https://www.stacksync.com/integrations/lusha-and-sugarcrm) - [Lusha and Twenty CRM](https://www.stacksync.com/integrations/lusha-and-twenty-crm) - [Lusha and Veeva CRM](https://www.stacksync.com/integrations/lusha-and-veeva-crm) - [Lusha and Vitally](https://www.stacksync.com/integrations/lusha-and-vitally) - [Lusha and Vtiger CRM](https://www.stacksync.com/integrations/lusha-and-vtiger-crm) - [Lusha and Xactly](https://www.stacksync.com/integrations/lusha-and-xactly) - [Lusha and Zoho CRM](https://www.stacksync.com/integrations/lusha-and-zoho-crm) - [Lusha and Zoho SalesIQ](https://www.stacksync.com/integrations/lusha-and-zoho-salesiq) ### ERP · 2 - [Lusha and NetSuite](https://www.stacksync.com/integrations/lusha-and-netsuite) - [Lusha and SAP](https://www.stacksync.com/integrations/lusha-and-sap) ### Database · 12 - [Lusha and Airtable](https://www.stacksync.com/integrations/airtable-and-lusha) - [Lusha and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-lusha) - [Lusha and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-lusha) - [Lusha and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-lusha) - [Lusha and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-lusha) - [Lusha and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-lusha) - [Lusha and JDBC](https://www.stacksync.com/integrations/jdbc-and-lusha) - [Lusha and MongoDB](https://www.stacksync.com/integrations/lusha-and-mongodb) - [Lusha and MySQL](https://www.stacksync.com/integrations/lusha-and-mysql) - [Lusha and PostgreSQL](https://www.stacksync.com/integrations/lusha-and-postgresql) - [Lusha and Reltio](https://www.stacksync.com/integrations/lusha-and-reltio) - [Lusha and SAP HANA](https://www.stacksync.com/integrations/lusha-and-sap-hana) ### Data warehouse · 26 - [Lusha and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-lusha) - [Lusha and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-lusha) - [Lusha and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-lusha) - [Lusha and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-lusha) - [Lusha and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-lusha) - [Lusha and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-lusha) - [Lusha and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-lusha) - [Lusha and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-lusha) - [Lusha and BigQuery](https://www.stacksync.com/integrations/bigquery-and-lusha) - [Lusha and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-lusha) - [Lusha and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-lusha) - [Lusha and Databricks](https://www.stacksync.com/integrations/databricks-and-lusha) - [Lusha and Dremio](https://www.stacksync.com/integrations/dremio-and-lusha) - [Lusha and Exasol](https://www.stacksync.com/integrations/exasol-and-lusha) - [Lusha and Firebolt](https://www.stacksync.com/integrations/firebolt-and-lusha) - [Lusha and IBM Netezza](https://www.stacksync.com/integrations/ibm-netezza-and-lusha) - [Lusha and Materialize](https://www.stacksync.com/integrations/lusha-and-materialize) - [Lusha and MotherDuck](https://www.stacksync.com/integrations/lusha-and-motherduck) - [Lusha and Rockset](https://www.stacksync.com/integrations/lusha-and-rockset) - [Lusha and Snowflake](https://www.stacksync.com/integrations/lusha-and-snowflake) - [Lusha and Starburst Enterprise](https://www.stacksync.com/integrations/lusha-and-starburst-enterprise) - [Lusha and StarRocks](https://www.stacksync.com/integrations/lusha-and-starrocks) - [Lusha and Teradata Vantage](https://www.stacksync.com/integrations/lusha-and-teradata-vantage) - [Lusha and Tinybird](https://www.stacksync.com/integrations/lusha-and-tinybird) - [Lusha and Vertica](https://www.stacksync.com/integrations/lusha-and-vertica) - [Lusha and Yellowbrick](https://www.stacksync.com/integrations/lusha-and-yellowbrick) ### Business productivity · 25 - [Lusha and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-lusha) - [Lusha and Agiloft](https://www.stacksync.com/integrations/agiloft-and-lusha) - [Lusha and Asana](https://www.stacksync.com/integrations/asana-and-lusha) - [Lusha and Braze](https://www.stacksync.com/integrations/braze-and-lusha) - [Lusha and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-lusha) - [Lusha and Customer.io](https://www.stacksync.com/integrations/customer-io-and-lusha) - [Lusha and Docusign](https://www.stacksync.com/integrations/docusign-and-lusha) - [Lusha and Front](https://www.stacksync.com/integrations/front-and-lusha) - [Lusha and Gainsight](https://www.stacksync.com/integrations/gainsight-and-lusha) - [Lusha and Gatekeeper](https://www.stacksync.com/integrations/gatekeeper-and-lusha) - [Lusha and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-lusha) - [Lusha and Ironclad](https://www.stacksync.com/integrations/ironclad-and-lusha) - [Lusha and Lemlist](https://www.stacksync.com/integrations/lemlist-and-lusha) - [Lusha and Microsoft Dynamics 365](https://www.stacksync.com/integrations/lusha-and-microsoft-dynamics-365) - [Lusha and Monday](https://www.stacksync.com/integrations/lusha-and-monday) - [Lusha and NextGen Healthcare](https://www.stacksync.com/integrations/lusha-and-nextgen-healthcare) - [Lusha and Notion](https://www.stacksync.com/integrations/lusha-and-notion) - [Lusha and Quip](https://www.stacksync.com/integrations/lusha-and-quip) - [Lusha and Resend](https://www.stacksync.com/integrations/lusha-and-resend) - [Lusha and SendGrid](https://www.stacksync.com/integrations/lusha-and-sendgrid) - [Lusha and ServiceMax](https://www.stacksync.com/integrations/lusha-and-servicemax) - [Lusha and Smartsheet](https://www.stacksync.com/integrations/lusha-and-smartsheet) - [Lusha and SysAid](https://www.stacksync.com/integrations/lusha-and-sysaid) - [Lusha and Wrike](https://www.stacksync.com/integrations/lusha-and-wrike) - [Lusha and Zendesk](https://www.stacksync.com/integrations/lusha-and-zendesk) ### Accounting and finance · 1 - [Lusha and Workday](https://www.stacksync.com/integrations/lusha-and-workday) ### Human resources · 13 - [Lusha and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-lusha) - [Lusha and D2L Brightspace](https://www.stacksync.com/integrations/d2l-brightspace-and-lusha) - [Lusha and Greenhouse](https://www.stacksync.com/integrations/greenhouse-and-lusha) - [Lusha and Hibob](https://www.stacksync.com/integrations/hibob-and-lusha) - [Lusha and Jobvite](https://www.stacksync.com/integrations/jobvite-and-lusha) - [Lusha and Lever](https://www.stacksync.com/integrations/lever-and-lusha) - [Lusha and Namely](https://www.stacksync.com/integrations/lusha-and-namely) - [Lusha and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/lusha-and-oracle-fusion-cloud-hcm) - [Lusha and Paylocity](https://www.stacksync.com/integrations/lusha-and-paylocity) - [Lusha and SmartRecruiters](https://www.stacksync.com/integrations/lusha-and-smartrecruiters) - [Lusha and Success Factors](https://www.stacksync.com/integrations/lusha-and-success-factors) - [Lusha and UKG Pro](https://www.stacksync.com/integrations/lusha-and-ukg-pro) - [Lusha and UKG Ready](https://www.stacksync.com/integrations/lusha-and-ukg-ready) ### Storage · 4 - [Lusha and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-lusha) - [Lusha and Box](https://www.stacksync.com/integrations/box-and-lusha) - [Lusha and Egnyte](https://www.stacksync.com/integrations/egnyte-and-lusha) - [Lusha and SharePoint](https://www.stacksync.com/integrations/lusha-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/)