actions/send-email/send-email.mjs
import { BODY_CONTENT_TYPE_OPTIONS, ENCODING_OPTIONS, } from "../../common/constants.mjs"; import { parseObject } from "../../common/utils.mjs"; import app from "../../elastic_email.app.mjs"; export default { key: "elastic_email-send-email", name: "Send Email", description: "Sends an email to one or more recipients. [See the documentation](https://elasticemail.com/developers/api-documentation/rest-api#operation/emailsPost)", version: "0.0.2", annotations: { destructiveHint: false, openWorldHint: true, readOnlyHint: false, }, type: "action", props: { app, recipients: { type: "string[]", label: "Recipients", description: "List of recipients", }, from: { type: "string", label: "From", description: "Your e-mail with an optional name (e.g.: email@domain.com)", }, bodyContentType: { type: "string", label: "Body Content Type", description: "Type of body part", options: BODY_CONTENT_TYPE_OPTIONS, optional: true, }, bodyContent: { type: "string", label: "Body Content", description: "Actual content of the body part", optional: true, }, merge: { type: "object", label: "Merge", description: "A key-value collection of custom merge fields, shared between recipients. Should be used in e-mail body like so: {firstname}, {lastname} etc.", optional: true, }, replyTo: { type: "string", label: "Reply To", description: "To what address should the recipients reply to (e.g. email@domain.com)", optional: true, }, subject: { type: "string", label: "Subject", description: "Default subject of email.", optional: true, }, templateName: { propDefinition: [ app, "templateName", ], optional: true, }, timeOffset: { type: "integer", label: "Time Offset", description: "By how long should an e-mail be delayed (in minutes). Maximum is 35 days.", optional: true, }, poolName: { type: "string", label: "Pool Name", description: "Name of your custom IP Pool to be used in the sending process", optional: true, }, channelName: { type: "string", label: "Channel Name", description: "Name of selected channel.", optional: true, }, encoding: { type: "string", label: "Encoding", description: "Encoding type for the email headers", options: ENCODING_OPTIONS, optional: true, }, trackOpens: { type: "boolean", label: "Track Opens", description: "Should the opens be tracked? If no value has been provided, Account's default setting will be used.", optional: true, }, trackClicks: { type: "boolean", label: "Track Clicks", description: "Should the clicks be tracked? If no value has been provided, Account's default setting will be used.", optional: true, }, }, async run({ $ }) { const response = await this.app.sendBulkEmails({ $, data: { Recipients: parseObject(this.recipients)?.map((item) => ({ Email: item, })), Content: { From: this.from, Body: [ { ContentType: this.bodyContentType, Body: this.bodyContent, }, ], Merge: parseObject(this.merge), ReplyTo: this.replyTo, Subject: this.subject, TemplateName: this.templateName, }, Options: { TimeOffset: this.timeOffset, PoolName: this.poolName, ChannelName: this.channelName, Encoding: this.encoding, TrackOpens: this.trackOpens, TrackClicks: this.trackClicks, }, }, }); $.export("$summary", `Emails sent successfully to ${this.recipients.join(", ")}`); return response; }, };
Chase Roberts@chsrbrts@benedictevans If you haven’t used @pipedream yet, then you haven’t lived.
✨Ellie Day✨@heyelliedayEvaluation update: @pipedream has quite literally been a dream to work with! I’m excited to leverage this tool for all the various workflows I need to write. I’m currently at 11k invocations a day from the initial workflows I’ve written in the past couple weeks.
Michael Braedley@MBraedleyUpdate: I got it working properly, and it's working so well that I'm dropping IFTTT. @pipedream can do everything that IFTTT basic can, and most (if not all things) IFTTT pro can for free or at a reasonable price if you need it. I am recommending it for basically any power user.
Thomas Cutting@mrthomascuttingWant quick+dirty integrations for a serverless workflow - @pipedream is my new go-to 😃
Matthew Roberts@mattdotrobertsday 013 - finally hit node js. This is the secret sauce of taking #nocode projects that one step further. Pumped about getting deeper into @pipedream now
Kenneth Auchenberg 💭@auchenbergYahoo Pipes is back! Kinda 😍 @pipedream
Raymond Camden 🥑@raymondcamdenAwesome video by the @pipedream folks showing real time twitter sentiment analysis integrated with Google Sheets. This is where Pipedream *really* shines, connecting systems together in easy workflows.
Nacho Caballero@nachocaballeroI couldn't recommend @pipedream more. It's an amazing service to integrate different APIs. Much more powerful than Zapier and more user-friendly than AWS Lambda. I'm very proud to wear this t-shirt #NoCode
Jason Snow@jyksnwDeveloped a working prototype environmental sensor IoT solution with @particle Photon, @pipedream, and @MongoDB with full graphing and alerting in less than a day! All amazing technology, will def. be exploring these more.
Steven Terrana@steven_terrana@burgwyn you've inspired me to finally set up my own blog. I'll make sure my first blog post explains the tech behind the setup. think @obsdmd + @GatsbyJS + @pipedream.
🚄 James Augeri, PhD@DotDotJamesWant to low-code your back end, need more horsepower than @Bubble / @KnackHQ, or just miss Yahoo! Pipes? Check out @PipeDream
Sébastien Chopin@AtinuxGitHub issues should be like @linear_app for maintainers. Looking forward more integrations with GH actions or tools like @pipedream 👀
Raul@raul_predescuIf you're a dev and not using @pipedream, you're missing out. Been using it for months, daily. FREE for devs. Plenty of integrations and good limits. Absolutely love it.
Bruno Skvorc@bitfallsSo @pipedream is pretty amazing. In 3 minutes I just made a flow which adds @rickastley's Never Gonna Give You Up to my @spotify playlist whenever a new pull request arrives in an old repo of mine.
Zach Lanich@ZachLanichUm, wow 🤯 @pipedream
Steven Bell@bellontechI just used @pipedream to build a Shopify App. Wow, they make small backed tasks easy.
Jay Hack 🎩🇺🇸@_jayhack_Very impressed with this bad boi - it reminds me of a @PalantirTech internal tool, but geared towards integrations instead of data analysis and far more customizable. Great expectations here 🚀🤩
Tree Sturgeon 🔥🚴♂️🌳@philsturgeonFor context this is day 2 of a really challenging and stupid migration from Notion to @airtable with disparate/missing data. It's going better than expected and thanks to @pipedream I don't have to bother the iOS dev to add W3W.