Trigger Incident with PagerDuty API on New Requests from HTTP / Webhook API

Pipedream makes it easy to connect APIs for PagerDuty, HTTP / Webhook and 2,400+ other apps remarkably fast.

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

Trigger Incident with the PagerDuty API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a HTTP / Webhook trigger and PagerDuty action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Requests trigger
1. Optional- Configure Body Only
2. Optional- Configure Response Status Code
3. Optional- Configure Response Content-Type
4. Optional- Configure Response Body
5. Connect your HTTP / Webhook account
Configure the Trigger Incident action
1. Connect your PagerDuty account
2. Configure Incident Title
3. Select a Service ID
4. Optional- Select a Incident Urgency
5. Optional- Configure Incident Details
6. Optional- Configure Incident Key
7. Optional- Select a Escalation Policy ID
8. Select one or more Assignee IDs
9. Optional- Configure Incident Conference Bridge Number
10. Optional- Configure Incident Conference Bridge URL
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Requests on HTTP / Webhook

Description:Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

Version:0.1.1

Key:http-new-requests

View on GitHub

HTTP / Webhook Overview#

Build, test, and send HTTP requests without code using your Pipedream workflows. The HTTP / Webhook action is a tool to build HTTP requests with a Postman-like graphical interface.

Point and click HTTP requests

Define the target URL, HTTP verb, headers, query parameters, and payload body without writing custom code.

$A screenshot of Pipedream's HTTP Request Configuration interface with a GET request type selected. The request URL is set to 'https://api.openai.com/v1/models'. The 'Auth' tab is highlighted, indicating that authentication is required for this request. In the headers section, there are two headers configured: 'User-Agent' is set to 'pipedream/1', and 'Authorization' is set to 'Bearer {{openai_api_key}}', showing how the OpenAI account's API key is dynamically inserted into the headers to handle authentication automatically.$

Here's an example workflow that uses the HTTP / Webhook action to send an authenticated API request to OpenAI.

Focus on integrating, not authenticating

This action can also use your connected accounts with third-party APIs. Selecting an integrated app will automatically update the request’s headers to authenticate with the app properly, and even inject your token dynamically.

Pipedream integrates with thousands of APIs, but if you can’t find a Pipedream integration simply use Environment Variables in your request headers to authenticate with.

Compatible with no code actions or Node.js and Python

The HTTP/Webhook action exports HTTP response data for use in subsequent workflow steps, enabling easy data transformation, further API calls, database storage, and more.

Response data is available for both coded (Node.js, Python) and no-code steps within your workflow.

Trigger Code#

import http from "../../http.app.mjs";

// Core HTTP component
export default {
  key: "http-new-requests",
  name: "New Requests",
  description: "Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.",
  version: "0.1.1",
  type: "source",
  props: {
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    emitBodyOnly: {
      type: "boolean",
      label: "Body Only",
      description: "This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.",
      optional: true,
      default: false,
    },
    resStatusCode: {
      type: "string",
      label: "Response Status Code",
      description: "The status code to return in the HTTP response",
      optional: true,
      default: "200",
    },
    resContentType: {
      type: "string",
      label: "Response Content-Type",
      description: "The `Content-Type` of the body returned in the HTTP response",
      optional: true,
      default: "application/json",
    },
    resBody: {
      type: "string",
      label: "Response Body",
      description: "The body to return in the HTTP response",
      optional: true,
      default: "{ \"success\": true }",
    },
    http,
  },
  async run(event) {
    const summary = `${event.method} ${event.path}`;

    this.httpInterface.respond({
      status: this.resStatusCode,
      body: this.resBody,
      headers: {
        "content-type": this.resContentType,
      },
    });

    if (this.emitBodyOnly) {
      this.$emit(event.body, {
        summary,
      });
    } else {
      this.$emit(event, {
        summary,
      });
    }
  },
};

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
N/A	`httpInterface`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
Body Only	`emitBodyOnly`	`boolean`	This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.
Response Status Code	`resStatusCode`	`string`	The status code to return in the HTTP response
Response Content-Type	`resContentType`	`string`	The `Content-Type` of the body returned in the HTTP response
Response Body	`resBody`	`string`	The body to return in the HTTP response
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.

Trigger Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

Get a unique URL where you can send HTTP or webhook requests

Action#

Trigger Incident on PagerDuty

Description:Trigger an incident. [See the docs here](https://developer.pagerduty.com/api-reference/b3A6Mjc0ODE0MA-create-an-incident)

Version:0.0.2

Key:pagerduty-trigger-incident

View on GitHub

PagerDuty Overview#

The PagerDuty API offers a powerful interface to automate your digital operations management. By leveraging its capabilities on Pipedream, you can create workflows that respond to incidents, automate alerts, and synchronize incident data across various platforms. PagerDuty's API enables you to manage services, teams, and incidents, ensuring that your systems remain operational and that the right people are notified at the right time.

Action Code#

import constants from "../../common/constants.mjs";
import utils from "../../common/utils.mjs";
import pagerduty from "../../pagerduty.app.mjs";

const {
  reduceProperties,
  emptyStrToUndefined,
  commaSeparatedListToArray,
} = utils;

export default {
  key: "pagerduty-trigger-incident",
  name: "Trigger Incident",
  description: "Trigger an incident. [See the docs here](https://developer.pagerduty.com/api-reference/b3A6Mjc0ODE0MA-create-an-incident)",
  type: "action",
  version: "0.0.2",
  props: {
    pagerduty,
    title: {
      propDefinition: [
        pagerduty,
        "incidentTitle",
      ],
    },
    serviceId: {
      propDefinition: [
        pagerduty,
        "serviceId",
      ],
    },
    urgency: {
      propDefinition: [
        pagerduty,
        "incidentUrgency",
      ],
    },
    bodyDetails: {
      propDefinition: [
        pagerduty,
        "incidentBodyDetails",
      ],
    },
    incidentKey: {
      propDefinition: [
        pagerduty,
        "incidentKey",
      ],
    },
    escalationPolicyId: {
      propDefinition: [
        pagerduty,
        "escalationPolicyId",
      ],
    },
    assigneeIds: {
      type: "string[]",
      label: "Assignee IDs",
      description: "The IDs of the users to assign to the incident. Use a comma-separated list when structured mode is `off` specifying the ids as values. (e.g. `P97DSQO,PWLDHXC,P1M4QLY`)",
      propDefinition: [
        pagerduty,
        "userId",
      ],
    },
    conferenceBridgeNumber: {
      propDefinition: [
        pagerduty,
        "incidentConferenceBridgeNumber",
      ],
    },
    conferenceBridgeUrl: {
      propDefinition: [
        pagerduty,
        "incidentConferenceBridgeUrl",
      ],
    },
  },
  async run({ $ }) {
    const {
      title,
      serviceId,
    } = this;

    const conferenceBridgeNumber = emptyStrToUndefined(this.conferenceBridgeNumber);
    const conferenceBridgeUrl = emptyStrToUndefined(this.conferenceBridgeUrl);
    const escalationPolicyId = emptyStrToUndefined(this.escalationPolicyId);
    const bodyDetails = emptyStrToUndefined(this.bodyDetails);
    const urgency = emptyStrToUndefined(this.urgency);
    const incidentKey = emptyStrToUndefined(this.incidentKey);
    const assigneeIds = commaSeparatedListToArray(this.assigneeIds);

    const initialProps = {
      type: constants.INCIDENT_TYPE,
      title,
      service: {
        id: serviceId,
        type: constants.REFERENCE.SERVICE,
      },
    };

    const additionalProps = {
      urgency,
      incident_key: incidentKey,
      body: [
        {
          type: constants.INCIDENT_BODY_TYPE,
          details: bodyDetails,
        },
        bodyDetails,
      ],
      assignments: [
        assigneeIds?.map((id) => ({
          assignee: {
            id,
            type: constants.REFERENCE.USER,
          },
        })),
        assigneeIds?.length && !escalationPolicyId,
      ],
      escalation_policy: [
        {
          id: escalationPolicyId,
          type: constants.REFERENCE.ESCALATION_POLICY,
        },
        escalationPolicyId,
      ],
      conference_bridge: [
        {
          conference_number: conferenceBridgeNumber,
          conference_url: conferenceBridgeUrl,
        },
        conferenceBridgeNumber || conferenceBridgeUrl,
      ],
    };

    const toCreate = reduceProperties({
      initialProps,
      additionalProps,
    });

    const { incident } = await this.pagerduty.createIncident({
      $,
      data: {
        incident: toCreate,
      },
    });

    $.export("$summary", `Incident ${incident.summary} has been ${incident.status}`);

    return incident;
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
PagerDuty	`pagerduty`	`app`	This component uses the PagerDuty app.
Incident Title	`title`	`string`	A succinct description of the nature, symptoms, cause, or effect of the incident.
Service ID	`serviceId`	`string`	Select a value from the drop down menu.
Incident Urgency	`urgency`	`string`	Select a value from the drop down menu:`{ "label": "High", "value": "high" }{ "label": "Low", "value": "low" }`
Incident Details	`bodyDetails`	`string`	Additional incident details.
Incident Key	`incidentKey`	`string`	A string which identifies the incident. Sending subsequent requests referencing the same service and with the same Incident Key will result in those requests being rejected if an open incident matches that Incident Key.
Escalation Policy ID	`escalationPolicyId`	`string`	Select a value from the drop down menu.
Assignee IDs	`assigneeIds`	`string[]`	Select a value from the drop down menu.
Incident Conference Bridge Number	`conferenceBridgeNumber`	`string`	The phone number of the conference call for the conference bridge. Phone numbers should be formatted like `+1 415-555-1212,,,,1234#`, where a comma (`,`) represents a one-second wait and pound (`#`) completes access code input.
Incident Conference Bridge URL	`conferenceBridgeUrl`	`string`	An URL for the conference bridge. This could be a link to a web conference or Slack channel.

Action Authentication#

PagerDuty uses OAuth authentication. When you connect your PagerDuty account, Pipedream will open a popup window where you can sign into PagerDuty and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any PagerDuty API.

Pipedream requests the following authorization scopes when you connect your account:

About PagerDuty#

Real-Time Operations and Incident Response

More Ways to Connect PagerDuty + HTTP / Webhook#

Other Popular Integrations#

Custom Request with HTTP / Webhook API on New or Updated Incident from PagerDuty API

PagerDuty + HTTP / Webhook