← HTTP / Webhook + Mailgun integrations

Mailgun Send Email with Mailgun APIon New Requests from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Mailgun, HTTP / Webhook and + other apps remarkably fast.

Trigger workflow on
New Requests from the HTTP / Webhook API
Next, do this
Mailgun Send Email with the Mailgun 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 HTTP / Webhook trigger and Mailgun 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 New Requests trigger
    1. Optional- Configure Body Only
    2. Optional- Configure Response Status Code
    3. Optional- Configure Response Content-Type
    4. Optional- Configure Response Body
    5. Connect your HTTP / Webhook account
  3. Configure the Mailgun Send Email action
    1. Connect your Mailgun account
    2. Select a Domain Name
    3. Configure From Name
    4. Configure From Email
    5. Optional- Configure Reply-To
    6. Configure To
    7. Optional- Configure CC
    8. Optional- Configure BCC
    9. Configure Subject
    10. Configure Message Body (text)
    11. Optional- Configure Message Body (HTML)
    12. Configure Send in test mode?
    13. Optional- Configure Use DKIM?
    14. Optional- Configure Use Tracking?
    15. Configure Halt on error?
  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:Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.
Version:0.1.1
Key:http-new-requests

Trigger Code

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

// Core HTTP component
export default {
  key: "http-new-requests",
  name: "New Requests",
  description: "Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.",
  version: "0.1.1",
  type: "source",
  props: {
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    emitBodyOnly: {
      type: "boolean",
      label: "Body Only",
      description: "This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.",
      optional: true,
      default: false,
    },
    resStatusCode: {
      type: "string",
      label: "Response Status Code",
      description: "The status code to return in the HTTP response",
      optional: true,
      default: "200",
    },
    resContentType: {
      type: "string",
      label: "Response Content-Type",
      description: "The `Content-Type` of the body returned in the HTTP response",
      optional: true,
      default: "application/json",
    },
    resBody: {
      type: "string",
      label: "Response Body",
      description: "The body to return in the HTTP response",
      optional: true,
      default: "{ \"success\": true }",
    },
    http,
  },
  async run(event) {
    const summary = `${event.method} ${event.path}`;

    this.httpInterface.respond({
      status: this.resStatusCode,
      body: this.resBody,
      headers: {
        "content-type": this.resContentType,
      },
    });

    if (this.emitBodyOnly) {
      this.$emit(event.body, {
        summary,
      });
    } else {
      this.$emit(event, {
        summary,
      });
    }
  },
};

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/AhttpInterface$.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.
Body OnlyemitBodyOnlyboolean

This source emits an event representing the full HTTP request by default. Select true to emit the body only.

Response Status CoderesStatusCodestring

The status code to return in the HTTP response

Response Content-TyperesContentTypestring

The Content-Type of the body returned in the HTTP response

Response BodyresBodystring

The body to return in the HTTP response

HTTP / WebhookhttpappThis component uses the HTTP / Webhook app.

Trigger Authentication

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook

Get a unique URL where you can send HTTP or webhook requests

Action

Description:Send email with Mailgun.
Version:0.0.1
Key:mailgun-send-email

Action Code

const mailgun = require("../../mailgun.app.js");

module.exports = {
  key: "mailgun-send-email",
  name: "Mailgun Send Email",
  description: "Send email with Mailgun.",
  version: "0.0.1",
  type: "action",
  props: {
    mailgun,
    domain: {
      propDefinition: [
        mailgun,
        "domain",
      ],
    },
    fromName: {
      type: "string",
      label: "From Name",
      description: "Sender name",
    },
    from: {
      type: "string",
      label: "From Email",
      description: "Sender email address",
    },
    replyTo: {
      type: "string",
      label: "Reply-To",
      description: "Sender reply email address",
      optional: true,
    },
    to: {
      type: "string[]",
      label: "To",
      description: "Recipient email address(es)",
    },
    cc: {
      type: "string[]",
      label: "CC",
      description: "Copy email address(es)",
      optional: true,
    },
    bcc: {
      type: "string[]",
      label: "BCC",
      description: "Blind copy email address(es)",
      optional: true,
    },
    subject: {
      type: "string",
      label: "Subject",
      description: "Message subject",
    },
    text: {
      type: "string",
      label: "Message Body (text)",
    },
    html: {
      type: "string",
      label: "Message Body (HTML)",
      optional: true,
    },
    testMode: {
      type: "boolean",
      label: "Send in test mode?",
      default: true,
      description: "Enables sending in test mode. For more information, see the [Mailgun API documentation](https://documentation.mailgun.com/en/latest/api-sending.html#sending)",
    },
    dkim: {
      type: "boolean",
      label: "Use DKIM?",
      default: true,
      description: "Enables or disables DKIM signatures. For more information, see the [Mailgun API documentation](https://documentation.mailgun.com/en/latest/api-sending.html#sending)",
      optional: true,
    },
    tracking: {
      type: "boolean",
      label: "Use Tracking?",
      default: true,
      description: "Enables or disables tracking. For more information, see the [Mailgun API documentation](https://documentation.mailgun.com/en/latest/api-sending.html#sending)",
      optional: true,
    },
    haltOnError: {
      propDefinition: [
        mailgun,
        "haltOnError",
      ],
    },
  },
  async run () {
    try {
      const msg = {
        "from": `${this.fromName} <${this.from}>`,
        "to": this.to,
        "cc": this.cc,
        "bcc": this.bcc,
        "subject": this.subject,
        "text": this.text,
        "html": this.html,
        "o:testmode": this.testMode,
      };
      if (this.replyTo) {
        msg["h:Reply-To"] = this.replyTo;
      }
      if (this.dkim !== null) {
        msg["o:dkim"] = this.dkim
          ? "yes"
          : "no";
      }
      if (this.tracking) {
        msg["o:tracking"] = "yes";
      }
      return await this.mailgun.api("messages").create(this.domain, msg);
    } catch (err) {
      if (this.haltOnError) {
        throw err;
      }
      return 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.

LabelPropTypeDescription
MailgunmailgunappThis component uses the Mailgun app.
Domain NamedomainstringSelect a value from the drop down menu.
From NamefromNamestring

Sender name

From Emailfromstring

Sender email address

Reply-ToreplyTostring

Sender reply email address

Totostring[]

Recipient email address(es)

CCccstring[]

Copy email address(es)

BCCbccstring[]

Blind copy email address(es)

Subjectsubjectstring

Message subject

Message Body (text)textstring
Message Body (HTML)htmlstring
Send in test mode?testModeboolean

Enables sending in test mode. For more information, see the Mailgun API documentation

Use DKIM?dkimboolean

Enables or disables DKIM signatures. For more information, see the Mailgun API documentation

Use Tracking?trackingboolean

Enables or disables tracking. For more information, see the Mailgun API documentation

Halt on error?haltOnErrorboolean

Action Authentication

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

Get your API Key in the Control Panel, specifically in Settings > API Keys. More info in docs.

If your Mailgun account resides in the EU, choose the EU option in the Region field. Otherwise, choose the US (non-EU) region.

About Mailgun

Sending, receiving and tracking email effortlessly

More Ways to Connect Mailgun + HTTP / Webhook

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.