Send Message with Mailjet API on New Message in Channel from Discord Bot API

Pipedream makes it easy to connect APIs for Mailjet, Discord Bot and 2,000+ other apps remarkably fast.

Trigger workflow on

New Message in Channel from the Discord Bot API

Next, do this

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

Select this integration
Configure the New Message in Channel trigger
1. Connect your Discord Bot account
2. Select a Guild
3. Select one or more Channels
4. Optional- Configure Emit messages as a single event
5. Configure timer
Configure the Send Message action
1. Connect your Mailjet account
2. Configure From Email
3. Optional- Configure From Name
4. Optional- Configure Sender
5. Optional- Configure To
6. Optional- Configure Cc
7. Optional- Configure Bcc
8. Optional- Configure Subject
9. Optional- Configure Text Part
10. Optional- Configure HTML Part
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 Message in Channel on Discord Bot

Description:Emit new event for each message posted to one or more channels

Version:0.0.18

Key:discord_bot-new-message-in-channel

View on GitHub

Discord Bot Overview#

The Discord Bot API unlocks the power to interact with Discord users and channels programmatically, making it possible to automate messages, manage servers, and integrate with other services. With Pipedream's serverless platform, you can create complex workflows that respond to events in Discord, process data, and trigger actions in other apps. This opens up opportunities for community engagement, content moderation, analytics, and more, without the overhead of managing infrastructure.

Trigger Code#

import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";
import maxBy from "lodash.maxby";
import common from "../common.mjs";
import sampleEmit from "./test-event.mjs";

const { discord } = common.props;

export default {
  ...common,
  key: "discord_bot-new-message-in-channel",
  name: "New Message in Channel",
  description: "Emit new event for each message posted to one or more channels",
  type: "source",
  version: "0.0.18",

  dedupe: "unique", // Dedupe events based on the Discord message ID
  props: {
    ...common.props,
    db: "$.service.db",
    channels: {
      type: "string[]",
      label: "Channels",
      description: "The channels you'd like to watch for new messages",
      propDefinition: [
        discord,
        "channelId",
        ({ guildId }) => ({
          guildId,
        }),
      ],
    },
    emitEventsInBatch: {
      type: "boolean",
      label: "Emit messages as a single event",
      description:
        "If `true`, all messages are emitted as an array, within a single Pipedream event. Defaults to `false`, emitting each Discord message as its own event in Pipedream",
      optional: true,
      default: false,
    },
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
  },
  async run({ $ }) {
    // We store a cursor to the last message ID
    let lastMessageIDs = this._getLastMessageIDs();

    // If this is our first time running this source,
    // get the last N messages, emit them, and checkpoint
    for (const channelId of this.channels) {
      let lastMessageID;
      let messages = [];

      if (!lastMessageID) {
        messages = await this.discord.getMessages({
          $,
          channelId,
          params: {
            limit: 100,
          },
        });

        lastMessageID = messages.length
          ? maxBy(messages, (message) => message.id).id
          : 1;

      } else {
        let newMessages = [];

        do {
          newMessages = await this.discord.getMessages({
            $,
            channelId,
            params: {
              after: lastMessageIDs[channelId],
            },
          });

          messages = messages.concat(newMessages);

          lastMessageID = newMessages.length
            ? maxBy(newMessages, (message) => message.id).id
            : lastMessageIDs[channelId];

        } while (newMessages.length);
      }

      // Set the new high water mark for the last message ID
      // for this channel
      lastMessageIDs[channelId] = lastMessageID;

      if (!messages.length) {
        console.log(`No new messages in channel ${channelId}`);
        return;
      }

      console.log(`${messages.length} new messages in channel ${channelId}`);

      // Batched emits do not take advantage of the built-in deduper
      if (this.emitEventsInBatch) {
        const suffixChar =
          messages.length > 1
            ? "s"
            : "";

        this.$emit(messages, {
          summary: `${messages.length} new message${suffixChar}`,
          id: lastMessageID,
        });

      } else {
        messages.forEach((message) => {
          this.$emit(message, {
            summary: message.content,
            id: message.id, // dedupes events based on this ID
          });
        });
      }
    }

    // Set the last message ID for the next run
    this._setLastMessageIDs(lastMessageIDs);
  },
  sampleEmit,
};

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
Discord Bot	`discord`	`app`	This component uses the Discord Bot app.
Guild	`guildId`	`string`	Select a value from the drop down menu.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Channels	`channels`	`string[]`	Select a value from the drop down menu.
Emit messages as a single event	`emitEventsInBatch`	`boolean`	If `true`, all messages are emitted as an array, within a single Pipedream event. Defaults to `false`, emitting each Discord message as its own event in Pipedream
	`timer`	`$.interface.timer`

Trigger Authentication#

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

This app allows you to use the Discord API using your own Discord bot. If you don't want to use a custom bot, and you just need to use the Discord API, exit this screen and use the Discord app, instead.

If you want to use your own Discord bot, but haven't created one yet, see these instructions or watch this video. You'll need to add this bot to your server(s) to make successful API requests.

Once you've created your bot, you'll find the Bot token within the Bot section of your app. Enter that token below.

About Discord Bot#

Use this app to interact with the Discord API using a bot in your account

Action#

Send Message on Mailjet

Description:Send a message via Send API v3. Send API v3 is built mainly for speed, allowing you to send up to 100 messages in a single API call. [See the docs here](https://dev.mailjet.com/email/reference/send-emails/#v3_1_post_send)

Version:0.0.2

Key:mailjet-send-message

View on GitHub

Mailjet Overview#

Mailjet's API offers the power to craft, send, and track emails with finesse. You can wield it to automate email sequences, synchronize email lists with your databases, and send transactional emails with personalized content. It's a playground for creating tailored email campaigns and dissecting campaign performance with rich analytics.

Action Code#

import mailjetApp from "../../mailjet.app.mjs";

export default {
  key: "mailjet-send-message",
  name: "Send Message",
  description: "Send a message via Send API v3. Send API v3 is built mainly for speed, allowing you to send up to 100 messages in a single API call. [See the docs here](https://dev.mailjet.com/email/reference/send-emails/#v3_1_post_send)",
  type: "action",
  version: "0.0.2",
  props: {
    mailjetApp,
    fromEmail: {
      type: "string",
      label: "From Email",
      description: "Specifies the sender email address.",
    },
    fromName: {
      type: "string",
      label: "From Name",
      description: "Sender name that will be displayed in the recipient's mailbox.",
      optional: true,
    },
    sender: {
      type: "boolean",
      label: "Sender",
      description: "When true, default sender email address will be used to send the message, while the **From Email** will be displayed in the recipient's inbox. In such cases, it is not necessary for the **From Email** to be verified. However, the information will be displayed in the inbox as `From {from_email} via / sent on behalf of {sender_domain}`.",
      optional: true,
    },
    to: {
      type: "string",
      label: "To",
      description: "The email address (and name, optionally) of the recipients. Acceptable formats are `john@example.com` or `<john@example.com>` or `\"John Doe\" <john@example.com>`. Can include multiple contacts, which should be separated by commas. Can be used together with **Cc** and **Bcc**.",
      optional: true,
    },
    cc: {
      type: "string",
      label: "Cc",
      description: "The email address (and name, optionally) of a recipient who is supposed to receive a carbon copy (cc) of this message. Used together with **To** and **Bcc** (optional). Acceptable formats are `john@example.com` or `<john@example.com>` or `\"John Doe\" <john@example.com>`. Can include multiple contacts, which should be separated by commas.",
      optional: true,
    },
    bcc: {
      type: "string",
      label: "Bcc",
      description: "The email address (and name, optionally) of a recipient who is supposed to receive a blind carbon copy (bcc) of this message. Use this when you do not want your other recipients to see that you are sending a copy of the message to this email address. Used together with **To** and **Cc** (optional). Acceptable formats are `john@example.com` or `<john@example.com>` or `\"John Doe\" <john@example.com>`. Can include multiple contacts, which should be separated by commas.",
      optional: true,
    },
    subject: {
      type: "string",
      label: "Subject",
      description: "The email subject line.",
      optional: true,
    },
    textPart: {
      type: "string",
      label: "Text Part",
      description: "Provides the Text part of the message. Mandatory, if the Html-part parameter is not specified.",
      optional: true,
    },
    htmlPart: {
      type: "string",
      label: "HTML Part",
      description: "Provides the HTML part of the message. Mandatory, if the Text-part parameter is not specified.",
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      fromEmail,
      fromName,
      sender,
      to,
      cc,
      bcc,
      subject,
      textPart,
      htmlPart,
    } = this;

    try {
      const { body: { Sent: response } } =
        await this.mailjetApp.sendMessage({
          data: {
            "FromEmail": fromEmail,
            "FromName": fromName,
            "Sender": sender,
            "To": to,
            "Cc": cc,
            "Bcc": bcc,
            "Subject": subject,
            "Text-part": textPart,
            "Html-part": htmlPart,
          },
        });

      $.export("$summary", `Successfully sent email message with ID ${response[0].MessageID}`);

      return response[0];

    } catch (error) {
      throw error.response?.res?.statusMessage ?? error;
    }
  },
};

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
Mailjet	`mailjetApp`	`app`	This component uses the Mailjet app.
From Email	`fromEmail`	`string`	Specifies the sender email address.
From Name	`fromName`	`string`	Sender name that will be displayed in the recipient's mailbox.
Sender	`sender`	`boolean`	When true, default sender email address will be used to send the message, while the From Email will be displayed in the recipient's inbox. In such cases, it is not necessary for the From Email to be verified. However, the information will be displayed in the inbox as `From {from_email} via / sent on behalf of {sender_domain}`.
To	`to`	`string`	The email address (and name, optionally) of the recipients. Acceptable formats are `john@example.com` or `<john@example.com>` or `"John Doe" <john@example.com>`. Can include multiple contacts, which should be separated by commas. Can be used together with Cc and Bcc.
Cc	`cc`	`string`	The email address (and name, optionally) of a recipient who is supposed to receive a carbon copy (cc) of this message. Used together with To and Bcc (optional). Acceptable formats are `john@example.com` or `<john@example.com>` or `"John Doe" <john@example.com>`. Can include multiple contacts, which should be separated by commas.
Bcc	`bcc`	`string`	The email address (and name, optionally) of a recipient who is supposed to receive a blind carbon copy (bcc) of this message. Use this when you do not want your other recipients to see that you are sending a copy of the message to this email address. Used together with To and Cc (optional). Acceptable formats are `john@example.com` or `<john@example.com>` or `"John Doe" <john@example.com>`. Can include multiple contacts, which should be separated by commas.
Subject	`subject`	`string`	The email subject line.
Text Part	`textPart`	`string`	Provides the Text part of the message. Mandatory, if the Html-part parameter is not specified.
HTML Part	`htmlPart`	`string`	Provides the HTML part of the message. Mandatory, if the Text-part parameter is not specified.

Action Authentication#

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

You can get your API and Secret Keys in the API Key Management page in your Mailjet account.

About Mailjet#

Mailjet is an easy-to-use all-in-one e-mail platform. With our transactional and marketing e-mail solution, it’s never been easier to get your emails into the inbox!

More Ways to Connect Mailjet + Discord Bot#

Other Popular Integrations#

Create Contact with Mailjet API on New Message in Channel from Discord Bot API

Discord Bot + Mailjet

Send Message with Mailjet API on New Message in Channel from Discord Bot API

Pipedream makes it easy to connect APIs for Mailjet, Discord Bot and 2,000+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of2,000+apps by most popular

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