Emergency Push Notification with Pushover API on New Issue Event (Instant) from Sentry API

Pipedream makes it easy to connect APIs for Pushover, Sentry and 2,000+ other apps remarkably fast.

Trigger workflow on

New Issue Event (Instant) from the Sentry API

Next, do this

Emergency Push Notification with the Pushover API

No credit card required

▶

Watch us build a workflow

4 min

Watch now ➜

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

Developers ♥ Pipedream

Getting Started#

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

Select this integration
Configure the New Issue Event (Instant) trigger
1. Connect your Sentry account
2. Select a Organization
Configure the Emergency Push Notification action
1. Connect your Pushover account
2. Configure Message
3. Configure Retry
4. Configure Expire
5. Optional- Configure Callback
6. Optional- Configure Title
7. Optional- Configure URL
8. Optional- Configure URL Title
9. Optional- Configure Device
10. Optional- Select a Sound
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 Issue Event (Instant) on Sentry

Description:Emit new events for issues that have been created or updated.

Version:0.1.1

Key:sentry-issue-event

View on GitHub

Sentry Overview#

The Sentry API on Pipedream allows you to automate error tracking and responses in your applications. Sentry's robust issue tracking and release monitoring align with Pipedream's ability to craft custom workflows, enabling developers to connect error alerts to a plethora of other services for notifications, analysis, task management, and more. With Sentry's detailed diagnostic data, these workflows can help reduce downtime by triggering quick actions upon issue detection.

Trigger Code#

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

export default {
  key: "sentry-issue-event",
  version: "0.1.1",
  name: "New Issue Event (Instant)",
  description: "Emit new events for issues that have been created or updated.",
  type: "source",
  props: {
    db: "$.service.db",
    http: {
      type: "$.interface.http",
      customResponse: true,
    },
    sentry,
    organizationSlug: {
      propDefinition: [
        sentry,
        "organizationSlug",
      ],
    },
  },
  hooks: {
    async activate() {
      const { slug: integrationSlug } = await this.sentry.createIntegration(
        this.getEventSourceName(),
        this.organizationSlug,
        this.http.endpoint,
      );
      this._setIntegrationSlug(integrationSlug);

      const clientSecret = await this.sentry.getClientSecret(integrationSlug);
      this._setClientSecret(clientSecret);
    },
    async deactivate() {
      const integrationSlug = this._getIntegrationSlug();
      await this.sentry.disableIntegration(integrationSlug);
    },
  },
  methods: {
    _setIntegrationSlug(integrationSlug) {
      this.db.set("integrationSlug", integrationSlug);
    },
    _getIntegrationSlug() {
      return this.db.get("integrationSlug");
    },
    _setClientSecret(clientSecret) {
      this.db.set("clientSecret", clientSecret);
    },
    _getClientSecret() {
      return this.db.get("clientSecret");
    },
    getEventSourceName() {
      return "Issue Event (Instant)";
    },
  },
  async run(event) {
    const clientSecret = this._getClientSecret();
    if (!this.sentry.isValidSource(event, clientSecret)) {
      this.http.respond({
        statusCode: 404,
      });
      return;
    }

    this.http.respond({
      statusCode: 200,
    });

    const {
      body, body: { data: { issue } },
    } = event;

    this.$emit(body, {
      id: issue.id,
      summary: issue.title,
      ts: Date.parse(issue.lastSeen),
    });
  },
};

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	`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.
Sentry	`sentry`	`app`	This component uses the Sentry app.
Organization	`organizationSlug`	`string`	Select a value from the drop down menu.

Trigger Authentication#

Sentry uses API keys for authentication. When you connect your Sentry account, Pipedream securely stores the keys so you can easily authenticate to Sentry APIs in both code and no-code steps.

About Sentry#

Sentry offers self-hosted and cloud-based application performance monitoring & error tracking that helps software teams see clearer, solve quicker, & learn continuously.

Action#

Emergency Push Notification on Pushover

Description:Sends an Emergency Push Notification to devices with Pushover. Notifications are repeated until they are acknowledged by the user. More information at [Pushing Messages](https://pushover.net/api#messages) and [Message Priority](https://pushover.net/api#priority)

Version:0.0.4

Key:pushover-emergency-push-notification

View on GitHub

Pushover Overview#

Pushover makes it easy to send real-time notifications to your Android and iOS devices. By leveraging the Pushover API on Pipedream, you can craft customized messages triggered by various events and send them to users instantly. This integration can be especially useful for monitoring systems, to-do list reminders, or even to keep tabs on your online services and workflows.

Action Code#

import pushover from "../../pushover.app.mjs";
import constants from "../../common/constants.mjs";

export default {
  key: "pushover-emergency-push-notification",
  name: "Emergency Push Notification",
  description: `Sends an Emergency Push Notification to devices with Pushover.
    Notifications are repeated until they are acknowledged by the user.
    More information at [Pushing Messages](https://pushover.net/api#messages) and [Message Priority](https://pushover.net/api#priority)`,
  version: "0.0.4",
  type: "action",
  props: {
    pushover,
    message: {
      propDefinition: [
        pushover,
        "message",
      ],
    },
    retry: {
      propDefinition: [
        pushover,
        "retry",
      ],
    },
    expire: {
      propDefinition: [
        pushover,
        "expire",
      ],
    },
    callback: {
      type: "string",
      label: "Callback",
      description: "A publicly-accessible URL that Pushover will send a request to when the user has acknowledged the notification",
      optional: true,
    },
    title: {
      propDefinition: [
        pushover,
        "title",
      ],
    },
    url: {
      propDefinition: [
        pushover,
        "url",
      ],
    },
    urlTitle: {
      propDefinition: [
        pushover,
        "urlTitle",
      ],
    },
    device: {
      propDefinition: [
        pushover,
        "device",
      ],
    },
    sound: {
      propDefinition: [
        pushover,
        "sound",
      ],
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      message,
      title,
      url,
      urlTitle,
      device,
      retry,
      expire,
      sound,
      callback,
    } = this;
    const response = await this.pushover.pushMessage({
      $,
      params: {
        message,
        title,
        url,
        device,
        priority: constants.PRIORITY.EMERGENCY,
        retry,
        expire,
        sound,
        callback,
        url_title: urlTitle,
      },
    });
    $.export("$summary", `Successfully sent emergency notification with message: "${message}"`);

    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
Pushover	`pushover`	`app`	This component uses the Pushover app.
Message	`message`	`string`	The notification message
Retry	`retry`	`integer`	How often, in seconds, Pushover will send the same notification. In a situation where your user might be in a noisy environment or sleeping, retrying the notification (with sound and vibration) will help get his or her attention. This parameter must have a value of at least 30 seconds between retries.
Expire	`expire`	`integer`	Notification expiration time, in seconds. If the notification has not been acknowledged in expire seconds, it will be marked as expired and will stop being sent to the user. Note that the notification is still shown to the user after it is expired, but it will not prompt the user for acknowledgement. This parameter must have a maximum value of at most 10800 seconds (3 hours).
Callback	`callback`	`string`	A publicly-accessible URL that Pushover will send a request to when the user has acknowledged the notification
Title	`title`	`string`	The message title
URL	`url`	`string`	A supplementary URL to show with the message
URL Title	`urlTitle`	`string`	A title for the supplementary URL. If blank, the URL is shown
Device	`device`	`string`	The device name to send the message directly. Can be comma-separated names for sending to multiple devices
Sound	`sound`	`string`	Select a value from the drop down menu.

Action Authentication#

Pushover uses API keys for authentication. When you connect your Pushover account, Pipedream securely stores the keys so you can easily authenticate to Pushover APIs in both code and no-code steps.

About Pushover#

Pushover is a simple push notification service that integrates easily into web apps like IFTTT, network monitoring systems, shell scripts, servers, and more.

More Ways to Connect Pushover + Sentry#

Other Popular Integrations#

Push Notification with Pushover API on New Issue Event (Instant) from Sentry API

Sentry + Pushover

Try it

Popular Triggers#

New Issue Event (Instant) from the Sentry API

Emit new events for issues that have been created or updated.

Try it

Popular Actions#

List Issue Events with the Sentry API

Return a list of events bound to an issue. See the docs here

Try it

List Project Events. with the Sentry API

Return a list of events bound to a project. See the docs here

Try it

List Project Issues. with the Sentry API

Return a list of issues bound to a project. See the docs here

Try it

Update Issue. with the Sentry API

Updates an individual issue's attributes. Only the attributes submitted are modified.See the docs here

Try it

Emergency Push Notification with the Pushover API

Sends an Emergency Push Notification to devices with Pushover. Notifications are repeated until they are acknowledged by the user. More information at Pushing Messages and Message Priority

Try it