PagerDuty to Databricks integration

Connect PagerDuty to Databricks and automatically sync your product analytics data. Weld extracts data from PagerDuty, loads it into Databricks, and lets you transform the data using SQL or dbt, no custom scripts required.

4.8 on G2
PagerDutySource
WeldWeld
DatabricksWarehouse
Weld · New sync
PagerDutySourcePagerDutyConnected
Tables to sync

Your own tables, picked when you set up the sync.

  • Extract
  • Load
  • Keep in sync
DatabricksDestinationDatabricksReady
pager_duty schema
  • pager_duty.Synced
  • pager_duty.Syncing
  • pager_duty.Synced
  • pager_duty.Synced

Trusted by data and AI teams

  • Flatpay
  • Holafly
  • eComplete
  • Dishoom
  • Danish Endurance
  • Female Invest
  • Son of a Tailor
  • Onomondo
  • Medik8
  • Pas Normal Studios
How it works

How to set up PagerDuty to Databricks in Weld.
In the app, with the API or an agent.

Weld · New PagerDuty sync
PagerDutyNew connectionPagerDutyAuthorised
Connection namepager_duty
AuthorizeOpens PagerDuty to grant read access
Use cases

Why sync PagerDuty to Databricks?
Ready for analysis.

Centralizing your PagerDuty data in Databricks lets you join it with other data sources for cross-platform analytics and deeper insights.

Build reliable dashboards and reports by querying PagerDuty data directly in Databricks using SQL or your preferred BI tool.

  • Product usage analytics

    Combine PagerDuty event data with business data in Databricks to understand how product usage drives retention and revenue.

  • Centralized data warehouse

    Bring PagerDuty data into Databricks alongside other sources to create a single source of truth for your organization.

  • Automated reporting

    Replace manual exports and spreadsheet-based reporting with automated pipelines from PagerDuty to Databricks. Connect BI tools like Looker, Metabase, or Power BI.

Data

What data can you sync?
From PagerDuty to Databricks.

Weld syncs the objects the PagerDuty connector exposes into Databricks, and you choose which tables and fields to include. The connector's docs list what is available.

    Weld MCP server

    Ask your agent.
    It queries Databricks for you.

    Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the PagerDuty context, finds the tables it needs and runs the query in Databricks.

    Claude CodeOpus 5
    >

    Which PagerDuty tables do we have in Databricks, and which is the largest?

    Looking up what Weld has synced from PagerDuty.

    ●weld·search_available_references
    ⎿raw.pager_duty.*
    tables, columns and freshness
    ●weld·get_reference_schema
    ⎿columns, types and nullability
    ●weld·run_query
    ⎿select count(*) from {{raw.pager_duty.…}}
    submitted
    ●weld·get_query_status
    ⎿DONE
    ●weld·get_query_result
    ⎿rows returned
    ✓Answered from PagerDuty data in Databricks
    >Ask about your PagerDuty data
    Under the hood

    Technical considerations.
    What to expect.

    Incremental syncing
    Weld uses incremental syncing where supported by the PagerDuty API, loading only new and updated records to minimize data transfer and warehouse costs.
    Schema handling
    Weld automatically manages schema changes. If PagerDuty adds new fields, they're detected and added to the corresponding Databricks tables.
    Data freshness
    Sync frequency depends on your Weld plan. Most connectors support schedules from every 5 minutes up to daily intervals.
    Security
    All data is encrypted in transit (TLS) and at rest. Weld is SOC 2 Type II compliant and supports IP whitelisting for database connections.
    FAQ

    Common questions.
    About PagerDuty to Databricks.

    Start syncing PagerDuty to Databricks.

    Set up your PagerDuty data pipeline in minutes. No credit card required. Free for 14 days.

    PagerDutySource
    WeldWeld
    DatabricksWarehouse