PAGERDUTY_MIGRATE_INTEGRATION_BETWEEN_ORCHESTRATIONS

This endpoint facilitates the migration of an integration from one event orchestration to another within PagerDuty. It allows users to reassign an existing integration to a different event orchestration, maintaining the integration's configuration while updating its association. This operation is useful when restructuring event management workflows or optimizing incident routing. The endpoint should be used when there's a need to change how a specific integration interacts with PagerDuty's event processing system. It's important to note that this process only changes the association and does not modify the integration's settings or connected external services.

Available from 1 provider (1 remote)

Input Schema


            {
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "title": "Id",
      "description": "The ID of an Event Orchestration."
    },
    "source_id": {
      "type": "string",
      "title": "Source Id",
      "description": "The ID of the Event Orchestration you\"ll be moving the Integration away from "
    },
    "source_type": {
      "enum": [
        "orchestration"
      ],
      "type": "string",
      "title": "Source Type",
      "description": "The type of of the `source_id` object"
    },
    "integration_id": {
      "type": "string",
      "title": "Integration Id",
      "description": "The ID of the Integration you\"ll be moving"
    }
  }
}
          

Remote Providers (1)

These servers are accessible over the network — no local installation needed.

PagerDuty

Remote

pagerduty

View product →