Send Email Multiple Recipients with Twilio SendGrid API on New Submission from Typeform API

Pipedream makes it easy to connect APIs for Twilio SendGrid, Typeform and 2,500+ other apps remarkably fast.

Trigger workflow on

New Submission from the Typeform API

Next, do this

Send Email Multiple Recipients with the Twilio SendGrid 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 Typeform trigger and Twilio SendGrid action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Submission trigger
1. Connect your Typeform account
2. Select a Form
Configure the Send Email Multiple Recipients action
1. Connect your Twilio SendGrid account
2. Optional- Configure Personalizations
3. Optional- Configure Recipient Emails
4. Select a From Email
5. Optional- Configure From Name
6. Optional- Configure Dynamic Template Data
7. Optional- Select a Template ID
8. Optional- Configure Reply To Email
9. Optional- Configure Reply To Name
10. Configure Subject
11. Optional- Configure Content
12. Optional- Configure Headers
13. Optional- Configure Categories
14. Optional- Configure Custom Args
15. Optional- Configure Send At
16. Optional- Configure ASM
17. Optional- Select a ASM Group ID
18. Optional- Select one or more ASM Groups to Display
19. Optional- Configure IP Pool Name
20. Optional- Configure Mail Settings
21. Optional- Configure Tracking Settings
22. Optional- Configure Number Of Attachments
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 Submission on Typeform

Description:Emit new submission

Version:0.0.8

Key:typeform-new-submission

View on GitHub

Typeform Overview#

The Typeform API furnishes you with the means to create dynamic forms and collect user responses in real-time. By leveraging this API within Pipedream's serverless platform, you can automate workflows to process this data, integrate seamlessly with other services, and react to form submissions instantaneously. This empowers you to craft tailored responses, synchronize with databases, trigger email campaigns, or even manage event registrations without manual intervention.

Trigger Code#

import { createHmac } from "crypto";
import sampleEmit from "./test-event.mjs";
import { uuid } from "uuidv4";
import common from "../common/common.mjs";
import constants from "../../constants.mjs";
import utils from "../common/utils.mjs";

const { typeform } = common.props;
const { parseIsoDate } = utils;

export default {
  ...common,
  key: "typeform-new-submission",
  name: "New Submission",
  version: "0.0.8",
  type: "source",
  description: "Emit new submission",
  props: {
    ...common.props,
    http: {
      type: "$.interface.http",
      customResponse: true,
    },
    db: "$.service.db",
    formId: {
      propDefinition: [
        typeform,
        "formId",
      ],
    },
  },
  methods: {
    ...common.methods,
    generateSecret() {
      return "" + Math.random();
    },
  },
  hooks: {
    ...common.hooks,
    async activate() {
      const secret = this.generateSecret();
      this._setSecret(secret);

      let tag = this._getTag();
      if (!tag) {
        tag = uuid();
        this._setTag(tag);
      }

      return await this.typeform.createHook({
        endpoint: this.http.endpoint,
        formId: this.formId,
        tag,
        secret,
      });
    },
    async deactivate() {
      const tag = this._getTag();

      return await this.typeform.deleteHook({
        formId: this.formId,
        tag,
      });
    },
  },
  async run(event) {
    const {
      body,
      headers,
    } = event;

    const { [constants.TYPEFORM_SIGNATURE]: typeformSignature } = headers;

    if (typeformSignature) {
      const secret = this._getSecret();

      const hmac =
        createHmac(constants.ALGORITHM, secret)
          .update(body)
          .digest(constants.ENCODING);

      const signature = `${constants.ALGORITHM}=${hmac}`;

      if (typeformSignature !== signature) {
        throw new Error("signature mismatch");
      }
    }

    let formResponseString = "";
    const data = Object.assign({}, body.form_response);
    data.form_response_parsed = {};

    for (let i = 0; i < body.form_response.answers.length; i++) {
      const field = body.form_response.definition.fields[i];
      const answer = body.form_response.answers[i];

      let parsedAnswer;
      let value = answer[answer.type];

      if (value.label) {
        parsedAnswer = value.label;

      } else if (value.labels) {
        parsedAnswer = value.labels.join();

      } else if (value.choice) {
        parsedAnswer = value.choice;

      } else if (value.choices) {
        parsedAnswer = value.choices.join();

      } else {
        parsedAnswer = value;
      }

      data.form_response_parsed[field.title] = parsedAnswer;
      formResponseString += `### ${field.title}\n${parsedAnswer}\n`;
    }

    data.form_response_string = formResponseString;
    data.raw_webhook_event = body;

    if (data.landed_at) {
      data.landed_at = parseIsoDate(data.landed_at);
    }

    if (data.submitted_at) {
      data.submitted_at = parseIsoDate(data.submitted_at);
    }

    data.form_title = body.form_response.definition.title;
    delete data.answers;
    delete data.definition;

    this.$emit(data, {
      summary: JSON.stringify(data),
      id: data.token,
    });

    this.http.respond({
      status: 200,
    });
  },
  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
Typeform	`typeform`	`app`	This component uses the Typeform app.
N/A	`http`	`$.interface.http`	This 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.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Form	`formId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

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

offlineaccounts:readforms:writeforms:readimages:writeimages:readthemes:writethemes:readresponses:readresponses:writewebhooks:readwebhooks:writeworkspaces:readworkspaces:write

About Typeform#

Typeform lets you build no-code forms, quizzes, and surveys - and get more responses.

Action#

Send Email Multiple Recipients on Twilio SendGrid

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.0.6

Key:sendgrid-send-email-multiple-recipients

View on GitHub

Twilio SendGrid Overview#

The Twilio SendGrid API opens up a world of possibilities for email automation, enabling you to send emails efficiently and track their performance. With this API, you can programmatically create and send personalized email campaigns, manage contacts, and parse inbound emails for data extraction. When you harness the power of Pipedream, you can connect SendGrid to hundreds of other apps to automate workflows, such as triggering email notifications based on specific actions, syncing email stats with your analytics, or handling incoming emails to create tasks or tickets.

Action Code#

import { ConfigurationError } from "@pipedream/platform";
import fs from "fs";
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.0.6",
  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,
    },
  },
  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 ${i}`,
          description: "The path to your file in /tmp dir. [See the documentation](https://pipedream.com/docs/code/nodejs/working-with-files/#writing-a-file-to-tmp) for how to work with tmp dir.",
          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;
      }
    }
    //Performs validation on parameters.
    validate.validators.arrayValidator = this.validateArray; //custom validator for object arrays
    validate.validators.asmValidator = this.validateAsm; //custom validator for asm object
    //Defines contraints for required parameters
    const constraints = {
      personalizations: {
        type: "array",
      },
      fromEmail: {
        email: true,
      },
    };
    //Defines contraints for optional parameters
    if (this.replyToEmail) {
      constraints.replyToEmail = {
        email: true,
      };
    }
    const attachments = [];
    for (let i = 1; i <= this.numberOfAttachments; i++) {
      const filepath = this.checkTmp(this["attachmentsPath" + i]);
      const content = fs.readFileSync(filepath, {
        encoding: "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,
        },
      };
    }
    //Executes validation
    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);
    //Set ups the `from` object, where `email`, `name` of the mail sender are specified, with
    //`email` being required.
    const from = {
      email: this.fromEmail,
    };
    if (this.fromName) {
      from.name = this.fromName;
    }
    //Set ups the `reply_to` object, where `email`, `name` of the reply-to recipient are
    //specified, with `email` being required.
    let replyTo = undefined;
    if (this.replyToEmail) {
      replyTo = {
        email: this.replyToEmail,
      };
      if (this.replyToName) {
        replyTo.name = this.replyToName;
      }
    }

    //Prepares and sends the request configuration
    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;
  },
};

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
Twilio SendGrid	`sendgrid`	`app`	This component uses the Twilio SendGrid app.
Personalizations	`personalizations`	`string`	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 for details. maxItems: 1000. Example: `[{to:[{email:"email@email.com",name:"Example"}],subject:"Mail Personalization Sample"}]`
Recipient Emails	`toEmails`	`string[]`	The intended recipients' email addresses. Will be ignored if `personalizations` prop is used.
From Email	`fromEmail`	`string`	Select a value from the drop down menu.
From Name	`fromName`	`string`	A name or title associated with the sending email address
Dynamic Template Data	`dynamicTemplateData`	`object`	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"`
Template ID	`templateId`	`string`	Select a value from the drop down menu.
Reply To Email	`replyToEmail`	`string`	The email address where any replies or bounces will be returned
Reply To Name	`replyToName`	`string`	A name or title associated with the `replyToEmail` address
Subject	`subject`	`string`	The global or `message level` subject of your email. This may be overridden by subject lines set -in personalizations.
Content	`content`	`string`	Content of the email in `text/html`
Headers	`headers`	`object`	An object containing key/value pairs of header names and the value to substitute for them. The key/value pairs must be strings. You must ensure these are properly encoded if they contain unicode characters. These headers cannot be one of the reserved headers.
Categories	`categories`	`string[]`	A string array of category names for this message. Each category name may not exceed 255 characters. Example: `["category1","category2"]`
Custom Args	`customArgs`	`string`	Values that are specific to the entire send that will be carried along with the email and its activity data. Key/value pairs must be strings. Substitutions will not be made on custom arguments, so any string that is entered into this parameter will be assumed to be the custom argument that you would like to be used. This parameter is overridden by `custom_args` set at the personalizations level. Total `custom_args` size may not exceed 10,000 bytes.
Send At	`sendAt`	`integer`	An ISO 8601 formatted date-time (YYYY-MM-DDTHH:MM:SSZ) allowing you to specify when you want your email to be delivered. This may be overridden by the `send_at` parameter set at the personalizations level. Delivery cannot be scheduled more than 72 hours in advance. If you have the flexibility, it's better to schedule mail for off-peak times. Most emails are scheduled and sent at the top of the hour or half hour. Scheduling email to avoid peak times — for example, scheduling at 10:53 — can result in lower deferral rates due to the reduced traffic during off-peak times.
ASM	`asm`	`object`	Advanced Suppression Manager. An object allowing you to specify how to handle unsubscribes
ASM Group ID	`asmGroupId`	`integer`	Select a value from the drop down menu.
ASM Groups to Display	`asmGroupsToDisplay`	`integer[]`	Select a value from the drop down menu.
IP Pool Name	`ipPoolName`	`string`	The IP Pool that you would like to send this email from
Mail Settings	`mailSettings`	`object`	A collection of different mail settings that you can use to specify how you would like this email to be handled
Tracking Settings	`trackingSettings`	`object`	Settings to determine how you would like to track the metrics of how your recipients interact with your email
Number Of Attachments	`numberOfAttachments`	`integer`	The number of attachments to be sent with the email.