Send email with Nodemailer with Helper Functions API on New Item in Feed from RSS API

Pipedream makes it easy to connect APIs for Helper Functions, RSS and 2,400+ other apps remarkably fast.

Trigger workflow on

New Item in Feed from the RSS API

Next, do this

Send email with Nodemailer with the Helper Functions 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 RSS trigger and Helper Functions action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Item in Feed trigger
1. Connect your RSS account
2. Configure timer
3. Configure Feed URL
4. Configure Published After
Configure the Send email with Nodemailer action
1. Connect your Helper Functions account
2. Configure host
3. Configure port
4. Optional- Configure secure
5. Optional- Configure Ignore TLS
6. Optional- Configure Require TLS
7. Configure user
8. Configure pass
9. Configure from
10. Configure to
11. Optional- Configure cc
12. Configure subject
13. Optional- Configure text
14. Optional- Configure html
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 Item in Feed on RSS

Description:Emit new items from an RSS feed

Version:1.2.7

Key:rss-new-item-in-feed

View on GitHub

RSS Overview#

The RSS app allows users to automatically fetch and parse updates from web feeds. This functionality is pivotal for staying abreast of content changes or updates from websites, blogs, and news outlets that offer RSS feeds. With Pipedream, you can harness the RSS API to trigger workflows that enable a broad range of automations, like content aggregation, monitoring for specific keywords, notifications, and data synchronization across platforms.

Trigger Code#

import { defineSource } from "@pipedream/types";
import rss from "../../app/rss.app.mjs";
import rssCommon from "../common/common.mjs";
export default defineSource({
    ...rssCommon,
    key: "rss-new-item-in-feed",
    name: "New Item in Feed",
    description: "Emit new items from an RSS feed",
    version: "1.2.7",
    type: "source",
    dedupe: "unique",
    props: {
        ...rssCommon.props,
        url: {
            propDefinition: [
                rss,
                "url",
            ],
        },
        publishedAfter: {
            type: "string",
            label: "Published After",
            description: "Emit items published after the specified date in ISO 8601 format .e.g `2022-12-07T12:57:10+07:00`",
            default: new Date(Date.now() - 24 * 60 * 60 * 1000).toISOString(), // default to one day ago
        },
    },
    hooks: {
        async activate() {
            // Try to parse the feed one time to confirm we can fetch and parse.
            // The code will throw any errors to the user.
            await this.rss.fetchAndParseFeed(this.url);
        },
    },
    methods: {
        ...rssCommon.methods,
        generateMeta: function (item) {
            return {
                id: this.rss.itemKey(item),
                summary: item.title,
                ts: Date.now(),
            };
        },
    },
    async run() {
        const items = await this.rss.fetchAndParseFeed(this.url);
        for (const item of items.reverse()) {
            const publishedAfter = +new Date(this.publishedAfter);
            const ts = this.rss.itemTs(item);
            if (Number.isNaN(publishedAfter) || publishedAfter > ts) {
                continue;
            }
            const meta = this.generateMeta(item);
            this.$emit(item, 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
RSS	`rss`	`app`	This component uses the RSS app.
	`timer`	`$.interface.timer`	How often you want to poll the feed for new items
Feed URL	`url`	`string`	Enter the URL for any public RSS feed
Published After	`publishedAfter`	`string`	Emit items published after the specified date in ISO 8601 format .e.g `2022-12-07T12:57:10+07:00`

Trigger Authentication#

The RSS API does not require authentication.

About RSS#

Real Simple Syndication

Action#

Send email with Nodemailer on Helper Functions

Description:Sends an email using the nodemailer package

Version:0.2.1

Key:helper_functions-send-email-with-nodemailer

View on GitHub

Helper Functions Overview#

The Helper Functions app on Pipedream is a set of pre-built functions that streamline common tasks in your workflows. It acts like a Swiss Army knife for developers, providing essential tools such as format conversion, date manipulation, and text processing. By leveraging these functions, you can reduce the boilerplate code needed for routine operations, speeding up the development of intricate automations. The Helper Functions API can be a game changer when it comes to tasks like parsing dates in user-friendly formats, encoding and decoding data, or generating UUIDs, making them more efficient and less error-prone.

Action Code#

// legacy_hash_id: a_EViLg3
import nodemailer from "nodemailer";
import helper_functions from "../../helper_functions.app.mjs";

export default {
  key: "helper_functions-send-email-with-nodemailer",
  name: "Send email with Nodemailer",
  description: "Sends an email using the nodemailer package",
  version: "0.2.1",
  type: "action",
  props: {
    helper_functions,
    host: {
      type: "string",
      description: "The hostname or IP address of your SMTP server",
    },
    port: {
      type: "string",
      description: "The port your SMTP server listens on (defaults to 587 if is secure is false or 465 if true)",
    },
    secure: {
      type: "boolean",
      description: "If `true` the connection will use TLS when connecting to server. If `false` (the default) then TLS is used if server supports the **STARTTLS** extension. In most cases set this value to `true` if you are connecting to port 465. For port 587 or 25 keep it `false`",
      optional: true,
    },
    ignoreTLS: {
      type: "boolean",
      label: "Ignore TLS",
      description: "If this is `true` and **secure** is `false` then TLS is not used even if the server supports **STARTTLS** extension",
      optional: true,
    },
    requireTLS: {
      type: "boolean",
      label: "Require TLS",
      description: "If this is `true` and **secure** is `false` then Nodemailer tries to use **STARTTLS** even if the server does not advertise support for it. If the connection can not be encrypted then message is not sent",
      optional: true,
    },
    user: {
      type: "string",
      description: "The username you use to connect to your SMTP server",
    },
    pass: {
      type: "string",
      description: "Your password",
    },
    from: {
      type: "string",
      description: "The email address of the sender. All email addresses can be plain 'sender@server.com' or formatted '\"Sender Name\" <sender@server.com>'",
    },
    to: {
      type: "string",
      description: "Comma separated list or an array of recipients email addresses that will appear on the To: field",
    },
    cc: {
      type: "string",
      description: "Comma separated list or an array of recipients email addresses that will appear on the Cc: field",
      optional: true,
    },
    subject: {
      type: "string",
      description: "The subject of the email",
    },
    text: {
      type: "string",
      description: "The plain text version of the message",
      optional: true,
    },
    html: {
      type: "string",
      description: "The HTML version of the message",
      optional: true,
    },
  },
  async run() {
    // See the Nodemailer docs for all options:
    // https://nodemailer.com/usage/
    var transporter = nodemailer.createTransport({
      host: this.host,
      port: this.port,
      secure: this.secure,
      ignoreTLS: this.ignoreTLS,
      requireTLS: this.requireTLS,
      auth: {
        user: this.user,
        pass: this.pass,
      },
    });

    var mailOptions = {
      from: this.from,
      to: this.to,
      cc: this.cc,
      subject: this.subject,
      text: (this.text || ""),
      html: (this.html || ""),
    };

    var mail = await transporter.sendMail(mailOptions);
    console.log("Email sent: " + mail.messageId);
    return mail;
  },
};

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
Helper Functions	`helper_functions`	`app`	This component uses the Helper Functions app.
host	`host`	`string`	The hostname or IP address of your SMTP server
port	`port`	`string`	The port your SMTP server listens on (defaults to 587 if is secure is false or 465 if true)
secure	`secure`	`boolean`	If `true` the connection will use TLS when connecting to server. If `false` (the default) then TLS is used if server supports the STARTTLS extension. In most cases set this value to `true` if you are connecting to port 465. For port 587 or 25 keep it `false`
Ignore TLS	`ignoreTLS`	`boolean`	If this is `true` and secure is `false` then TLS is not used even if the server supports STARTTLS extension
Require TLS	`requireTLS`	`boolean`	If this is `true` and secure is `false` then Nodemailer tries to use STARTTLS even if the server does not advertise support for it. If the connection can not be encrypted then message is not sent
user	`user`	`string`	The username you use to connect to your SMTP server
pass	`pass`	`string`	Your password
from	`from`	`string`	The email address of the sender. All email addresses can be plain 'sender@server.com' or formatted '"Sender Name" sender@server.com'
to	`to`	`string`	Comma separated list or an array of recipients email addresses that will appear on the To: field
cc	`cc`	`string`	Comma separated list or an array of recipients email addresses that will appear on the Cc: field
subject	`subject`	`string`	The subject of the email
text	`text`	`string`	The plain text version of the message
html	`html`	`string`	The HTML version of the message