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