--- title: "GitHub connector: setup and compatibility | Stacksync" description: "GitHub integration guide: plan Issues and Organizations and Teams, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/github last_modified: 2026-09-15 --- Business productivity · Two-way sync platform # GitHub 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 GitHub workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Issues, Organizations and Teams 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. - **Repositories** - **Issues** - **Pull Requests** **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=github) ## 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 ## GitHub records to discuss. These GitHub record examples help scope a technical review. They are not a list of verified Stacksync operations. Repositories Identify this record type and the operation you need to review with Stacksync. Issues Use a stable task/work-item ID and preserve its project or parent-ticket reference. Pull Requests Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Commits Identify this record type and the operation you need to review with Stacksync. Releases Identify this record type and the operation you need to review with Stacksync. Workflow runs (Actions) Identify this record type and the operation you need to review with Stacksync. Connection setup ## GitHub connection requirements. Review GitHub 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 GitHub account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for GitHub, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your GitHub integration. Define repository/project context, issue or change identity, and relationships to operational records. Moving metadata does not authorize a code change, build, or deployment. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks GitHub **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 a stable task/work-item ID and preserve its project or parent-ticket reference. Load related records in the right order Resolve project, user, and parent-item references before the task. ### Mapping checks by record type #### Issues Confirm object support with Stacksync Identity Use a stable task/work-item ID and preserve its project or parent-ticket reference. Fields to consider Source task ID · Parent reference · Assignee · Status · Due date Related records to resolve first Resolve project, user, and parent-item references before the task. Test before going live Test a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones. #### Organizations and Teams Confirm object support with Stacksync Identity Keep group IDs and membership relationships separately from group names. Fields to consider Source group ID · Member references · Tenant reference · Group type Related records to resolve first Resolve user and tenant identities before membership changes. Test before going live Test removed membership, nested groups, and equal group names in different tenants. #### 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 GitHub integration in four steps. A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action. ### View the four setup tests and expected results 1. ### Confirm the intended GitHub 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 Issues Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones. **Expected result:** A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action. 3. ### Test the operation your workflow needs Review one GitHub 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 GitHub integration. ### Diagnose record matching, delayed changes, and rejected operations A GitHub record appears under the wrong destination record Use a stable task/work-item ID and preserve its project or parent-ticket reference. Resolve project, user, and parent-item references before the task. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected GitHub implementation’s change-detection method for Issues, Organizations and Teams 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 GitHub 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 GitHub workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=github) ## GitHub 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) - [article GitHub Into Snowflake Is Solved. The Trip Back Is Not.](https://www.stacksync.com/blog/two-way-sync-github-snowflake) FAQ ## GitHub connector FAQ ### How should I plan an integration with GitHub? Define repository/project context, issue or change identity, and relationships to operational records. Moving metadata does not authorize a code change, build, or deployment. 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 GitHub connector write changes back? Write-back support is not established for this connection. Review the GitHub records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for GitHub data? Use a stable task/work-item ID and preserve its project or parent-ticket reference. ### Which related records should I load first for GitHub? Resolve project, user, and parent-item references before the task. ### How do I validate GitHub changes after the initial load? Test a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones. A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action. ### What will we cover in a GitHub integration demo? Start with one workflow and a sample record from Issues, Organizations and Teams 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 GitHub 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 GitHub and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use GitHub. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a GitHub record changes.” - “Create a Genie that answers questions about our GitHub 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. AI assistant setup ## Use GitHub through Stacksync MCP. [Explore capabilities and setup →](https://www.stacksync.com/mcp/github) - [Claude guide ↗](https://www.stacksync.com/mcp/github/claude) - [Claude Code guide ↗](https://www.stacksync.com/mcp/github/claude-code) - [ChatGPT guide ↗](https://www.stacksync.com/mcp/github/chatgpt) ## Explore GitHub 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 - [Datadog and GitHub](https://www.stacksync.com/integrations/datadog-and-github) - [GitHub and Notion](https://www.stacksync.com/integrations/github-and-notion) - [GitHub and Jira](https://www.stacksync.com/integrations/github-and-jira) - [GitHub and Slack](https://www.stacksync.com/integrations/github-and-slack) - [GitHub and HubSpot](https://www.stacksync.com/integrations/github-and-hubspot) - [Asana and GitHub](https://www.stacksync.com/integrations/asana-and-github) - [GitHub and Supabase](https://www.stacksync.com/integrations/github-and-supabase) - [GitHub and Google Sheets](https://www.stacksync.com/integrations/github-and-google-sheets) ### CRM · 28 - [GitHub and Affinity](https://www.stacksync.com/integrations/affinity-and-github) - [GitHub and Attio](https://www.stacksync.com/integrations/attio-and-github) - [GitHub and Chorusai](https://www.stacksync.com/integrations/chorusai-and-github) - [GitHub and Clari](https://www.stacksync.com/integrations/clari-and-github) - [GitHub and Close](https://www.stacksync.com/integrations/close-and-github) - [GitHub and DealCloud](https://www.stacksync.com/integrations/dealcloud-and-github) - [GitHub and Drift](https://www.stacksync.com/integrations/drift-and-github) - [GitHub and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-github) - [GitHub and Gladly](https://www.stacksync.com/integrations/github-and-gladly) - [GitHub and Gong](https://www.stacksync.com/integrations/github-and-gong) - [GitHub and Gorgias](https://www.stacksync.com/integrations/github-and-gorgias) - [GitHub and HubSpot](https://www.stacksync.com/integrations/github-and-hubspot) - [GitHub and Intercom](https://www.stacksync.com/integrations/github-and-intercom) - [GitHub and Kommo](https://www.stacksync.com/integrations/github-and-kommo) - [GitHub and Kustomer](https://www.stacksync.com/integrations/github-and-kustomer) - [GitHub and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/github-and-microsoft-dynamics-365-sales) - [GitHub and Outreach](https://www.stacksync.com/integrations/github-and-outreach) - [GitHub and Pipedrive](https://www.stacksync.com/integrations/github-and-pipedrive) - [GitHub and Salesforce](https://www.stacksync.com/integrations/github-and-salesforce) - [GitHub and Seismic](https://www.stacksync.com/integrations/github-and-seismic) - [GitHub and Shopify](https://www.stacksync.com/integrations/github-and-shopify) - [GitHub and Streak CRM](https://www.stacksync.com/integrations/github-and-streak-crm) - [GitHub and Twenty CRM](https://www.stacksync.com/integrations/github-and-twenty-crm) - [GitHub and Vitally](https://www.stacksync.com/integrations/github-and-vitally) - [GitHub and Vtiger CRM](https://www.stacksync.com/integrations/github-and-vtiger-crm) - [GitHub and Xactly](https://www.stacksync.com/integrations/github-and-xactly) - [GitHub and Zoho CRM](https://www.stacksync.com/integrations/github-and-zoho-crm) - [GitHub and Zoho SalesIQ](https://www.stacksync.com/integrations/github-and-zoho-salesiq) ### ERP · 14 - [GitHub and Acumatica](https://www.stacksync.com/integrations/acumatica-and-github) - [GitHub and Deposco](https://www.stacksync.com/integrations/deposco-and-github) - [GitHub and Dynamics 365 Business Central](https://www.stacksync.com/integrations/github-and-microsoft-dynamics-365-business-central) - [GitHub and Fishbowl Manufacturing](https://www.stacksync.com/integrations/fishbowl-manufacturing-and-github) - [GitHub and Linnworks](https://www.stacksync.com/integrations/github-and-linnworks) - [GitHub and Manhattan Associates WMS](https://www.stacksync.com/integrations/github-and-manhattan-associates-wms) - [GitHub and NetSuite](https://www.stacksync.com/integrations/github-and-netsuite) - [GitHub and Odoo](https://www.stacksync.com/integrations/github-and-odoo) - [GitHub and Oracle Fusion ERP](https://www.stacksync.com/integrations/github-and-oracle-fusion-erp) - [GitHub and QAD ERP](https://www.stacksync.com/integrations/github-and-qad-erp) - [GitHub and SAP](https://www.stacksync.com/integrations/github-and-sap) - [GitHub and SAP Business One](https://www.stacksync.com/integrations/github-and-sap-business-one) - [GitHub and SAP S/4HANA](https://www.stacksync.com/integrations/github-and-sap-s4hana) - [GitHub and TikTok Shop](https://www.stacksync.com/integrations/github-and-tiktok) ### Database · 42 - [GitHub and Airtable](https://www.stacksync.com/integrations/airtable-and-github) - [GitHub and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-github) - [GitHub and Amazon DynamoDB](https://www.stacksync.com/integrations/dynamo-db-and-github) - [GitHub and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-github) - [GitHub and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-github) - [GitHub and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-github) - [GitHub and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-github) - [GitHub and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-github) - [GitHub and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-github) - [GitHub and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-github) - [GitHub and Citus](https://www.stacksync.com/integrations/citus-and-github) - [GitHub and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-github) - [GitHub and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-github) - [GitHub and Firebase](https://www.stacksync.com/integrations/firebase-and-github) - [GitHub and Google AlloyDB](https://www.stacksync.com/integrations/github-and-google-alloydb) - [GitHub and Google Cloud Spanner](https://www.stacksync.com/integrations/github-and-google-cloud-spanner) - [GitHub and Google Cloud SQL](https://www.stacksync.com/integrations/github-and-google-cloud-sql) - [GitHub and IBM AS/400](https://www.stacksync.com/integrations/github-and-ibm-as400) - [GitHub and IBM Db2](https://www.stacksync.com/integrations/github-and-ibm-db2) - [GitHub and IBM Informix](https://www.stacksync.com/integrations/github-and-ibm-informix) - [GitHub and InterSystems IRIS](https://www.stacksync.com/integrations/github-and-intersystems-iris) - [GitHub and JDBC](https://www.stacksync.com/integrations/github-and-jdbc) - [GitHub and MariaDB](https://www.stacksync.com/integrations/github-and-mariadb) - [GitHub and MarkLogic](https://www.stacksync.com/integrations/github-and-marklogic) - [GitHub and MongoDB](https://www.stacksync.com/integrations/github-and-mongodb) - [GitHub and MySQL](https://www.stacksync.com/integrations/github-and-mysql) - [GitHub and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/github-and-oci-database) - [GitHub and Oracle DB](https://www.stacksync.com/integrations/github-and-oracle-db) - [GitHub and Postgres Heroku](https://www.stacksync.com/integrations/github-and-postgres-heroku) - [GitHub and PostgreSQL](https://www.stacksync.com/integrations/github-and-postgresql) - [GitHub and RavenDB](https://www.stacksync.com/integrations/github-and-ravendb) - [GitHub and Reltio](https://www.stacksync.com/integrations/github-and-reltio) - [GitHub and Render Postgres](https://www.stacksync.com/integrations/github-and-render-postgres) - [GitHub and SAP ASE (Sybase)](https://www.stacksync.com/integrations/github-and-sap-ase-sybase) - [GitHub and SAP HANA](https://www.stacksync.com/integrations/github-and-sap-hana) - [GitHub and Scaleway Postgres](https://www.stacksync.com/integrations/github-and-scaleway-postgres) - [GitHub and SingleStore](https://www.stacksync.com/integrations/github-and-singlestore) - [GitHub and SQL Server](https://www.stacksync.com/integrations/github-and-sql-server) - [GitHub and Supabase](https://www.stacksync.com/integrations/github-and-supabase) - [GitHub and TiDB](https://www.stacksync.com/integrations/github-and-tidb) - [GitHub and VoltDB](https://www.stacksync.com/integrations/github-and-voltdb) - [GitHub and YugabyteDB](https://www.stacksync.com/integrations/github-and-yugabytedb) ### Data warehouse · 30 - [GitHub and Actian Vector](https://www.stacksync.com/integrations/actian-vector-and-github) - [GitHub and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-github) - [GitHub and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-github) - [GitHub and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-github) - [GitHub and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-github) - [GitHub and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-github) - [GitHub and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-github) - [GitHub and Apache Kylin](https://www.stacksync.com/integrations/apache-kylin-and-github) - [GitHub and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-github) - [GitHub and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-github) - [GitHub and BigQuery](https://www.stacksync.com/integrations/bigquery-and-github) - [GitHub and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-github) - [GitHub and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-github) - [GitHub and Databricks](https://www.stacksync.com/integrations/databricks-and-github) - [GitHub and Dremio](https://www.stacksync.com/integrations/dremio-and-github) - [GitHub and Exasol](https://www.stacksync.com/integrations/exasol-and-github) - [GitHub and Firebolt](https://www.stacksync.com/integrations/firebolt-and-github) - [GitHub and Google Cloud Platform](https://www.stacksync.com/integrations/github-and-google-cloud-platform) - [GitHub and Greenplum](https://www.stacksync.com/integrations/github-and-greenplum) - [GitHub and IBM Netezza](https://www.stacksync.com/integrations/github-and-ibm-netezza) - [GitHub and Materialize](https://www.stacksync.com/integrations/github-and-materialize) - [GitHub and MotherDuck](https://www.stacksync.com/integrations/github-and-motherduck) - [GitHub and Rockset](https://www.stacksync.com/integrations/github-and-rockset) - [GitHub and Snowflake](https://www.stacksync.com/integrations/github-and-snowflake) - [GitHub and Starburst Enterprise](https://www.stacksync.com/integrations/github-and-starburst-enterprise) - [GitHub and StarRocks](https://www.stacksync.com/integrations/github-and-starrocks) - [GitHub and Teradata Vantage](https://www.stacksync.com/integrations/github-and-teradata-vantage) - [GitHub and Tinybird](https://www.stacksync.com/integrations/github-and-tinybird) - [GitHub and Vertica](https://www.stacksync.com/integrations/github-and-vertica) - [GitHub and Yellowbrick](https://www.stacksync.com/integrations/github-and-yellowbrick) ### Business productivity · 36 - [GitHub and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-github) - [GitHub and Agiloft](https://www.stacksync.com/integrations/agiloft-and-github) - [GitHub and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-github) - [GitHub and Asana](https://www.stacksync.com/integrations/asana-and-github) - [GitHub and Atlassian](https://www.stacksync.com/integrations/atlassian-and-github) - [GitHub and Aviato](https://www.stacksync.com/integrations/aviato-and-github) - [GitHub and Campfire](https://www.stacksync.com/integrations/campfire-and-github) - [GitHub and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-github) - [GitHub and Customer.io](https://www.stacksync.com/integrations/customer-io-and-github) - [GitHub and Docusign](https://www.stacksync.com/integrations/docusign-and-github) - [GitHub and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-github) - [GitHub and Front](https://www.stacksync.com/integrations/front-and-github) - [GitHub and FullEnrich](https://www.stacksync.com/integrations/full-enrich-and-github) - [GitHub and Gainsight](https://www.stacksync.com/integrations/gainsight-and-github) - [GitHub and Gatekeeper](https://www.stacksync.com/integrations/gatekeeper-and-github) - [GitHub and Google Sheets](https://www.stacksync.com/integrations/github-and-google-sheets) - [GitHub and Ironclad](https://www.stacksync.com/integrations/github-and-ironclad) - [GitHub and Klaviyo](https://www.stacksync.com/integrations/github-and-klaviyo) - [GitHub and Lemlist](https://www.stacksync.com/integrations/github-and-lemlist) - [GitHub and Microsoft 365](https://www.stacksync.com/integrations/github-and-microsoft-365) - [GitHub and Microsoft Dynamics 365](https://www.stacksync.com/integrations/github-and-microsoft-dynamics-365) - [GitHub and Microsoft Teams](https://www.stacksync.com/integrations/github-and-microsoft-teams) - [GitHub and Monday](https://www.stacksync.com/integrations/github-and-monday) - [GitHub and Notion](https://www.stacksync.com/integrations/github-and-notion) - [GitHub and Orderful](https://www.stacksync.com/integrations/github-and-orderful) - [GitHub and Quip](https://www.stacksync.com/integrations/github-and-quip) - [GitHub and Resend](https://www.stacksync.com/integrations/github-and-resend) - [GitHub and SendGrid](https://www.stacksync.com/integrations/github-and-sendgrid) - [GitHub and ServiceMax](https://www.stacksync.com/integrations/github-and-servicemax) - [GitHub and ServiceNow](https://www.stacksync.com/integrations/github-and-servicenow) - [GitHub and Slack](https://www.stacksync.com/integrations/github-and-slack) - [GitHub and Smartsheet](https://www.stacksync.com/integrations/github-and-smartsheet) - [GitHub and SysAid](https://www.stacksync.com/integrations/github-and-sysaid) - [GitHub and Twilio](https://www.stacksync.com/integrations/github-and-twilio) - [GitHub and Wrike](https://www.stacksync.com/integrations/github-and-wrike) - [GitHub and Zendesk](https://www.stacksync.com/integrations/github-and-zendesk) ### Accounting and finance · 16 - [GitHub and Adyen](https://www.stacksync.com/integrations/adyen-and-github) - [GitHub and Anaplan](https://www.stacksync.com/integrations/anaplan-and-github) - [GitHub and BILL](https://www.stacksync.com/integrations/bill-and-github) - [GitHub and Braintree](https://www.stacksync.com/integrations/braintree-and-github) - [GitHub and Coupa](https://www.stacksync.com/integrations/coupa-and-github) - [GitHub and Hyperline](https://www.stacksync.com/integrations/github-and-hyperline) - [GitHub and LogiSense](https://www.stacksync.com/integrations/github-and-logisense) - [GitHub and Navan](https://www.stacksync.com/integrations/github-and-navan) - [GitHub and Pigment](https://www.stacksync.com/integrations/github-and-pigment) - [GitHub and QuickBooks](https://www.stacksync.com/integrations/github-and-quickbooks) - [GitHub and Ramp](https://www.stacksync.com/integrations/github-and-ramp) - [GitHub and Recurly](https://www.stacksync.com/integrations/github-and-recurly) - [GitHub and Rillet](https://www.stacksync.com/integrations/github-and-rillet) - [GitHub and Stripe](https://www.stacksync.com/integrations/github-and-stripe) - [GitHub and Workday](https://www.stacksync.com/integrations/github-and-workday) - [GitHub and Zuora](https://www.stacksync.com/integrations/github-and-zuora) ### AI · 5 - [GitHub and Anthropic](https://www.stacksync.com/integrations/anthropic-and-github) - [GitHub and Autopilot](https://www.stacksync.com/integrations/autopilot-and-github) - [GitHub and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-github) - [GitHub and OpenAI](https://www.stacksync.com/integrations/github-and-openai) - [GitHub and Pinecone](https://www.stacksync.com/integrations/github-and-pinecone) ### Developer tools · 11 - [GitHub and Azure Service Bus](https://www.stacksync.com/integrations/azure-service-bus-and-github) - [GitHub and Datadog](https://www.stacksync.com/integrations/datadog-and-github) - [GitHub and Google Cloud Pub/Sub](https://www.stacksync.com/integrations/github-and-google-pubsub) - [GitHub and Jira](https://www.stacksync.com/integrations/github-and-jira) - [GitHub and JMS](https://www.stacksync.com/integrations/github-and-jms) - [GitHub and LDAP](https://www.stacksync.com/integrations/github-and-ldap) - [GitHub and Microsoft Graph](https://www.stacksync.com/integrations/github-and-microsoft-graph) - [GitHub and New Relic](https://www.stacksync.com/integrations/github-and-newrelic) - [GitHub and Opsgenie](https://www.stacksync.com/integrations/github-and-opsgenie) - [GitHub and PagerDuty](https://www.stacksync.com/integrations/github-and-pagerduty) - [GitHub and RabbitMQ](https://www.stacksync.com/integrations/github-and-rabbitmq) ### Human resources · 13 - [GitHub and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-github) - [GitHub and D2L Brightspace](https://www.stacksync.com/integrations/d2l-brightspace-and-github) - [GitHub and Greenhouse](https://www.stacksync.com/integrations/github-and-greenhouse) - [GitHub and Hibob](https://www.stacksync.com/integrations/github-and-hibob) - [GitHub and Jobvite](https://www.stacksync.com/integrations/github-and-jobvite) - [GitHub and Lever](https://www.stacksync.com/integrations/github-and-lever) - [GitHub and Namely](https://www.stacksync.com/integrations/github-and-namely) - [GitHub and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/github-and-oracle-fusion-cloud-hcm) - [GitHub and Paylocity](https://www.stacksync.com/integrations/github-and-paylocity) - [GitHub and SmartRecruiters](https://www.stacksync.com/integrations/github-and-smartrecruiters) - [GitHub and Success Factors](https://www.stacksync.com/integrations/github-and-success-factors) - [GitHub and UKG Pro](https://www.stacksync.com/integrations/github-and-ukg-pro) - [GitHub and UKG Ready](https://www.stacksync.com/integrations/github-and-ukg-ready) ### Security and identity · 6 - [GitHub and Active Directory](https://www.stacksync.com/integrations/active-directory-and-github) - [GitHub and Auth0](https://www.stacksync.com/integrations/auth0-and-github) - [GitHub and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-github) - [GitHub and JumpCloud](https://www.stacksync.com/integrations/github-and-jumpcloud) - [GitHub and Okta](https://www.stacksync.com/integrations/github-and-okta) - [GitHub and OneLogin](https://www.stacksync.com/integrations/github-and-onelogin) ### Storage · 4 - [GitHub and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-github) - [GitHub and Box](https://www.stacksync.com/integrations/box-and-github) - [GitHub and Egnyte](https://www.stacksync.com/integrations/egnyte-and-github) - [GitHub and SharePoint](https://www.stacksync.com/integrations/github-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/)