actions/send-email-multiple-recipients/send-email-multiple-recipients.mjs
import { ConfigurationError, getFileStream, } from "@pipedream/platform"; import mime from "mime"; import validate from "validate.js"; import common from "../common/common.mjs"; export default { ...common, key: "sendgrid-send-email-multiple-recipients", name: "Send Email Multiple Recipients", description: "This action sends a personalized e-mail to multiple specified recipients. [See the docs here](https://docs.sendgrid.com/api-reference/mail-send/mail-send)", version: "0.1.2", annotations: { destructiveHint: false, openWorldHint: true, readOnlyHint: false, }, type: "action", props: { ...common.props, personalizations: { type: "string", label: "Personalizations", description: "An array of messages and their metadata. Each object within personalizations can be thought of as an envelope - it defines who should receive an individual message and how that message should be handled. See our [Personalizations documentation](https://sendgrid.com/docs/for-developers/sending-email/personalizations/) for details. maxItems: 1000. Example: `[{to:[{email:\"email@email.com\",name:\"Example\"}],subject:\"Mail Personalization Sample\"}]`", optional: true, }, toEmails: { type: "string[]", label: "Recipient Emails", description: "The intended recipients' email addresses. Will be ignored if `personalizations` prop is used.", optional: true, }, fromEmail: { propDefinition: [ common.props.sendgrid, "fromEmail", ], }, fromName: { propDefinition: [ common.props.sendgrid, "fromName", ], }, dynamicTemplateData: { type: "object", label: "Dynamic Template Data", description: "Dynamic template data is available using Handlebars syntax in Dynamic Transactional Templates. This field should be used in combination with a Dynamic Transactional Template, which can be identified by a template_id starting with d-. This field is a collection of key/value pairs following the pattern `\"variable_name\":\"value to insert\"`", optional: true, }, templateId: { propDefinition: [ common.props.sendgrid, "templateId", ], optional: true, }, replyToEmail: { propDefinition: [ common.props.sendgrid, "replyToEmail", ], }, replyToName: { propDefinition: [ common.props.sendgrid, "replyToName", ], }, subject: { propDefinition: [ common.props.sendgrid, "subject", ], description: "The global or `message level` subject of your email. This may be overridden by subject lines set -in personalizations.", }, content: { propDefinition: [ common.props.sendgrid, "content", ], optional: true, }, headers: { propDefinition: [ common.props.sendgrid, "headers", ], }, categories: { propDefinition: [ common.props.sendgrid, "categories", ], }, customArgs: { propDefinition: [ common.props.sendgrid, "customArgs", ], }, sendAt: { propDefinition: [ common.props.sendgrid, "sendAt", ], }, asm: { propDefinition: [ common.props.sendgrid, "asm", ], }, asmGroupId: { propDefinition: [ common.props.sendgrid, "asmGroupId", ], }, asmGroupsToDisplay: { propDefinition: [ common.props.sendgrid, "asmGroupsToDisplay", ], }, ipPoolName: { propDefinition: [ common.props.sendgrid, "ipPoolName", ], }, mailSettings: { propDefinition: [ common.props.sendgrid, "mailSettings", ], }, trackingSettings: { propDefinition: [ common.props.sendgrid, "trackingSettings", ], }, numberOfAttachments: { propDefinition: [ common.props.sendgrid, "numberOfAttachments", ], optional: true, }, syncDir: { type: "dir", accessMode: "read", sync: true, optional: true, }, }, async additionalProps() { const props = {}; if (this.numberOfAttachments) { for (let i = 1; i <= this.numberOfAttachments; i++) { props[`attachmentsName${i}`] = { type: "string", label: `Attachment File Name ${i}`, description: "The name of the file.", optional: true, }; props[`attachmentsPath${i}`] = { type: "string", label: `Attachment File Path or URL ${i}`, description: "The file to upload. Provide either a file URL or a path to a file in the `/tmp` directory (for example, `/tmp/myFile.txt`).", optional: true, }; } } return props; }, async run({ $ }) { if (!this.personalizations && !this.toEmails) { throw new ConfigurationError("Please input either Personalization or Recipient Emails."); } const personalizations = this.personalizations || []; if (personalizations.length == 0) { if (this.convertEmptyStringToUndefined(this.toEmails)) { for (const toEmail of this.toEmails) { const personalization = { to: [ { email: toEmail, }, ], }; personalizations.push(personalization); } } } if (this.dynamicTemplateData) { for (const personalization of personalizations) { personalization.dynamic_template_data = this.dynamicTemplateData; } } validate.validators.arrayValidator = this.validateArray; validate.validators.asmValidator = this.validateAsm; const constraints = { personalizations: { type: "array", }, fromEmail: { email: true, }, }; if (this.replyToEmail) { constraints.replyToEmail = { email: true, }; } const attachments = []; for (let i = 1; i <= this.numberOfAttachments; i++) { const filepath = this["attachmentsPath" + i]; const stream = await getFileStream(filepath); const chunks = []; for await (const chunk of stream) { chunks.push(chunk); } const content = Buffer.concat(chunks).toString("base64"); const type = mime.getType(filepath); attachments.push({ content, type, filename: this[`attachmentsName${i}`], }); } if (this.categories) { constraints.categories = { type: "array", }; } this.sendAt = this.convertEmptyStringToUndefined(Date.parse(this.sendAt)); if (this.sendAt) { constraints.sendAt = this.getIntegerGtZeroConstraint(); } if (this.asm || this.asmGroupsToDisplay) { constraints.asm = { asmValidator: { asm: this.asm, asmGroupId: this.asmGroupId, asmGroupsToDisplay: this.asmGroupsToDisplay, }, }; } const validationResult = validate( { personalizations: this.personalizations, fromEmail: this.fromEmail, replyToEmail: this.replyToEmail, subject: this.subject, attachments: this.attachments, categories: this.categories, sendAt: this.sendAt, }, constraints, ); this.checkValidationResults(validationResult); const from = { email: this.fromEmail, }; if (this.fromName) { from.name = this.fromName; } let replyTo = undefined; if (this.replyToEmail) { replyTo = { email: this.replyToEmail, }; if (this.replyToName) { replyTo.name = this.replyToName; } } const config = this.omitEmptyStringValues({ personalizations: this.getArrayObject(personalizations), from, reply_to: replyTo, subject: this.subject, content: this.content && [ { type: "text/html", value: this.content, }, ], attachments, headers: this.headers, categories: this.categories, custom_args: this.customArgs, send_at: this.sendAt, asm: this.getAsmConfig(), ip_pool_name: this.ipPoolName, mail_settings: this.mailSettings, tracking_settings: this.trackingSettings, template_id: this.templateId, }); const resp = await this.sendgrid.sendEmail(config); $.export("$summary", "Email successfully sent"); return resp; }, };
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.