--- title: "Lever connector: setup and compatibility | Stacksync" description: "Lever integration guide: plan Users and Opportunities, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/lever last_modified: 2026-09-15 --- Human resources · Two-way sync platform # Lever 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 Lever workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Users and Opportunities. 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. - **Opportunities** - **Postings** - **Requisitions** **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=lever) ## 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 ## Lever records to discuss. These Lever record examples help scope a technical review. They are not a list of verified Stacksync operations. Opportunities Keep the opportunity/deal ID separate from any later order or invoice ID. Postings Identify this record type and the operation you need to review with Stacksync. Requisitions Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Offers Identify this record type and the operation you need to review with Stacksync. Users Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Stages Identify this record type and the operation you need to review with Stacksync. Connection setup ## Lever connection requirements. Review Lever 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 Lever account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Lever, including read/write support, authentication, and initial-load limits. [Open the Lever vendor API reference](https://hire.lever.co/developer/documentation) ### Lever API reference - [Lever vendor API documentation](https://hire.lever.co/developer/documentation) Integration design ## Match records and fields for your Lever integration. Separate a person from employment records, assignments, and candidate applications. Decide how future-dated changes, transfers, and rehires reach downstream applications. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Lever **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 Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Load related records in the right order Resolve tenant and group references and establish a protected administrative-account policy. ### Mapping checks by record type #### Users Confirm object support with Stacksync Identity Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Fields to consider Source user ID · Tenant reference · Account status · Group references Related records to resolve first Resolve tenant and group references and establish a protected administrative-account policy. Test before going live Test a renamed login, disabled account, missing group, and a user existing in two tenants. #### Opportunities Confirm object support with Stacksync Identity Keep the opportunity/deal ID separate from any later order or invoice ID. Fields to consider Source deal ID · Stage · Amount and currency · Expected close date · Company reference Related records to resolve first Map the customer and sales pipeline before the opportunity; map stage values deliberately. Test before going live Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency. [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 Lever integration in four steps. A future-dated change takes effect at the agreed time; a rehire links to the correct person without duplicating their employment history. ### View the four setup tests and expected results 1. ### Confirm the intended Lever account and grant After confirming an implementation path, validate the selected access method with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity. **Expected result:** The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure. 2. ### Test record matching for Users Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a renamed login, disabled account, missing group, and a user existing in two tenants. **Expected result:** A future-dated change takes effect at the agreed time; a rehire links to the correct person without duplicating their employment history. 3. ### Test the operation your workflow needs Review one Lever 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 Lever integration. ### Diagnose record matching, delayed changes, and rejected operations A Lever record appears under the wrong destination record Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Resolve tenant and group references and establish a protected administrative-account policy. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Lever implementation’s change-detection method for Users and Opportunities. 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 Lever 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 Lever workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=lever) ## Lever 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 ## Lever connector FAQ ### How should I plan an integration with Lever? Separate a person from employment records, assignments, and candidate applications. Decide how future-dated changes, transfers, and rehires reach downstream applications. 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 Lever connector write changes back? Write-back support is not established for this connection. Review the Lever records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Lever data? Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. ### Which related records should I load first for Lever? Resolve tenant and group references and establish a protected administrative-account policy. ### How do I validate Lever changes after the initial load? Test a renamed login, disabled account, missing group, and a user existing in two tenants. A future-dated change takes effect at the agreed time; a rehire links to the correct person without duplicating their employment history. ### What will we cover in a Lever integration demo? Start with one workflow and a sample record from Users and Opportunities. 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 Lever 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 Lever and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Lever. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Lever record changes.” - “Create a Genie that answers questions about our Lever 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 Lever 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 - [Lever and Slack](https://www.stacksync.com/integrations/lever-and-slack) - [BambooHR and Lever](https://www.stacksync.com/integrations/bamboohr-and-lever) - [Lever and Rockset](https://www.stacksync.com/integrations/lever-and-rockset) - [Docusign and Lever](https://www.stacksync.com/integrations/docusign-and-lever) - [Lever and Workday](https://www.stacksync.com/integrations/lever-and-workday) - [Lever and Salesforce](https://www.stacksync.com/integrations/lever-and-salesforce) - [Lever and Twilio](https://www.stacksync.com/integrations/lever-and-twilio) - [Lever and ServiceNow](https://www.stacksync.com/integrations/lever-and-servicenow) ### CRM · 45 - [Lever and 6sense](https://www.stacksync.com/integrations/6sense-and-lever) - [Lever and Affinity](https://www.stacksync.com/integrations/affinity-and-lever) - [Lever and Apollo.io](https://www.stacksync.com/integrations/apollo-io-and-lever) - [Lever and Attio](https://www.stacksync.com/integrations/attio-and-lever) - [Lever and Chorusai](https://www.stacksync.com/integrations/chorusai-and-lever) - [Lever and Clari](https://www.stacksync.com/integrations/clari-and-lever) - [Lever and Clearbit](https://www.stacksync.com/integrations/clearbit-and-lever) - [Lever and Close](https://www.stacksync.com/integrations/close-and-lever) - [Lever and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-lever) - [Lever and Creatio CRM](https://www.stacksync.com/integrations/creatio-crm-and-lever) - [Lever and DealCloud](https://www.stacksync.com/integrations/dealcloud-and-lever) - [Lever and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-lever) - [Lever and Folk CRM](https://www.stacksync.com/integrations/folk-crm-and-lever) - [Lever and Freshsales](https://www.stacksync.com/integrations/freshsales-and-lever) - [Lever and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-lever) - [Lever and Gladly](https://www.stacksync.com/integrations/gladly-and-lever) - [Lever and Gong](https://www.stacksync.com/integrations/gong-and-lever) - [Lever and Gorgias](https://www.stacksync.com/integrations/gorgias-and-lever) - [Lever and HubSpot](https://www.stacksync.com/integrations/hubspot-and-lever) - [Lever and Infor CRM](https://www.stacksync.com/integrations/infor-crm-and-lever) - [Lever and Insightly](https://www.stacksync.com/integrations/insightly-and-lever) - [Lever and Intercom](https://www.stacksync.com/integrations/intercom-and-lever) - [Lever and Kommo](https://www.stacksync.com/integrations/kommo-and-lever) - [Lever and Kustomer](https://www.stacksync.com/integrations/kustomer-and-lever) - [Lever and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/lever-and-microsoft-dynamics-365-sales) - [Lever and Nimble](https://www.stacksync.com/integrations/lever-and-nimble) - [Lever and Nutshell](https://www.stacksync.com/integrations/lever-and-nutshell) - [Lever and Oracle CX Sales](https://www.stacksync.com/integrations/lever-and-oracle-cx-sales) - [Lever and Outreach](https://www.stacksync.com/integrations/lever-and-outreach) - [Lever and Pipedrive](https://www.stacksync.com/integrations/lever-and-pipedrive) - [Lever and Salesforce](https://www.stacksync.com/integrations/lever-and-salesforce) - [Lever and Salesloft](https://www.stacksync.com/integrations/lever-and-salesloft) - [Lever and SAP Sales Cloud](https://www.stacksync.com/integrations/lever-and-sap-sales-cloud) - [Lever and Seismic](https://www.stacksync.com/integrations/lever-and-seismic) - [Lever and Shopify](https://www.stacksync.com/integrations/lever-and-shopify) - [Lever and Streak CRM](https://www.stacksync.com/integrations/lever-and-streak-crm) - [Lever and SugarCRM](https://www.stacksync.com/integrations/lever-and-sugarcrm) - [Lever and Twenty CRM](https://www.stacksync.com/integrations/lever-and-twenty-crm) - [Lever and Veeva CRM](https://www.stacksync.com/integrations/lever-and-veeva-crm) - [Lever and Vitally](https://www.stacksync.com/integrations/lever-and-vitally) - [Lever and Vtiger CRM](https://www.stacksync.com/integrations/lever-and-vtiger-crm) - [Lever and Xactly](https://www.stacksync.com/integrations/lever-and-xactly) - [Lever and Zoho CRM](https://www.stacksync.com/integrations/lever-and-zoho-crm) - [Lever and Zoho SalesIQ](https://www.stacksync.com/integrations/lever-and-zoho-salesiq) - [Lever and ZoomInfo](https://www.stacksync.com/integrations/lever-and-zoominfo) ### ERP · 38 - [Lever and Acumatica](https://www.stacksync.com/integrations/acumatica-and-lever) - [Lever and Blue Yonder WMS](https://www.stacksync.com/integrations/blue-yonder-wms-and-lever) - [Lever and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-lever) - [Lever and Cin7](https://www.stacksync.com/integrations/cin7-and-lever) - [Lever and DEAR Inventory](https://www.stacksync.com/integrations/dear-inventory-and-lever) - [Lever and Dynamics 365 Business Central](https://www.stacksync.com/integrations/lever-and-microsoft-dynamics-365-business-central) - [Lever and Dynamics 365 F&O](https://www.stacksync.com/integrations/dynamics-365-finance-operations-and-lever) - [Lever and Epicor ERP](https://www.stacksync.com/integrations/epicor-erp-and-lever) - [Lever and Extensiv (3PL Central)](https://www.stacksync.com/integrations/extensiv-3pl-central-and-lever) - [Lever and Fishbowl Manufacturing](https://www.stacksync.com/integrations/fishbowl-manufacturing-and-lever) - [Lever and Infor CloudSuite](https://www.stacksync.com/integrations/infor-cloudsuite-and-lever) - [Lever and Infor LN](https://www.stacksync.com/integrations/infor-ln-and-lever) - [Lever and Infor M3](https://www.stacksync.com/integrations/infor-m3-and-lever) - [Lever and Infor WMS](https://www.stacksync.com/integrations/infor-wms-and-lever) - [Lever and Linnworks](https://www.stacksync.com/integrations/lever-and-linnworks) - [Lever and Logiwa WMS](https://www.stacksync.com/integrations/lever-and-logiwa-wms) - [Lever and Macola ERP](https://www.stacksync.com/integrations/lever-and-macola-erp) - [Lever and Manhattan Associates WMS](https://www.stacksync.com/integrations/lever-and-manhattan-associates-wms) - [Lever and Microsoft Dynamics GP](https://www.stacksync.com/integrations/lever-and-microsoft-dynamics-gp) - [Lever and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/lever-and-microsoft-dynamics-nav) - [Lever and NetSuite](https://www.stacksync.com/integrations/lever-and-netsuite) - [Lever and Odoo](https://www.stacksync.com/integrations/lever-and-odoo) - [Lever and Oracle Fusion ERP](https://www.stacksync.com/integrations/lever-and-oracle-fusion-erp) - [Lever and Plex ERP](https://www.stacksync.com/integrations/lever-and-plex-erp) - [Lever and QAD ERP](https://www.stacksync.com/integrations/lever-and-qad-erp) - [Lever and Rootstock ERP](https://www.stacksync.com/integrations/lever-and-rootstock-erp) - [Lever and Sage 100](https://www.stacksync.com/integrations/lever-and-sage-100) - [Lever and Sage 300](https://www.stacksync.com/integrations/lever-and-sage-300) - [Lever and Sage Intacct](https://www.stacksync.com/integrations/lever-and-sage-intacct) - [Lever and Sage X3](https://www.stacksync.com/integrations/lever-and-sage-x3) - [Lever and SAP](https://www.stacksync.com/integrations/lever-and-sap) - [Lever and SAP Business ByDesign](https://www.stacksync.com/integrations/lever-and-sap-business-bydesign) - [Lever and SAP Business One](https://www.stacksync.com/integrations/lever-and-sap-business-one) - [Lever and SAP S/4HANA](https://www.stacksync.com/integrations/lever-and-sap-s4hana) - [Lever and SuiteAnalytics](https://www.stacksync.com/integrations/lever-and-suite-analytics) - [Lever and Syspro](https://www.stacksync.com/integrations/lever-and-syspro) - [Lever and TikTok Shop](https://www.stacksync.com/integrations/lever-and-tiktok) - [Lever and Unleashed Software](https://www.stacksync.com/integrations/lever-and-unleashed-software) ### Database · 50 - [Lever and Airtable](https://www.stacksync.com/integrations/airtable-and-lever) - [Lever and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-lever) - [Lever and Amazon DynamoDB](https://www.stacksync.com/integrations/dynamo-db-and-lever) - [Lever and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-lever) - [Lever and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-lever) - [Lever and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-lever) - [Lever and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-lever) - [Lever and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-lever) - [Lever and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-lever) - [Lever and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-lever) - [Lever and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-lever) - [Lever and Citus](https://www.stacksync.com/integrations/citus-and-lever) - [Lever and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-lever) - [Lever and Couchbase](https://www.stacksync.com/integrations/couchbase-and-lever) - [Lever and DuckDB](https://www.stacksync.com/integrations/duckdb-and-lever) - [Lever and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-lever) - [Lever and Firebase](https://www.stacksync.com/integrations/firebase-and-lever) - [Lever and Google AlloyDB](https://www.stacksync.com/integrations/google-alloydb-and-lever) - [Lever and Google Cloud Spanner](https://www.stacksync.com/integrations/google-cloud-spanner-and-lever) - [Lever and Google Cloud SQL](https://www.stacksync.com/integrations/google-cloud-sql-and-lever) - [Lever and IBM AS/400](https://www.stacksync.com/integrations/ibm-as400-and-lever) - [Lever and IBM Db2](https://www.stacksync.com/integrations/ibm-db2-and-lever) - [Lever and IBM Informix](https://www.stacksync.com/integrations/ibm-informix-and-lever) - [Lever and InfluxDB](https://www.stacksync.com/integrations/influxdb-and-lever) - [Lever and InterSystems IRIS](https://www.stacksync.com/integrations/intersystems-iris-and-lever) - [Lever and JDBC](https://www.stacksync.com/integrations/jdbc-and-lever) - [Lever and MariaDB](https://www.stacksync.com/integrations/lever-and-mariadb) - [Lever and MarkLogic](https://www.stacksync.com/integrations/lever-and-marklogic) - [Lever and MongoDB](https://www.stacksync.com/integrations/lever-and-mongodb) - [Lever and MySQL](https://www.stacksync.com/integrations/lever-and-mysql) - [Lever and Neo4j](https://www.stacksync.com/integrations/lever-and-neo4j) - [Lever and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/lever-and-oci-database) - [Lever and OpenSearch](https://www.stacksync.com/integrations/lever-and-opensearch) - [Lever and Oracle DB](https://www.stacksync.com/integrations/lever-and-oracle-db) - [Lever and Postgres Heroku](https://www.stacksync.com/integrations/lever-and-postgres-heroku) - [Lever and PostgreSQL](https://www.stacksync.com/integrations/lever-and-postgresql) - [Lever and RavenDB](https://www.stacksync.com/integrations/lever-and-ravendb) - [Lever and Redis Enterprise](https://www.stacksync.com/integrations/lever-and-redis-enterprise) - [Lever and Reltio](https://www.stacksync.com/integrations/lever-and-reltio) - [Lever and Render Postgres](https://www.stacksync.com/integrations/lever-and-render-postgres) - [Lever and SAP ASE (Sybase)](https://www.stacksync.com/integrations/lever-and-sap-ase-sybase) - [Lever and SAP HANA](https://www.stacksync.com/integrations/lever-and-sap-hana) - [Lever and Scaleway Postgres](https://www.stacksync.com/integrations/lever-and-scaleway-postgres) - [Lever and SingleStore](https://www.stacksync.com/integrations/lever-and-singlestore) - [Lever and SQL Server](https://www.stacksync.com/integrations/lever-and-sql-server) - [Lever and Supabase](https://www.stacksync.com/integrations/lever-and-supabase) - [Lever and TiDB](https://www.stacksync.com/integrations/lever-and-tidb) - [Lever and TimescaleDB](https://www.stacksync.com/integrations/lever-and-timescaledb) - [Lever and VoltDB](https://www.stacksync.com/integrations/lever-and-voltdb) - [Lever and YugabyteDB](https://www.stacksync.com/integrations/lever-and-yugabytedb) ### Data warehouse · 29 - [Lever and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-lever) - [Lever and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-lever) - [Lever and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-lever) - [Lever and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-lever) - [Lever and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-lever) - [Lever and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-lever) - [Lever and Apache Kylin](https://www.stacksync.com/integrations/apache-kylin-and-lever) - [Lever and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-lever) - [Lever and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-lever) - [Lever and BigQuery](https://www.stacksync.com/integrations/bigquery-and-lever) - [Lever and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-lever) - [Lever and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-lever) - [Lever and Databricks](https://www.stacksync.com/integrations/databricks-and-lever) - [Lever and Dremio](https://www.stacksync.com/integrations/dremio-and-lever) - [Lever and Exasol](https://www.stacksync.com/integrations/exasol-and-lever) - [Lever and Firebolt](https://www.stacksync.com/integrations/firebolt-and-lever) - [Lever and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-lever) - [Lever and Greenplum](https://www.stacksync.com/integrations/greenplum-and-lever) - [Lever and IBM Netezza](https://www.stacksync.com/integrations/ibm-netezza-and-lever) - [Lever and Materialize](https://www.stacksync.com/integrations/lever-and-materialize) - [Lever and MotherDuck](https://www.stacksync.com/integrations/lever-and-motherduck) - [Lever and Rockset](https://www.stacksync.com/integrations/lever-and-rockset) - [Lever and Snowflake](https://www.stacksync.com/integrations/lever-and-snowflake) - [Lever and Starburst Enterprise](https://www.stacksync.com/integrations/lever-and-starburst-enterprise) - [Lever and StarRocks](https://www.stacksync.com/integrations/lever-and-starrocks) - [Lever and Teradata Vantage](https://www.stacksync.com/integrations/lever-and-teradata-vantage) - [Lever and Tinybird](https://www.stacksync.com/integrations/lever-and-tinybird) - [Lever and Vertica](https://www.stacksync.com/integrations/lever-and-vertica) - [Lever and Yellowbrick](https://www.stacksync.com/integrations/lever-and-yellowbrick) ### Business productivity · 40 - [Lever and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-lever) - [Lever and Agiloft](https://www.stacksync.com/integrations/agiloft-and-lever) - [Lever and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-lever) - [Lever and Asana](https://www.stacksync.com/integrations/asana-and-lever) - [Lever and Atlassian](https://www.stacksync.com/integrations/atlassian-and-lever) - [Lever and BetterContact](https://www.stacksync.com/integrations/better-contact-and-lever) - [Lever and Braze](https://www.stacksync.com/integrations/braze-and-lever) - [Lever and Campfire](https://www.stacksync.com/integrations/campfire-and-lever) - [Lever and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-lever) - [Lever and Customer.io](https://www.stacksync.com/integrations/customer-io-and-lever) - [Lever and Docusign](https://www.stacksync.com/integrations/docusign-and-lever) - [Lever and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-lever) - [Lever and Front](https://www.stacksync.com/integrations/front-and-lever) - [Lever and FullEnrich](https://www.stacksync.com/integrations/full-enrich-and-lever) - [Lever and Gainsight](https://www.stacksync.com/integrations/gainsight-and-lever) - [Lever and Gatekeeper](https://www.stacksync.com/integrations/gatekeeper-and-lever) - [Lever and GitHub](https://www.stacksync.com/integrations/github-and-lever) - [Lever and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-lever) - [Lever and Ironclad](https://www.stacksync.com/integrations/ironclad-and-lever) - [Lever and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-lever) - [Lever and Lemlist](https://www.stacksync.com/integrations/lemlist-and-lever) - [Lever and Lusha](https://www.stacksync.com/integrations/lever-and-lusha) - [Lever and Microsoft 365](https://www.stacksync.com/integrations/lever-and-microsoft-365) - [Lever and Microsoft Dynamics 365](https://www.stacksync.com/integrations/lever-and-microsoft-dynamics-365) - [Lever and Microsoft Teams](https://www.stacksync.com/integrations/lever-and-microsoft-teams) - [Lever and Monday](https://www.stacksync.com/integrations/lever-and-monday) - [Lever and NextGen Healthcare](https://www.stacksync.com/integrations/lever-and-nextgen-healthcare) - [Lever and Notion](https://www.stacksync.com/integrations/lever-and-notion) - [Lever and Orderful](https://www.stacksync.com/integrations/lever-and-orderful) - [Lever and Quip](https://www.stacksync.com/integrations/lever-and-quip) - [Lever and Resend](https://www.stacksync.com/integrations/lever-and-resend) - [Lever and SendGrid](https://www.stacksync.com/integrations/lever-and-sendgrid) - [Lever and ServiceMax](https://www.stacksync.com/integrations/lever-and-servicemax) - [Lever and ServiceNow](https://www.stacksync.com/integrations/lever-and-servicenow) - [Lever and Slack](https://www.stacksync.com/integrations/lever-and-slack) - [Lever and Smartsheet](https://www.stacksync.com/integrations/lever-and-smartsheet) - [Lever and SysAid](https://www.stacksync.com/integrations/lever-and-sysaid) - [Lever and Twilio](https://www.stacksync.com/integrations/lever-and-twilio) - [Lever and Wrike](https://www.stacksync.com/integrations/lever-and-wrike) - [Lever and Zendesk](https://www.stacksync.com/integrations/lever-and-zendesk) ### Accounting and finance · 17 - [Lever and Adyen](https://www.stacksync.com/integrations/adyen-and-lever) - [Lever and Anaplan](https://www.stacksync.com/integrations/anaplan-and-lever) - [Lever and BILL](https://www.stacksync.com/integrations/bill-and-lever) - [Lever and Braintree](https://www.stacksync.com/integrations/braintree-and-lever) - [Lever and Chargebee](https://www.stacksync.com/integrations/chargebee-and-lever) - [Lever and Coupa](https://www.stacksync.com/integrations/coupa-and-lever) - [Lever and Hyperline](https://www.stacksync.com/integrations/hyperline-and-lever) - [Lever and LogiSense](https://www.stacksync.com/integrations/lever-and-logisense) - [Lever and Navan](https://www.stacksync.com/integrations/lever-and-navan) - [Lever and Pigment](https://www.stacksync.com/integrations/lever-and-pigment) - [Lever and QuickBooks](https://www.stacksync.com/integrations/lever-and-quickbooks) - [Lever and Ramp](https://www.stacksync.com/integrations/lever-and-ramp) - [Lever and Recurly](https://www.stacksync.com/integrations/lever-and-recurly) - [Lever and Rillet](https://www.stacksync.com/integrations/lever-and-rillet) - [Lever and Stripe](https://www.stacksync.com/integrations/lever-and-stripe) - [Lever and Workday](https://www.stacksync.com/integrations/lever-and-workday) - [Lever and Zuora](https://www.stacksync.com/integrations/lever-and-zuora) ### AI · 5 - [Lever and Anthropic](https://www.stacksync.com/integrations/anthropic-and-lever) - [Lever and Autopilot](https://www.stacksync.com/integrations/autopilot-and-lever) - [Lever and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-lever) - [Lever and OpenAI](https://www.stacksync.com/integrations/lever-and-openai) - [Lever and Pinecone](https://www.stacksync.com/integrations/lever-and-pinecone) ### Analytics · 7 - [Lever and Adobe Analytics](https://www.stacksync.com/integrations/adobeanalytics-and-lever) - [Lever and Microsoft Power BI](https://www.stacksync.com/integrations/lever-and-microsoft-power-bi) - [Lever and Mixpanel](https://www.stacksync.com/integrations/lever-and-mixpanel) - [Lever and Pendo](https://www.stacksync.com/integrations/lever-and-pendo) - [Lever and Splunk](https://www.stacksync.com/integrations/lever-and-splunk) - [Lever and Tableau](https://www.stacksync.com/integrations/lever-and-tableau) - [Lever and Treasure Data](https://www.stacksync.com/integrations/lever-and-treasuredata) ### Human resources · 13 - [Lever and BambooHR](https://www.stacksync.com/integrations/bamboohr-and-lever) - [Lever and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-lever) - [Lever and D2L Brightspace](https://www.stacksync.com/integrations/d2l-brightspace-and-lever) - [Lever and Greenhouse](https://www.stacksync.com/integrations/greenhouse-and-lever) - [Lever and Hibob](https://www.stacksync.com/integrations/hibob-and-lever) - [Lever and Jobvite](https://www.stacksync.com/integrations/jobvite-and-lever) - [Lever and Namely](https://www.stacksync.com/integrations/lever-and-namely) - [Lever and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/lever-and-oracle-fusion-cloud-hcm) - [Lever and Paylocity](https://www.stacksync.com/integrations/lever-and-paylocity) - [Lever and SmartRecruiters](https://www.stacksync.com/integrations/lever-and-smartrecruiters) - [Lever and Success Factors](https://www.stacksync.com/integrations/lever-and-success-factors) - [Lever and UKG Pro](https://www.stacksync.com/integrations/lever-and-ukg-pro) - [Lever and UKG Ready](https://www.stacksync.com/integrations/lever-and-ukg-ready) ### Security and identity · 6 - [Lever and Active Directory](https://www.stacksync.com/integrations/active-directory-and-lever) - [Lever and Auth0](https://www.stacksync.com/integrations/auth0-and-lever) - [Lever and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-lever) - [Lever and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-lever) - [Lever and Okta](https://www.stacksync.com/integrations/lever-and-okta) - [Lever and OneLogin](https://www.stacksync.com/integrations/lever-and-onelogin) ### Storage · 4 - [Lever and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-lever) - [Lever and Box](https://www.stacksync.com/integrations/box-and-lever) - [Lever and Egnyte](https://www.stacksync.com/integrations/egnyte-and-lever) - [Lever and SharePoint](https://www.stacksync.com/integrations/lever-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/)