Create HTTP Check with Pingdom API on New or Updated Incident from PagerDuty API

Pipedream makes it easy to connect APIs for Pingdom, PagerDuty and 2,900+ other apps remarkably fast.

Trigger workflow on

New or Updated Incident from the PagerDuty API

Next, do this

Create HTTP Check with the Pingdom 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 PagerDuty trigger and Pingdom action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New or Updated Incident trigger
1. Connect your PagerDuty account
2. Select a Service ID
3. Optional- Select one or more Events
Configure the Create HTTP Check action
1. Connect your Pingdom account
2. Configure Host
3. Configure Name
4. Optional- Configure Auth
5. Optional- Configure Custom Message
6. Optional- Configure Integration Ids
7. Optional- Configure IPV6
8. Optional- Configure Notify Again Every
9. Optional- Configure Notify When Backup
10. Optional- Configure Paused
11. Optional- Select one or more Probe Filters
12. Optional- Select a Resolution
13. Optional- Configure Responsetime Threshold
14. Optional- Configure Send Notification When Down
15. Optional- Configure Tags
16. Optional- Select one or more Team Ids
17. Optional- Select one or more User Ids
18. Optional- Configure Encryption
19. Optional- Configure Port
20. Optional- Configure SSL Down Days Before
21. Optional- Configure Verify Certificate
22. Optional- Configure Post Data
23. Optional- Configure Request Headers
24. Optional- Configure Should Contain
25. Optional- Configure Should Not Contain
26. Optional- Configure 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 or Updated Incident on PagerDuty

Description:Emit new event each time an incident is created or updated

Version:0.1.1

Key:pagerduty-new-or-updated-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.

Trigger Code#

import constants from "../../common/constants.mjs";
import commonWebhook from "../common-webhook.mjs";

export default {
  ...commonWebhook,
  type: "source",
  key: "pagerduty-new-or-updated-incident",
  name: "New or Updated Incident",
  version: "0.1.1",
  description: "Emit new event each time an incident is created or updated",
  methods: {
    ...commonWebhook.methods,
    getMetadata({
      id, occurred_at, data,
    }) {
      return {
        id,
        summary: `Incident ${data.incident?.id || data.id} has been created or updated`,
        ts: Date.parse(occurred_at),
      };
    },
    getEventTypes() {
      return constants.INCIDENT_EVENT_TYPES;
    },
    getHookName() {
      return "New or Updated Incident";
    },
  },
};

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
PagerDuty	`pagerduty`	`app`	This component uses the PagerDuty app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
N/A	`http`	`$.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.
Service ID	`serviceId`	`string`	Select a value from the drop down menu.
Events	`webhookEvent`	`string[]`	Select a value from the drop down menu:`incident.acknowledgedincident.annotatedincident.delegatedincident.escalatedincident.reassignedincident.reopenedincident.resolvedincident.status_update_publishedincident.triggeredincident.unacknowledgedincident.responder.addedincident.responder.repliedincident.priority_updatedservice.createdservice.deletedservice.updated`

Trigger 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

Action#

Create HTTP Check on Pingdom

Description:Creates a new HTTP check in Pingdom. [See the documentation](https://docs.pingdom.com/api/#tag/Checks/operation/post.checks)

Version:0.0.2

Key:pingdom-create-http-check

View on GitHub

Pingdom Overview#

The Pingdom API offers a suite of endpoints to monitor the uptime, performance, and interactions for websites and web applications. With this API, you can automate the retrieval of monitor statuses, alerts, and performance data. Integrating Pingdom with Pipedream allows developers to create custom workflows that can notify teams of incidents, track performance metrics, or even trigger actions based on website status changes.

Action Code#

import {
  PROBE_FILTERS_OPTIONS,
  RESOLUTION_OPTIONS,
} from "../../common/constants.mjs";
import { removeHttp } from "../../common/utils.mjs";
import pingdom from "../../pingdom.app.mjs";

export default {
  key: "pingdom-create-http-check",
  name: "Create HTTP Check",
  description: "Creates a new HTTP check in Pingdom. [See the documentation](https://docs.pingdom.com/api/#tag/Checks/operation/post.checks)",
  version: "0.0.2",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: false,
  },
  type: "action",
  props: {
    pingdom,
    host: {
      type: "string",
      label: "Host",
      description: "The target host for the check.",
    },
    name: {
      type: "string",
      label: "Name",
      description: "The name of the check.",
    },
    auth: {
      type: "string",
      label: "Auth",
      description: "Username and password, colon separated.",
      optional: true,
    },
    customMessage: {
      type: "string",
      label: "Custom Message",
      description: "Custom message that will be added to email and webhook alerts.",
      optional: true,
    },
    integrationIds: {
      type: "integer[]",
      label: "Integration Ids",
      description: "Integration identifiers.",
      optional: true,
    },
    ipv6: {
      type: "boolean",
      label: "IPV6",
      description: "Use ipv6 instead of ipv4, if an IP address is provided as host this will be overrided by the IP address version.",
      optional: true,
    },
    notifyAgainEvery: {
      type: "string",
      label: "Notify Again Every",
      description: "Notify again every n result. 0 means that no extra notifications will be sent.",
      optional: true,
    },
    notifyWhenBackup: {
      type: "boolean",
      label: "Notify When Backup",
      description: "Notify when back up again.",
      optional: true,
    },
    paused: {
      type: "boolean",
      label: "Paused",
      description: "Whether the check is paused or not.",
      optional: true,
    },
    probeFilters: {
      type: "string[]",
      label: "Probe Filters",
      description: "Filters used for probe selections. Overwrites previous filters for check. To remove all filters from a check, use an empty value.",
      options: PROBE_FILTERS_OPTIONS,
      optional: true,
    },
    resolution: {
      type: "integer",
      label: "Resolution",
      description: "How often should the check be tested? (minutes).",
      options: RESOLUTION_OPTIONS,
      optional: true,
    },
    responseTimeThreshold: {
      type: "integer",
      label: "Responsetime Threshold",
      description: "Triggers a down alert if the response time exceeds threshold specified in ms (Not available for Starter and Free plans).",
      optional: true,
    },
    sendNotificationWhenDown: {
      type: "integer",
      label: "Send Notification When Down",
      description: "Send notification when down X times.",
      optional: true,
    },
    tags: {
      type: "string[]",
      label: "Tags",
      description: "List of tags for check. The maximum length of a tag is 64 characters.",
      optional: true,
    },
    teamIds: {
      propDefinition: [
        pingdom,
        "teamIds",
      ],
      optional: true,
    },
    userIds: {
      propDefinition: [
        pingdom,
        "userIds",
      ],
      optional: true,
    },
    encryption: {
      type: "boolean",
      label: "Encryption",
      description: "Connection encryption.",
      optional: true,
    },
    port: {
      type: "integer",
      label: "Port",
      description: "Target port.",
      optional: true,
    },
    sslDownDaysBefore: {
      type: "string",
      label: "SSL Down Days Before",
      description: "Treat the target site as down if a certificate expires within the given number of days. This parameter will be ignored if `verify_certificate` is set to `false`. It will appear provided `verify_certificate` is true and `ssl_down_days_before` value is greater than or equals 1.",
      optional: true,
    },
    verifyCertificate: {
      type: "boolean",
      label: "Verify Certificate",
      description: "Treat target site as down if an invalid/unverifiable certificate is found.",
      optional: true,
    },
    postData: {
      type: "string",
      label: "Post Data",
      description: "Data that should be posted to the web page, for example submission data for a sign-up or login form. The data needs to be formatted in the same way as a web browser would send it to the web server.",
      optional: true,
    },
    requestHeaders: {
      type: "string[]",
      label: "Request Headers",
      description: "Custom HTTP header.",
      optional: true,
    },
    shouldContain: {
      type: "string",
      label: "Should Contain",
      description: "Target site should contain this string. Note! This parameter cannot be used together with the parameter 'shouldnotcontain', use only one of them in your request.",
      optional: true,
    },
    shouldNotContain: {
      type: "string",
      label: "Should Not Contain",
      description: "Target site should NOT contain this string. Note! This parameter cannot be used together with the parameter 'shouldcontain', use only one of them in your request.",
      optional: true,
    },
    url: {
      type: "string",
      label: "URL",
      description: "Path to target on server.",
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      pingdom,
      host,
      customMessage,
      notifyAgainEvery,
      probeFilters,
      responseTimeThreshold,
      sslDownDaysBefore,
      verifyCertificate,
      integrationIds,
      notifyWhenBackup,
      sendNotificationWhenDown,
      teamIds,
      userIds,
      postData,
      requestHeaders,
      shouldContain,
      shouldNotContain,
      ...data
    } = this;

    const response = await pingdom.createCheck({
      data: {
        type: "http",
        host: removeHttp(host),
        custom_message: customMessage,
        integrationids: integrationIds,
        notifyagainevery: notifyAgainEvery && parseInt(notifyAgainEvery),
        notifywhenbackup: notifyWhenBackup,
        probe_filters: probeFilters && probeFilters.map((item) => `region:${item}`),
        sendnotificationwhendown: sendNotificationWhenDown,
        teamids: teamIds,
        userids: userIds,
        responsetime_threshold: responseTimeThreshold,
        postdata: postData,
        requestheaders: requestHeaders,
        shouldcontain: shouldContain,
        shouldnotcontain: shouldNotContain,
        ssl_down_days_before: sslDownDaysBefore && parseInt(sslDownDaysBefore),
        verify_certificate: verifyCertificate,
        ...data,
      },
    });

    $.export("$summary", `Successfully created HTTP check with name "${this.name}"`);
    return response;
  },
};

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
Pingdom	`pingdom`	`app`	This component uses the Pingdom app.
Host	`host`	`string`	The target host for the check.
Name	`name`	`string`	The name of the check.
Auth	`auth`	`string`	Username and password, colon separated.
Custom Message	`customMessage`	`string`	Custom message that will be added to email and webhook alerts.
Integration Ids	`integrationIds`	`integer[]`	Integration identifiers.
IPV6	`ipv6`	`boolean`	Use ipv6 instead of ipv4, if an IP address is provided as host this will be overrided by the IP address version.
Notify Again Every	`notifyAgainEvery`	`string`	Notify again every n result. 0 means that no extra notifications will be sent.
Notify When Backup	`notifyWhenBackup`	`boolean`	Notify when back up again.
Paused	`paused`	`boolean`	Whether the check is paused or not.
Probe Filters	`probeFilters`	`string[]`	Select a value from the drop down menu:`EUNAAPACLATAM`
Resolution	`resolution`	`integer`	Select a value from the drop down menu:`{ "label": "1 minute", "value": 1 }{ "label": "5 minutes", "value": 5 }{ "label": "15 minutes", "value": 15 }{ "label": "30 minutes", "value": 30 }{ "label": "60 minutes", "value": 60 }`
Responsetime Threshold	`responseTimeThreshold`	`integer`	Triggers a down alert if the response time exceeds threshold specified in ms (Not available for Starter and Free plans).
Send Notification When Down	`sendNotificationWhenDown`	`integer`	Send notification when down X times.
Tags	`tags`	`string[]`	List of tags for check. The maximum length of a tag is 64 characters.
Team Ids	`teamIds`	`integer[]`	Select a value from the drop down menu.
User Ids	`userIds`	`string[]`	Select a value from the drop down menu.
Encryption	`encryption`	`boolean`	Connection encryption.
Port	`port`	`integer`	Target port.
SSL Down Days Before	`sslDownDaysBefore`	`string`	Treat the target site as down if a certificate expires within the given number of days. This parameter will be ignored if `verify_certificate` is set to `false`. It will appear provided `verify_certificate` is true and `ssl_down_days_before` value is greater than or equals 1.
Verify Certificate	`verifyCertificate`	`boolean`	Treat target site as down if an invalid/unverifiable certificate is found.
Post Data	`postData`	`string`	Data that should be posted to the web page, for example submission data for a sign-up or login form. The data needs to be formatted in the same way as a web browser would send it to the web server.
Request Headers	`requestHeaders`	`string[]`	Custom HTTP header.
Should Contain	`shouldContain`	`string`	Target site should contain this string. Note! This parameter cannot be used together with the parameter 'shouldnotcontain', use only one of them in your request.
Should Not Contain	`shouldNotContain`	`string`	Target site should NOT contain this string. Note! This parameter cannot be used together with the parameter 'shouldcontain', use only one of them in your request.
URL	`url`	`string`	Path to target on server.