--- title: "PagerDuty connector: setup and compatibility | Stacksync" description: "PagerDuty integration guide: plan Users and Teams, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/pagerduty last_modified: 2026-09-15 --- Developer tools · Two-way sync platform # PagerDuty 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 PagerDuty workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Users and Teams. 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. - **Incidents** - **Services** - **Users** **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=pagerduty) ## 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 ## PagerDuty records to discuss. These PagerDuty record examples help scope a technical review. They are not a list of verified Stacksync operations. Incidents Identify this record type and the operation you need to review with Stacksync. Services 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. ### See 3 more record examples Teams Keep group IDs and membership relationships separately from group names. Schedules Identify this record type and the operation you need to review with Stacksync. Escalation Policies Identify this record type and the operation you need to review with Stacksync. Connection setup ## PagerDuty connection requirements. Review PagerDuty 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 PagerDuty account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for PagerDuty, including read/write support, authentication, and initial-load limits. [Open the PagerDuty vendor API reference](https://developer.pagerduty.com/api-reference/) ### PagerDuty API reference - [PagerDuty vendor API documentation](https://developer.pagerduty.com/api-reference/) Integration design ## Match records and fields for your PagerDuty 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 PagerDuty **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. #### 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. [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 PagerDuty 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 PagerDuty 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 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 PagerDuty 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 PagerDuty integration. ### Diagnose record matching, delayed changes, and rejected operations A PagerDuty 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 PagerDuty implementation’s change-detection method for Users and Teams. 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 PagerDuty 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 PagerDuty workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=pagerduty) ## PagerDuty 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 ## PagerDuty connector FAQ ### How should I plan an integration with PagerDuty? 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 PagerDuty connector write changes back? Write-back support is not established for this connection. Review the PagerDuty records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for PagerDuty 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 PagerDuty? Resolve tenant and group references and establish a protected administrative-account policy. ### How do I validate PagerDuty changes after the initial load? Test a renamed login, disabled account, missing group, and a user existing in two tenants. 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 PagerDuty integration demo? Start with one workflow and a sample record from Users and Teams. 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 PagerDuty 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 PagerDuty and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use PagerDuty. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a PagerDuty record changes.” - “Create a Genie that answers questions about our PagerDuty 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 PagerDuty 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 - [PagerDuty and Splunk](https://www.stacksync.com/integrations/pagerduty-and-splunk) - [PagerDuty and Slack](https://www.stacksync.com/integrations/pagerduty-and-slack) - [PagerDuty and ServiceNow](https://www.stacksync.com/integrations/pagerduty-and-servicenow) - [Okta and PagerDuty](https://www.stacksync.com/integrations/okta-and-pagerduty) - [Elasticsearch and PagerDuty](https://www.stacksync.com/integrations/elasticsearch-and-pagerduty) - [Databricks and PagerDuty](https://www.stacksync.com/integrations/databricks-and-pagerduty) - [PagerDuty and Zendesk](https://www.stacksync.com/integrations/pagerduty-and-zendesk) - [PagerDuty and Zoom](https://www.stacksync.com/integrations/pagerduty-and-zoom) ### Database · 50 - [PagerDuty and Airtable](https://www.stacksync.com/integrations/airtable-and-pagerduty) - [PagerDuty and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-pagerduty) - [PagerDuty and Amazon DynamoDB](https://www.stacksync.com/integrations/dynamo-db-and-pagerduty) - [PagerDuty and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-pagerduty) - [PagerDuty and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-pagerduty) - [PagerDuty and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-pagerduty) - [PagerDuty and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-pagerduty) - [PagerDuty and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-pagerduty) - [PagerDuty and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-pagerduty) - [PagerDuty and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-pagerduty) - [PagerDuty and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-pagerduty) - [PagerDuty and Citus](https://www.stacksync.com/integrations/citus-and-pagerduty) - [PagerDuty and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-pagerduty) - [PagerDuty and Couchbase](https://www.stacksync.com/integrations/couchbase-and-pagerduty) - [PagerDuty and DuckDB](https://www.stacksync.com/integrations/duckdb-and-pagerduty) - [PagerDuty and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-pagerduty) - [PagerDuty and Firebase](https://www.stacksync.com/integrations/firebase-and-pagerduty) - [PagerDuty and Google AlloyDB](https://www.stacksync.com/integrations/google-alloydb-and-pagerduty) - [PagerDuty and Google Cloud Spanner](https://www.stacksync.com/integrations/google-cloud-spanner-and-pagerduty) - [PagerDuty and Google Cloud SQL](https://www.stacksync.com/integrations/google-cloud-sql-and-pagerduty) - [PagerDuty and IBM AS/400](https://www.stacksync.com/integrations/ibm-as400-and-pagerduty) - [PagerDuty and IBM Db2](https://www.stacksync.com/integrations/ibm-db2-and-pagerduty) - [PagerDuty and IBM Informix](https://www.stacksync.com/integrations/ibm-informix-and-pagerduty) - [PagerDuty and InfluxDB](https://www.stacksync.com/integrations/influxdb-and-pagerduty) - [PagerDuty and InterSystems IRIS](https://www.stacksync.com/integrations/intersystems-iris-and-pagerduty) - [PagerDuty and JDBC](https://www.stacksync.com/integrations/jdbc-and-pagerduty) - [PagerDuty and MariaDB](https://www.stacksync.com/integrations/mariadb-and-pagerduty) - [PagerDuty and MarkLogic](https://www.stacksync.com/integrations/marklogic-and-pagerduty) - [PagerDuty and MongoDB](https://www.stacksync.com/integrations/mongodb-and-pagerduty) - [PagerDuty and MySQL](https://www.stacksync.com/integrations/mysql-and-pagerduty) - [PagerDuty and Neo4j](https://www.stacksync.com/integrations/neo4j-and-pagerduty) - [PagerDuty and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/oci-database-and-pagerduty) - [PagerDuty and OpenSearch](https://www.stacksync.com/integrations/opensearch-and-pagerduty) - [PagerDuty and Oracle DB](https://www.stacksync.com/integrations/oracle-db-and-pagerduty) - [PagerDuty and Postgres Heroku](https://www.stacksync.com/integrations/pagerduty-and-postgres-heroku) - [PagerDuty and PostgreSQL](https://www.stacksync.com/integrations/pagerduty-and-postgresql) - [PagerDuty and RavenDB](https://www.stacksync.com/integrations/pagerduty-and-ravendb) - [PagerDuty and Redis Enterprise](https://www.stacksync.com/integrations/pagerduty-and-redis-enterprise) - [PagerDuty and Reltio](https://www.stacksync.com/integrations/pagerduty-and-reltio) - [PagerDuty and Render Postgres](https://www.stacksync.com/integrations/pagerduty-and-render-postgres) - [PagerDuty and SAP ASE (Sybase)](https://www.stacksync.com/integrations/pagerduty-and-sap-ase-sybase) - [PagerDuty and SAP HANA](https://www.stacksync.com/integrations/pagerduty-and-sap-hana) - [PagerDuty and Scaleway Postgres](https://www.stacksync.com/integrations/pagerduty-and-scaleway-postgres) - [PagerDuty and SingleStore](https://www.stacksync.com/integrations/pagerduty-and-singlestore) - [PagerDuty and SQL Server](https://www.stacksync.com/integrations/pagerduty-and-sql-server) - [PagerDuty and Supabase](https://www.stacksync.com/integrations/pagerduty-and-supabase) - [PagerDuty and TiDB](https://www.stacksync.com/integrations/pagerduty-and-tidb) - [PagerDuty and TimescaleDB](https://www.stacksync.com/integrations/pagerduty-and-timescaledb) - [PagerDuty and VoltDB](https://www.stacksync.com/integrations/pagerduty-and-voltdb) - [PagerDuty and YugabyteDB](https://www.stacksync.com/integrations/pagerduty-and-yugabytedb) ### Data warehouse · 28 - [PagerDuty and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-pagerduty) - [PagerDuty and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-pagerduty) - [PagerDuty and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-pagerduty) - [PagerDuty and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-pagerduty) - [PagerDuty and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-pagerduty) - [PagerDuty and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-pagerduty) - [PagerDuty and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-pagerduty) - [PagerDuty and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-pagerduty) - [PagerDuty and BigQuery](https://www.stacksync.com/integrations/bigquery-and-pagerduty) - [PagerDuty and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-pagerduty) - [PagerDuty and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-pagerduty) - [PagerDuty and Databricks](https://www.stacksync.com/integrations/databricks-and-pagerduty) - [PagerDuty and Dremio](https://www.stacksync.com/integrations/dremio-and-pagerduty) - [PagerDuty and Exasol](https://www.stacksync.com/integrations/exasol-and-pagerduty) - [PagerDuty and Firebolt](https://www.stacksync.com/integrations/firebolt-and-pagerduty) - [PagerDuty and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-pagerduty) - [PagerDuty and Greenplum](https://www.stacksync.com/integrations/greenplum-and-pagerduty) - [PagerDuty and IBM Netezza](https://www.stacksync.com/integrations/ibm-netezza-and-pagerduty) - [PagerDuty and Materialize](https://www.stacksync.com/integrations/materialize-and-pagerduty) - [PagerDuty and MotherDuck](https://www.stacksync.com/integrations/motherduck-and-pagerduty) - [PagerDuty and Rockset](https://www.stacksync.com/integrations/pagerduty-and-rockset) - [PagerDuty and Snowflake](https://www.stacksync.com/integrations/pagerduty-and-snowflake) - [PagerDuty and Starburst Enterprise](https://www.stacksync.com/integrations/pagerduty-and-starburst-enterprise) - [PagerDuty and StarRocks](https://www.stacksync.com/integrations/pagerduty-and-starrocks) - [PagerDuty and Teradata Vantage](https://www.stacksync.com/integrations/pagerduty-and-teradata-vantage) - [PagerDuty and Tinybird](https://www.stacksync.com/integrations/pagerduty-and-tinybird) - [PagerDuty and Vertica](https://www.stacksync.com/integrations/pagerduty-and-vertica) - [PagerDuty and Yellowbrick](https://www.stacksync.com/integrations/pagerduty-and-yellowbrick) ### Business productivity · 37 - [PagerDuty and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-pagerduty) - [PagerDuty and Agiloft](https://www.stacksync.com/integrations/agiloft-and-pagerduty) - [PagerDuty and Asana](https://www.stacksync.com/integrations/asana-and-pagerduty) - [PagerDuty and Atlassian](https://www.stacksync.com/integrations/atlassian-and-pagerduty) - [PagerDuty and Braze](https://www.stacksync.com/integrations/braze-and-pagerduty) - [PagerDuty and Campfire](https://www.stacksync.com/integrations/campfire-and-pagerduty) - [PagerDuty and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-pagerduty) - [PagerDuty and Customer.io](https://www.stacksync.com/integrations/customer-io-and-pagerduty) - [PagerDuty and Docusign](https://www.stacksync.com/integrations/docusign-and-pagerduty) - [PagerDuty and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-pagerduty) - [PagerDuty and Front](https://www.stacksync.com/integrations/front-and-pagerduty) - [PagerDuty and FullEnrich](https://www.stacksync.com/integrations/full-enrich-and-pagerduty) - [PagerDuty and Gainsight](https://www.stacksync.com/integrations/gainsight-and-pagerduty) - [PagerDuty and Gatekeeper](https://www.stacksync.com/integrations/gatekeeper-and-pagerduty) - [PagerDuty and GitHub](https://www.stacksync.com/integrations/github-and-pagerduty) - [PagerDuty and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-pagerduty) - [PagerDuty and Ironclad](https://www.stacksync.com/integrations/ironclad-and-pagerduty) - [PagerDuty and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-pagerduty) - [PagerDuty and Lemlist](https://www.stacksync.com/integrations/lemlist-and-pagerduty) - [PagerDuty and Microsoft 365](https://www.stacksync.com/integrations/microsoft-365-and-pagerduty) - [PagerDuty and Microsoft Dynamics 365](https://www.stacksync.com/integrations/microsoft-dynamics-365-and-pagerduty) - [PagerDuty and Microsoft Teams](https://www.stacksync.com/integrations/microsoft-teams-and-pagerduty) - [PagerDuty and Monday](https://www.stacksync.com/integrations/monday-and-pagerduty) - [PagerDuty and NextGen Healthcare](https://www.stacksync.com/integrations/nextgen-healthcare-and-pagerduty) - [PagerDuty and Notion](https://www.stacksync.com/integrations/notion-and-pagerduty) - [PagerDuty and Orderful](https://www.stacksync.com/integrations/orderful-and-pagerduty) - [PagerDuty and Quip](https://www.stacksync.com/integrations/pagerduty-and-quip) - [PagerDuty and Resend](https://www.stacksync.com/integrations/pagerduty-and-resend) - [PagerDuty and SendGrid](https://www.stacksync.com/integrations/pagerduty-and-sendgrid) - [PagerDuty and ServiceMax](https://www.stacksync.com/integrations/pagerduty-and-servicemax) - [PagerDuty and ServiceNow](https://www.stacksync.com/integrations/pagerduty-and-servicenow) - [PagerDuty and Slack](https://www.stacksync.com/integrations/pagerduty-and-slack) - [PagerDuty and Smartsheet](https://www.stacksync.com/integrations/pagerduty-and-smartsheet) - [PagerDuty and SysAid](https://www.stacksync.com/integrations/pagerduty-and-sysaid) - [PagerDuty and Twilio](https://www.stacksync.com/integrations/pagerduty-and-twilio) - [PagerDuty and Wrike](https://www.stacksync.com/integrations/pagerduty-and-wrike) - [PagerDuty and Zendesk](https://www.stacksync.com/integrations/pagerduty-and-zendesk) ### Analytics · 3 - [PagerDuty and Pendo](https://www.stacksync.com/integrations/pagerduty-and-pendo) - [PagerDuty and Splunk](https://www.stacksync.com/integrations/pagerduty-and-splunk) - [PagerDuty and Treasure Data](https://www.stacksync.com/integrations/pagerduty-and-treasuredata) ### Communications · 5 - [PagerDuty and Aircall](https://www.stacksync.com/integrations/aircall-and-pagerduty) - [PagerDuty and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-pagerduty) - [PagerDuty and Infobip](https://www.stacksync.com/integrations/infobip-and-pagerduty) - [PagerDuty and RingCentral](https://www.stacksync.com/integrations/pagerduty-and-ringcentral) - [PagerDuty and Zoom](https://www.stacksync.com/integrations/pagerduty-and-zoom) ### Security and identity · 6 - [PagerDuty and Active Directory](https://www.stacksync.com/integrations/active-directory-and-pagerduty) - [PagerDuty and Auth0](https://www.stacksync.com/integrations/auth0-and-pagerduty) - [PagerDuty and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-pagerduty) - [PagerDuty and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-pagerduty) - [PagerDuty and Okta](https://www.stacksync.com/integrations/okta-and-pagerduty) - [PagerDuty and OneLogin](https://www.stacksync.com/integrations/onelogin-and-pagerduty) ### Storage · 4 - [PagerDuty and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-pagerduty) - [PagerDuty and Box](https://www.stacksync.com/integrations/box-and-pagerduty) - [PagerDuty and Egnyte](https://www.stacksync.com/integrations/egnyte-and-pagerduty) - [PagerDuty and SharePoint](https://www.stacksync.com/integrations/pagerduty-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/)