Send Single Email with Postmark API on New Message In Channels (Instant) from Slack API

Pipedream makes it easy to connect APIs for Postmark, Slack and 2,000+ other apps remarkably fast.

Trigger workflow on

New Message In Channels (Instant) from the Slack API

Next, do this

Send Single Email with the Postmark 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 Slack trigger and Postmark 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 Channels (Instant) trigger
1. Connect your Slack account
2. Optional- Select one or more Channels
3. Configure slackApphook
4. Optional- Configure Resolve Names
5. Optional- Configure Ignore Bots
6. Optional- Configure Ignore replies in threads
Configure the Send Single Email action
1. Connect your Postmark account
2. Configure Subject
3. Optional- Configure HTML Body
4. Optional- Configure Text Body
5. Configure "From" email address
6. Configure Recipient email address(es)
7. Optional- Configure CC email address(es)
8. Optional- Configure BCC email address(es)
9. Optional- Configure Tag
10. Optional- Configure "Reply To" email address
11. Optional- Configure Custom Headers
12. Optional- Configure Track Opens
13. Optional- Select a Track Links
14. Optional- Configure Attachments
15. Optional- Configure Metadata
16. Optional- Configure Message stream
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 Channels (Instant) on Slack

Description:Emit new event when a new message is posted to one or more channels

Version:1.0.14

Key:slack-new-message-in-channels

View on GitHub

Slack Overview#

The Pipedream Slack app enables you to build event-driven workflows that interact with the Slack API. When you authorize the Pipedream app's access to your workspace, you can use Pipedream workflows to perform common Slack actions, or write your own code against the Slack API.

The Pipedream Slack app is not a typical app. You don't interact with it directly as a bot, and it doesn't add custom functionality to your workspace out of the box. It makes it easier to automate anything you'd typically use the Slack API for, using Pipedream workflows.

Automate posting updates to your team channels
Create a bot to answer common questions
Integrate with your existing tools and services
And much more!

Trigger Code#

import common from "../common/base.mjs";
import sampleEmit from "./test-event.mjs";
import constants from "../common/constants.mjs";

export default {
  ...common,
  key: "slack-new-message-in-channels",
  name: "New Message In Channels (Instant)",
  version: "1.0.14",
  description: "Emit new event when a new message is posted to one or more channels",
  type: "source",
  dedupe: "unique",
  props: {
    ...common.props,
    conversations: {
      propDefinition: [
        common.props.slack,
        "conversation",
      ],
      type: "string[]",
      label: "Channels",
      description: "Select one or more channels to monitor for new messages.",
      optional: true,
    },
    // eslint-disable-next-line pipedream/props-description,pipedream/props-label
    slackApphook: {
      type: "$.interface.apphook",
      appProp: "slack",
      async eventNames() {
        return this.conversations || [
          "message",
        ];
      },
    },
    resolveNames: {
      propDefinition: [
        common.props.slack,
        "resolveNames",
      ],
    },
    ignoreBot: {
      propDefinition: [
        common.props.slack,
        "ignoreBot",
      ],
    },
    ignoreThreads: {
      type: "boolean",
      label: "Ignore replies in threads",
      description: "Ignore replies to messages in threads",
      optional: true,
    },
  },
  methods: {
    ...common.methods,
    getSummary() {
      return "New message in channel";
    },
    async processEvent(event) {
      if (event.type !== "message") {
        console.log(`Ignoring event with unexpected type "${event.type}"`);
        return;
      }
      if (event.subtype && !constants.ALLOWED_MESSAGE_IN_CHANNEL_SUBTYPES.includes(event.subtype)) {
        // This source is designed to just emit an event for each new message received.
        // Due to inconsistencies with the shape of message_changed and message_deleted
        // events, we are ignoring them for now. If you want to handle these types of
        // events, feel free to change this code!!
        console.log("Ignoring message with subtype.");
        return;
      }
      if ((this.ignoreBot) && (event.subtype == "bot_message" || event.bot_id)) {
        return;
      }
      console.log(event.s);
      // There is no thread message type only the thread_ts field
      // indicates if the message is part of a thread in the event.
      if (this.ignoreThreads && event.thread_ts) {
        console.log("Ignoring reply in thread");
        return;
      }
      if (this.resolveNames) {
        if (event.user) {
          event.user_id = event.user;
          event.user = await this.getUserName(event.user);
        } else if (event.bot_id) {
          event.bot = await this.getBotName(event.bot_id);
        }
        event.channel_id = event.channel;
        event.channel = await this.getConversationName(event.channel);
        if (event.team) {
          event.team_id = event.team;
          event.team = await this.getTeamName(event.team);
        }
      }
      return event;
    },
  },
  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
Slack	`slack`	`app`	This component uses the Slack app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Channels	`conversations`	`string[]`	Select a value from the drop down menu.
	`slackApphook`	`$.interface.apphook`
Resolve Names	`resolveNames`	`boolean`	Instead of returning `channel`, `team`, and `user` as IDs, return their human-readable names.
Ignore Bots	`ignoreBot`	`boolean`	Ignore messages from bots
Ignore replies in threads	`ignoreThreads`	`boolean`	Ignore replies to messages in threads

Trigger Authentication#

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

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

bookmarks:writecalls:readcalls:writechannels:historychannels:readchannels:writednd:readdnd:writeemoji:readfiles:readgroups:historygroups:readgroups:writeim:historyim:readim:writelinks:readlinks:writempim:historympim:readmpim:writepins:readpins:writereactions:readreactions:writereminders:readreminders:writeremote_files:readremote_files:sharestars:readstars:writeteam:readusergroups:readusergroups:writeusers:readusers:read.emailusers:writechat:write:botchat:write:usercommandsfiles:write:userusers.profile:writeusers.profile:readsearch:read

About Slack#

Slack is a channel-based messaging platform. With Slack, people can work together more effectively, connect all their software tools and services, and find the information they need to do their best work — all within a secure, enterprise-grade environment.

Action#

Send Single Email on Postmark

Description:Send a single email with Postmark [See the documentation](https://postmarkapp.com/developer/api/email-api#send-a-single-email)

Version:0.2.2

Key:postmark-send-single-email

View on GitHub

Postmark Overview#

What Is the Postmark API?

The Postmark API enables developers to easily integrate programmatic emailing into their applications. With the API, developers can create, send, and track transactional emails that are designed to enhance user experience and user engagement. The API also provides developers with access to powerful analytics and insights, such as open/click rates, spam complaints, bounces, and unsubscribes.

What Can You Build With the Postmark API?

The Postmark API allows developers to easily incorporate automated email notifications into their applications. Some examples of what you can build using the API are:

Welcome emails
Password reset emails
Email verification reminders
Event notification emails
Automated transactional emails
Billing and invoicing emails
Receipt emails
Email newsletters
Auto-responders and more!

Action Code#

import common from "../common/common.mjs";

const {
  postmark, ...props
} = common.props;

export default {
  ...common,
  key: "postmark-send-single-email",
  name: "Send Single Email",
  description: "Send a single email with Postmark [See the documentation](https://postmarkapp.com/developer/api/email-api#send-a-single-email)",
  version: "0.2.2",
  type: "action",
  props: {
    postmark,
    subject: {
      type: "string",
      label: "Subject",
      description: "Email subject.",
    },
    htmlBody: {
      type: "string",
      label: "HTML Body",
      description:
        `HTML email message.
        \\
        **Required** if no \`Text Body\` is specified.
        \\
        **Required** to enable \`Open Tracking\`.`,
      optional: true,
    },
    textBody: {
      type: "string",
      label: "Text Body",
      description:
        `Plain text email message.
        \\
        **Required** if no \`HTML Body\` is specified.`,
      optional: true,
    },
    // The above props are intentionally placed first
    ...props,
  },
  async run({ $ }) {
    const response = await this.postmark.sendSingleEmail({
      $,
      data: {
        ...this.getActionRequestCommonData(),
        Subject: this.subject,
        HtmlBody: this.htmlBody,
        TextBody: this.textBody,
      },
    });
    $.export("$summary", "Sent email 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
Postmark	`postmark`	`app`	This component uses the Postmark app.
Subject	`subject`	`string`	Email subject.
HTML Body	`htmlBody`	`string`	HTML email message. Required if no `Text Body` is specified. Required to enable `Open Tracking`.
Text Body	`textBody`	`string`	Plain text email message. Required if no `HTML Body` is specified.
"From" email address	`fromEmail`	`string`	The sender email address. Must have a registered and confirmed Sender Signature. To include a name, use the format 'Full Name <sender@domain.com>' for the address.
Recipient email address(es)	`toEmail`	`string`	Recipient email address. Multiple addresses are comma separated. Max 50.
CC email address(es)	`ccEmail`	`string`	Cc recipient email address. Multiple addresses are comma separated. Max 50.
BCC email address(es)	`bccEmail`	`string`	Bcc recipient email address. Multiple addresses are comma separated. Max 50.
Tag	`tag`	`string`	Email tag that allows you to categorize outgoing emails and get detailed statistics.
"Reply To" email address	`replyTo`	`string`	Reply To override email address. Defaults to the Reply To set in the sender signature.
Custom Headers	`customHeaders`	`string[]`	List of custom headers to include.
Track Opens	`trackOpens`	`boolean`	Activate open tracking for this email. Note: the email must have `HTML Body` to enable open tracking.
Track Links	`trackLinks`	`string`	Select a value from the drop down menu:`NoneHtmlAndTextHtmlOnlyTextOnly`
Attachments	`attachments`	`string[]`	Each attachment should be a string with the parameters separated by a pipe character `\|`, in the format: `Name\|Content\|ContentType`. Alternatively, you can pass a string representing an object. All three parameters are required: `Name` - the filename with extension, i.e. `readme.txt` `Content` - the base64-encoded string with the binary data for the file, i.e. `dGVzdCBjb250ZW50` `ContentType` - the MIME content type, i.e. `text/plain` Example with pipe-separated parameters: `readme.txt\|dGVzdCBjb250ZW50\|text/plain` Example with JSON-stringified object: `{"Name":"readme.txt","Content":"dGVzdCBjb250ZW50","ContentType":"text/plain"}`
Metadata	`metadata`	`object`	Custom metadata key/value pairs.
Message stream	`messageStream`	`string`	Set message stream ID that's used for sending. If not provided, message will default to the outbound transactional stream.