Send Message With File with Discord API on New Monitor Event (Instant) from Datadog API

Pipedream makes it easy to connect APIs for Discord, Datadog and 2,400+ other apps remarkably fast.

Trigger workflow on

New Monitor Event (Instant) from the Datadog API

Next, do this

Send Message With File with the Discord 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 Datadog trigger and Discord action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Monitor Event (Instant) trigger
1. Connect your Datadog account
2. Select a Region
3. Select one or more Monitors
Configure the Send Message With File action
1. Connect your Discord account
2. Configure channel
3. Optional- Configure Message
4. Optional- Configure Thread ID
5. Optional- Configure Username
6. Optional- Configure Avatar URL
7. Optional- Configure Include link to workflow
8. Optional- Configure Suppress notifications
9. Optional- Configure File URL
10. Optional- Configure File Path
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 Monitor Event (Instant) on Datadog

Description:Emit new events captured by a Datadog monitor

Version:0.1.2

Key:datadog-new-monitor-event

View on GitHub

Datadog Overview#

The Datadog API, accessible through Pipedream, empowers you to programmatically interact with Datadog's monitoring and analytics platform. This enables developers to automate the retrieval of monitoring data, manage alert configurations, and synchronize service health information across systems. With Pipedream's serverless execution model, you can create intricate workflows that react to Datadog events or metrics, manipulate the data, and pass it on to other services or even Datadog itself for a cohesive operational ecosystem.

Trigger Code#

import datadog from "../../datadog.app.mjs";
import { payloadFormat } from "../common/payload-format.mjs";

export default {
  key: "datadog-new-monitor-event",
  name: "New Monitor Event (Instant)",
  description: "Emit new events captured by a Datadog monitor",
  dedupe: "unique",
  version: "0.1.2",
  type: "source",
  props: {
    datadog,
    db: "$.service.db",
    http: {
      type: "$.interface.http",
      customResponse: true,
    },
    region: {
      propDefinition: [
        datadog,
        "region",
      ],
    },
    monitors: {
      propDefinition: [
        datadog,
        "monitors",
        (c) => ({
          region: c.region,
        }),
      ],
    },
  },
  hooks: {
    async deploy() {
      // emit historical events
      const { events } = await this.datadog.getEvents({
        params: {
          start: Math.floor(this.datadog.daysAgo(7) / 1000), // one week ago
          end: Math.floor(Date.now() / 1000), // now
        },
        region: this.region,
      });
      const relevantEvents = events.filter((event) => this.monitors.includes(event.monitor_id));

      for (const event of relevantEvents.reverse().slice(-25)) {
        const payload = {
          alertTitle: event.eventTitle,
          alertType: event.alert_type,
          date: event.date_happened,
          eventMsg: event.text,
          eventTitle: event.title,
          hostname: event.host,
          id: event.id,
          lastUpdated: event.date_happened,
          link: `https://app.datadoghq.com${event.url}`,
          priority: event.priority,
          tags: event.tags.join(),
        };
        const meta = this.generateMeta(payload);
        this.$emit(payload, meta);
      }
    },
    async activate() {
      const {
        name: webhookName,
        secretKey: webhookSecretKey,
      } = await this.datadog.createWebhook(
        this.http.endpoint,
        payloadFormat,
        this.region,
      );

      console.log(`Created webhook "${webhookName}"`);
      this._setWebhookName(webhookName);
      this._setWebhookSecretKey(webhookSecretKey);

      await Promise.all(
        this.monitors.map((monitorId) =>
          this.datadog.addWebhookNotification(webhookName, monitorId, this.region)),
      );
    },
    async deactivate() {
      const webhookName = this._getWebhookName();
      await this.datadog.removeWebhookNotifications(webhookName, this.region);
      await this.datadog.deleteWebhook(webhookName, this.region);
    },
  },
  methods: {
    _getWebhookName() {
      return this.db.get("webhookName");
    },
    _setWebhookName(webhookName) {
      this.db.set("webhookName", webhookName);
    },
    _getWebhookSecretKey() {
      return this.db.get("webhookSecretKey");
    },
    _setWebhookSecretKey(webhookSecretKey) {
      this.db.set("webhookSecretKey", webhookSecretKey);
    },
    generateMeta(data) {
      const {
        id,
        eventTitle: summary,
        date: ts,
      } = data;
      return {
        id,
        summary,
        ts,
      };
    },
  },
  async run(event) {
    const webhookSecretKey = this._getWebhookSecretKey();
    if (!this.datadog.isValidSource(event, webhookSecretKey)) {
      console.log("Skipping event from unrecognized source");
      this.http.respond({
        status: 404,
      });
      return;
    }

    // Acknowledge the event back to Datadog.
    this.http.respond({
      status: 200,
    });

    const { body } = event;
    const meta = this.generateMeta(body);
    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.

Label	Prop	Type	Description
Datadog	`datadog`	`app`	This component uses the Datadog 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.
Region	`region`	`string`	Select a value from the drop down menu:`{ "label": "US1 - East", "value": "datadoghq.com" }{ "label": "US3 - West", "value": "us3.datadoghq.com" }{ "label": "US5 - Central", "value": "us5.datadoghq.com" }{ "label": "EU1 - Europe", "value": "datadoghq.eu" }{ "label": "US1-FED (FedRamp)", "value": "ddog-gov.com" }`
Monitors	`monitors`	`integer[]`	Select a value from the drop down menu.

Trigger Authentication#

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

Manage your account’s API and applications keys in Datadog

About Datadog#

Cloud monitoring as a service

Action#

Send Message With File on Discord

Description:Post a message with an attached file

Version:1.1.1

Key:discord-send-message-with-file

View on GitHub

Discord Overview#

The Discord API interacts seamlessly with Pipedream, empowering you to craft customized automations and workflows for your Discord server. With this powerful integration, you can automate tasks like message posting, user management, and notifications, based on a myriad of triggers and actions from different apps. These automations can enhance the Discord experience for community moderators and members, by synchronizing with external tools, organizing community engagement, and streamlining notifications.

Action Code#

import common from "../common/common.mjs";
import { axios } from "@pipedream/platform";
import fs from "fs";
import { ConfigurationError } from "@pipedream/platform";

export default {
  ...common,
  key: "discord-send-message-with-file",
  name: "Send Message With File",
  description: "Post a message with an attached file",
  version: "1.1.1",
  type: "action",
  props: {
    ...common.props,
    message: {
      propDefinition: [
        common.props.discord,
        "message",
      ],
      optional: true,
    },
    fileUrl: {
      propDefinition: [
        common.props.discord,
        "fileUrl",
      ],
    },
    filePath: {
      propDefinition: [
        common.props.discord,
        "filePath",
      ],
    },
  },
  async run({ $ }) {
    const {
      message,
      avatarURL,
      threadID,
      username,
      fileUrl,
      filePath,
      includeSentViaPipedream,
      suppressNotifications,
    } = this;

    if (!fileUrl && !filePath) {
      throw new ConfigurationError("This action requires either File URL or File Path. Please enter one or the other above.");
    }

    const file = fileUrl
      ? await axios($, {
        method: "get",
        url: fileUrl,
        responseType: "stream",
      })
      : fs.createReadStream(filePath);

    try {
      const resp = await this.discord.sendMessage(this.channel, {
        avatar_url: avatarURL,
        username,
        file,
        flags: this.getMessageFlags(suppressNotifications),
        content: includeSentViaPipedream
          ? this.appendPipedreamText(message ?? "")
          : message,
      }, {
        thread_id: threadID,
      });
      $.export("$summary", "Message sent successfully");
      return resp || {
        success: true,
      };
    } catch (err) {
      const unsentMessage = this.getUserInputProps();
      $.export("unsent", unsentMessage);
      throw err;
    }
  },
};

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
Discord	`discord`	`app`	This component uses the Discord app.
channel	`channel`	`$.discord.channel`
Message	`message`	`string`	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 ID	`threadID`	`string`	If provided, the message will be posted to this thread
Username	`username`	`string`	Overrides the current username of the webhook
Avatar URL	`avatarURL`	`string`	If used, it overrides the default avatar of the webhook. Note: Consecutive posts by the same username within 10 minutes of each other will not display updated avatar.
Include link to workflow	`includeSentViaPipedream`	`boolean`	Defaults to `true`, includes a link to this workflow at the end of your Discord message.
Suppress notifications	`suppressNotifications`	`boolean`	Defaults to `false`, sends the message as silent, triggers no notifications to clients.
File URL	`fileUrl`	`string`	The URL of the file to attach. Must specify either File URL or File Path.
File Path	`filePath`	`string`	The path to the file, e.g. `/tmp/myFile.csv`. Must specify either File URL or File Path.

Action Authentication#

Discord uses OAuth authentication. When you connect your Discord account, Pipedream will open a popup window where you can sign into Discord 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 API.

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

botemailidentifyguilds