← Sentry + Discord Webhook integrations

Send Message (Advanced) with Discord Webhook APIon Issue Event (Instant) from Sentry API

Pipedream makes it easy to connect APIs for Discord Webhook, Sentry and + other apps remarkably fast.

Trigger workflow on
Issue Event (Instant) from the Sentry API
Next, do this
Send Message (Advanced) with the Discord Webhook API
No credit card required
Trusted by 200,000+ developers from startups to Fortune 500 companies:
Trusted by 200,000+ developers from startups to Fortune 500 companies

Developers Pipedream

Getting Started

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

  1. Select this integration
  2. Configure the Issue Event (Instant) trigger
    1. Connect your Sentry account
    2. Select a Organization
  3. Configure the Send Message (Advanced) action
    1. Connect your Discord Webhook account
    2. Optional- Configure message
    3. Optional- Configure Thread ID
    4. Optional- Configure embeds
    5. Optional- Configure username
    6. Optional- Configure Avatar URL
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. Turn on the trigger

Details

This integration uses pre-built, open source 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

Description:
Version:0.0.1
Key:sentry-issue-events

Trigger Code

const sentry = require('../../sentry.app');

const EVENT_SOURCE_NAME = 'Issue Event (Instant)';

module.exports = {
  key: 'sentry-issue-events',
  version: '0.0.1',
  name: EVENT_SOURCE_NAME,
  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.db.set('integrationSlug', integrationSlug);

      const clientSecret = await this.sentry.getClientSecret(integrationSlug);
      this.db.set('clientSecret', clientSecret);
    },
    async deactivate() {
      const integrationSlug = this.db.get('integrationSlug');
      await this.sentry.disableIntegration(integrationSlug);
    },
  },
  methods: {
    getEventSourceName() {
      return EVENT_SOURCE_NAME;
    },
    generateMeta(event) {
      const {body, headers} = event;
      const {
        'request-id': id,
        'sentry-hook-resource': resourceType,
        'sentry-hook-timestamp': ts,
      } = headers;
      const {action, data} = body;
      const {[resourceType]: resource} = data;
      const summary = `${resourceType} #${resource.id} ${action}`;
      return {
        id,
        summary,
        ts,
      };
    },
  },
  async run(event) {
    const clientSecret = this.db.get('clientSecret');
    if (!this.sentry.isValidSource(event, clientSecret)) {
      this.http.respond({
        statusCode: 404,
      });
      return;
    }

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

    const {body} = event;
    const meta = this.generateMeta(event);
    this.$emit(body, meta);
  },
};

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.
LabelPropTypeDescription
N/Adb$.service.dbThis component uses $.service.db to maintain state between component invocations.
N/Ahttp$.interface.httpThis 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.
SentrysentryappThis component uses the Sentry app.
OrganizationorganizationSlugstringSelect 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.

Create authentication tokens at https://sentry.io/settings/account/api/auth-tokens/ to use the Sentry API on behalf of your user account.

About Sentry

Self-hosted and cloud-based error monitoring

Action

Description:Send a simple or structured message (using embeds) to a Discord channel
Version:0.1.4
Key:discord_webhook-send-message-advanced

Action Code

const discordWebhook = require("../../discord_webhook.app.js");

module.exports = {
  key: "discord_webhook-send-message-advanced",
  name: "Send Message (Advanced)",
  description: "Send a simple or structured message (using embeds) to a Discord channel",
  version: "0.1.4",
  type: "action",
  props: {
    discordWebhook,
    message: {
      propDefinition: [
        discordWebhook,
        "message",
      ],
      optional: true,
    },
    threadID: {
      propDefinition: [
        discordWebhook,
        "threadID",
      ],
    },
    embeds: {
      propDefinition: [
        discordWebhook,
        "embeds",
      ],
    },
    username: {
      propDefinition: [
        discordWebhook,
        "username",
      ],
    },
    avatarURL: {
      propDefinition: [
        discordWebhook,
        "avatarURL",
      ],
    },
  },
  async run() {
    const content = this.message;
    const {
      avatarURL,
      embeds,
      threadID,
      username,
    } = this;

    if (!content && !embeds) {
      throw new Error("This action requires at least 1 message OR embeds object. Please enter one or the other above.");
    }

    // No interesting data is returned from Discord
    await this.discordWebhook.sendMessage({
      avatarURL,
      embeds,
      content,
      threadID,
      username,
    });
  },
};

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.

LabelPropTypeDescription
Discord WebhookdiscordWebhookappThis component uses the Discord Webhook app.
messagemessagestring

Enter a simple message up to 2000 characters. This is the most commonly used field. However, it's optional if you pass embed content.

Thread IDthreadIDstring

If provided, the message will be posted to this thread

embedsembedsany

Optionally pass an array of embed objects. E.g., {{ [{"description":"Use markdown including *Italic* **bold** __underline__ ~~strikeout~~ [hyperlink](https://google.com) `code`"}] }}. To pass data from another step, enter a reference using double curly brackets (e.g., {{steps.mydata.$return_value}}).
Tip: Construct the embeds array in a Node.js code step, return it, and then pass the return value to this step.

usernameusernamestring

Overrides the current username of the webhook

Avatar URLavatarURLstring

If used, it overrides the default avatar of the webhook

Action Authentication

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

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

webhook.incomingemailidentify

About Discord Webhook

Use this app to send messages to a channel using Discord's incoming webhooks

About Pipedream

Stop writing boilerplate code, struggling with authentication and managing infrastructure. Start connecting APIs with code-level control when you need it — and no code when you don't.

Into to Pipedream
Watch us build a workflow
Watch us build a workflow
4 min
Watch now ➜
"The past few weeks, I truly feel like the clichéd 10x engineer."
@heyellieday
Powerful features that scale
Manage concurrency and execution rate
Manage concurrency and execution rate

Queue up to 10,000 events per workfow and manage the concurrency and rate at which workflows are triggered.

Process large payloads up to 5 terabytes
Process large payloads up to 5 terabytes

Large file support enables you to trigger workflows with any data (e.g., large JSON files, images and videos) up to 5 terabytes.

Return custom responses to HTTP requests
Return custom responses to HTTP requests

Return any JSON-serializable response from an HTTP triggered workflow using $respond().

Use most npm packages
Use most npm packages

To use any npm package, just require() it -- there's no npm install or package.json required.

Maintain state between executions
Maintain state between executions

Use $checkpoint to save state in one workflow invocation and read it the next time your workflow runs.

Pass data between steps
Pass data between steps

Return data from any step to inspect it in a human-friendly way and reference the data in future steps via the steps object.