PAGERDUTY_CREATE_INCIDENT_RECORD

Creates a new incident in PagerDuty with specified details and assignments. Use this endpoint when an event requires immediate attention from on-call teams. It supports comprehensive incident documentation, including priority, urgency, and conference bridge information. The 'incident_key' parameter helps prevent duplicate incidents, crucial for maintaining a clean incident list.

Available from 1 provider (1 remote)

Input Schema

            {
  "type": "object",
  "properties": {
    "incident__type": {
      "type": "string",
      "title": "Incident  Type",
      "default": "incident",
      "description": "Specifies the type of object being created. Always set to \"incident\" for incident creation. This field helps ensure API consistency and proper object handling.  "
    },
    "incident__title": {
      "type": "string",
      "title": "Incident  Title",
      "default": "New Incident",
      "description": "A clear, descriptive title for the incident that helps responders quickly understand the issue. Best Practice Format: \"<System/Service> - <Problem> - <Impact>\" Examples: - \"Production Database - CPU Usage 95% - Customer Queries Delayed\" - \"Payment API - 500 Error Rate >5% - Orders Failing\" - \"Website - SSL Certificate Expiring - Security Risk\"  "
    },
    "incident__urgency": {
      "type": "string",
      "title": "Incident  Urgency",
      "default": "low",
      "description": "Determines the immediacy of notifications and escalations. Options: - high: Immediate notifications, aggressive escalation - low: Respect service\"s notification rules, standard escalation Choose based on: - Business impact - Time sensitivity - Service criticality - Customer impact  "
    },
    "incident__body__type": {
      "type": "string",
      "title": "Incident  Body  Type",
      "default": "Test",
      "description": "Specifies the type of body content"
    },
    "incident__assignments": {
      "type": "array",
      "items": {
        "type": "object",
        "title": "AssignmentsRequest",
        "properties": {
          "assignee__id": {
            "type": "string",
            "title": "Assignee  Id",
            "pattern": "^P[A-Z0-9]{6}$",
            "description": "User\"s unique identifier. Found in user profile or via API. "
          },
          "assignee__type": {
            "type": "string",
            "title": "Assignee  Type",
            "description": "Object type for user reference"
          }
        },
        "description": "Request schema for `Assignments`"
      },
      "title": "Incident  Assignments",
      "description": "List of users to assign to the incident. Maximum 10 assignees allowed. Important Notes: - Cannot be used with escalation_policy - Users must have access to the service - Assignments override default escalation - Order matters for primary/secondary  "
    },
    "incident__service__id": {
      "type": "string",
      "title": "Incident  Service  Id",
      "pattern": "^P[A-Z0-9]{6}$",
      "description": "Unique identifier for the PagerDuty service. Found in service settings or via API. Example: \"PSVC123\"  "
    },
    "incident__priority__id": {
      "type": "string",
      "title": "Incident  Priority  Id",
      "pattern": "^P[A-Z0-9]{6}$",
      "description": "Unique identifier for the priority level. Example: \"PRIO123\" "
    },
    "incident__body__details": {
      "type": "string",
      "title": "Incident  Body  Details",
      "default": "Incident details pending",
      "description": "Comprehensive incident details in structured format. Recommended Structure: ``` CURRENT STATUS: [Brief description of current situation] IMPACT: - Business Impact: [Description] - User Impact: [Number of affected users/systems] - Revenue Impact: [If applicable] ACTIONS TAKEN: 1. [Action 1] 2. [Action 2] METRICS: - Error Rate: [Value] - Response Time: [Value] LINKS: - Dashboard: [URL] - Logs: [URL] - Runbook: [URL] ```  "
    },
    "incident__incident__key": {
      "type": "string",
      "title": "Incident  Incident  Key",
      "pattern": "^[a-zA-Z0-9._-]+$",
      "description": "Unique identifier for deduplicating incidents within a service. Best Practice Format: \"<source>-<type>-<identifier>-<timestamp>\" Examples: - \"datadog-cpu-alert-prod-db1-1640995200\" - \"cloudwatch-memory-warning-cache-1640995200\" - \"synthetic-api-failure-payments-1640995200\" Notes: - Must be unique per service - Used to prevent duplicate incidents - Should be consistent and meaningful  "
    },
    "incident__service__type": {
      "enum": [
        "service_reference"
      ],
      "type": "string",
      "title": "Incident  Service  Type",
      "default": "service_reference",
      "description": "Object type identifier. Always \"service_reference\" for service objects. "
    },
    "incident__priority__type": {
      "type": "string",
      "title": "Incident  Priority  Type",
      "description": "Object type for priority reference"
    },
    "incident__incident__type__id": {
      "type": "string",
      "title": "Incident  Incident  Type  Id",
      "pattern": "^P[A-Z0-9]{6}$",
      "description": "Unique identifier for incident type"
    },
    "incident__incident__type__name": {
      "enum": [
        "major_incident",
        "security_incident",
        "engineering_incident",
        "customer_incident"
      ],
      "type": "string",
      "title": "Incident  Incident  Type  Name",
      "default": "engineering_incident",
      "description": "Predefined incident type categories. Used for reporting and analytics. "
    },
    "incident__incident__type__type": {
      "type": "string",
      "title": "Incident  Incident  Type  Type",
      "default": "incident_type_reference",
      "description": "Object type for incident type reference"
    },
    "incident__conference__bridge__conference__url": {
      "type": "string",
      "title": "Incident  Conference  Bridge  Conference  Url",
      "format": "uri",
      "default": "https://meet.example.com/incident",
      "description": "Web conference URL. Should be accessible to all responders. "
    },
    "incident__conference__bridge__conference__type": {
      "enum": [
        "zoom",
        "meet",
        "teams",
        "webex",
        "other"
      ],
      "type": "string",
      "title": "Incident  Conference  Bridge  Conference  Type",
      "description": "Platform used for conference bridge. Helps responders prepare right tools.  "
    },
    "incident__conference__bridge__conference__number": {
      "type": "string",
      "title": "Incident  Conference  Bridge  Conference  Number",
      "description": "Phone number with access sequence. Format: \"+1-555-123-4567,,,,1234#\" Commas (,) represent one-second pauses  "
    }
  }
}