Reply To Conversation with Intercom API on New Monitor Event (Instant) from Datadog API

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

Trigger workflow on

New Monitor Event (Instant) from the Datadog API

Next, do this

Reply To Conversation with the Intercom 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 Intercom 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 Reply To Conversation action
1. Connect your Intercom account
2. Select a Conversation ID
3. Select a Reply Type
4. Select a Message Type
5. Configure Body
6. Optional- Configure Attachment URLs
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#

Reply To Conversation on Intercom

Description:Add a reply or a note to an existing conversation thread. [See the documentation](https://developers.intercom.com/docs/references/rest-api/api.intercom.io/conversations/replyconversation).

Version:0.0.2

Key:intercom-reply-to-conversation

View on GitHub

Intercom Overview#

The Intercom API offers rich capabilities for enhancing customer communication and support workflows. By leveraging this API on Pipedream, you can automate tasks, sync customer data across platforms, and create personalized interactions. Whether you are managing user segments, sending targeted messages, or updating customer profiles, the Intercom API's robust set of endpoints allows for intricate and useful automations within your business processes.

Action Code#

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

export default {
  key: "intercom-reply-to-conversation",
  name: "Reply To Conversation",
  description: "Add a reply or a note to an existing conversation thread. [See the documentation](https://developers.intercom.com/docs/references/rest-api/api.intercom.io/conversations/replyconversation).",
  version: "0.0.2",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: false,
  },
  type: "action",
  props: {
    intercom,
    conversationId: {
      propDefinition: [
        intercom,
        "conversationId",
      ],
    },
    replyType: {
      type: "string",
      label: "Reply Type",
      description: "The type of the reply.",
      options: [
        {
          label: "Contact Reply",
          value: "user",
        },
        {
          label: "Admin Reply",
          value: "admin",
        },
      ],
      reloadProps: true,
    },
    messageType: {
      propDefinition: [
        intercom,
        "messageType",
        ({ replyType: type }) => ({
          type,
        }),
      ],
    },
    body: {
      type: "string",
      label: "Body",
      description: "The text body of the comment.",
    },
    attachmentUrls: {
      type: "string[]",
      label: "Attachment URLs",
      description: "A list of image URLs that will be added as attachments. You can include up to 10 URLs.",
      optional: true,
    },
  },
  additionalProps() {
    const {
      replyType,
      replyOnBehalfOf,
    } = this;

    if (replyType === "admin") {
      return {
        adminId: {
          type: "string",
          label: "Admin ID",
          description: "The id of the admin who is authoring the comment.",
          options: async () => {
            const { admins } = await this.intercom.listAdmins();
            return admins.map((admin) => ({
              label: admin.name,
              value: admin.id,
            }));
          },
        },
      };
    }

    return {
      replyOnBehalfOf: {
        type: "string",
        label: "Reply On Behalf Of",
        description: "The user ID of the user on whose behalf the reply is being made.",
        options: [
          {
            label: "Intercom User ID",
            value: "intercom_user_id",
          },
          {
            label: "Email",
            value: "email",
          },
          {
            label: "User ID",
            value: "user_id",
          },
        ],
        reloadProps: true,
      },
      ...(replyOnBehalfOf === "intercom_user_id" && {
        intercomUserId: {
          type: "string",
          label: "Intercom User ID",
          description: "The identifier for the contact as given by Intercom.",
          options: async () => {
            const results = await this.intercom.searchContacts({
              query: {
                field: "role",
                operator: "=",
                value: "user",
              },
            });
            return results.map((user) => ({
              label: user.name || user.id,
              value: user.id,
            }));
          },
        },
      }),
      ...(replyOnBehalfOf === "email" && {
        email: {
          type: "string",
          label: "Email",
          description: "The email you have defined for the user.",
          options: async () => {
            const results = await this.intercom.searchContacts({
              query: {
                field: "role",
                operator: "=",
                value: "user",
              },
            });
            return results.map((user) => ({
              label: user.name || user.id,
              value: user.email,
            }));
          },
        },
      }),
      ...(replyOnBehalfOf === "user_id" && {
        userId: {
          type: "string",
          label: "User ID",
          description: "The external ID you have defined for the contact.",
          options: async () => {
            const results = await this.intercom.searchContacts({
              query: {
                field: "role",
                operator: "=",
                value: "user",
              },
            });
            return results.map((user) => ({
              label: user.name || user.id,
              value: user.external_id,
            }));
          },
        },
      }),
    };
  },
  methods: {
    replyToConversation({
      conversationId, ...args
    } = {}) {
      return this.intercom.makeRequest({
        method: "POST",
        endpoint: `conversations/${conversationId}/parts`,
        ...args,
      });
    },
  },
  async run({ $ }) {
    const {
      replyToConversation,
      conversationId,
      body,
      attachmentUrls,
      replyType,
      adminId,
      intercomUserId,
      email,
      userId,
      messageType,
    } = this;

    const response = await replyToConversation({
      $,
      conversationId,
      data: {
        body,
        attachment_urls: attachmentUrls,
        admin_id: adminId,
        intercom_user_id: intercomUserId,
        email,
        user_id: userId,
        message_type: messageType,
        type: replyType,
      },
    });

    $.export("$summary", "Reply or note added successfully");
    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
Intercom	`intercom`	`app`	This component uses the Intercom app.
Conversation ID	`conversationId`	`string`	Select a value from the drop down menu.
Reply Type	`replyType`	`string`	Select a value from the drop down menu:`{ "label": "Contact Reply", "value": "user" }{ "label": "Admin Reply", "value": "admin" }`
Message Type	`messageType`	`string`	Select a value from the drop down menu.
Body	`body`	`string`	The text body of the comment.
Attachment URLs	`attachmentUrls`	`string[]`	A list of image URLs that will be added as attachments. You can include up to 10 URLs.

Action Authentication#

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

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

Reply To Conversation with Intercom API on New Monitor Event (Instant) from Datadog API

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

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

Developers ♥ Pipedream

1-24of2,900+apps by most popular

1
-
24
of
2,900+
apps by most popular