Create New Lead with Mailbluster API on New Submission from Typeform API

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

Trigger workflow on

New Submission from the Typeform API

Next, do this

Create New Lead with the Mailbluster 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 Typeform trigger and Mailbluster 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 Create New Lead action
1. Connect your Mailbluster account
2. Configure Email
3. Configure Subscribed
4. Optional- Configure First Name
5. Optional- Configure Last Name
6. Optional- Configure Fields
7. Optional- Configure Timezone
8. Optional- Configure IP Address
9. Optional- Configure Double Opt-In
10. Optional- Configure Tags
11. Optional- Configure Override Existing
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#

Create New Lead on Mailbluster

Description:Create a new lead. [See the documentation](https://app.mailbluster.com/api-doc/leads)

Version:0.0.2

Key:mailbluster-create-lead

View on GitHub

Mailbluster Overview#

Mailbluster is an API for managing email marketing campaigns, allowing for the creation, sending, and tracking of email newsletters. With Pipedream, you can automate workflows involving Mailbluster to send personalized emails, sync subscriber lists, and analyze campaign performance without the need to write code. By leveraging Pipedream's serverless platform, you can connect Mailbluster with various apps, set up triggers based on certain conditions, and create complex email sequences effortlessly.

Action Code#

import mailbluster from "../../app/mailbluster.app.mjs";
export default {
    key: "mailbluster-create-lead",
    name: "Create New Lead",
    description: "Create a new lead. [See the documentation](https://app.mailbluster.com/api-doc/leads)",
    type: "action",
    version: "0.0.2",
    props: {
        mailbluster,
        email: {
            type: "string",
            label: "Email",
            description: "Email address of the lead.",
        },
        subscribed: {
            type: "boolean",
            label: "Subscribed",
            description: "Lead is subscribed to receive email or not.",
        },
        firstName: {
            type: "string",
            label: "First Name",
            description: "First name of the lead.",
            optional: true,
        },
        lastName: {
            type: "string",
            label: "Last Name",
            description: "Last name of the lead.",
            optional: true,
        },
        fields: {
            type: "object",
            label: "Fields",
            description: "An object containing field information of the lead. Field merge tag is the key and field value is the value.",
            optional: true,
        },
        timezone: {
            type: "string",
            label: "Timezone",
            description: "Timezone of the lead. View supported timezones from [here](https://app.mailbluster.com/pages/timezones).",
            optional: true,
        },
        ipAddress: {
            type: "string",
            label: "IP Address",
            description: "IP address of the lead. IP address is used to find country, city, latitude, longitude, timezone (if no timezone is given) etc of this lead & store them as `meta`.",
            optional: true,
        },
        doubleOptIn: {
            type: "boolean",
            label: "Double Opt-In",
            description: "If true, the lead will receive the opt-in confirmation email.",
            optional: true,
        },
        tags: {
            type: "string[]",
            label: "Tags",
            description: "Tag(s) name of the lead. For each tag, if tag already exists, it will be only attached to the lead. Otherwise, it will be created first and then get attached.",
            optional: true,
        },
        overrideExisting: {
            type: "boolean",
            label: "Override Existing",
            description: "If lead exists, should it get overridden? Before creating a lead, we will try to find whether the lead already exists in the system using the provided email. This param controls if lead is found, we should override the lead info or throw an error message.",
            optional: true,
        },
    },
    async run({ $ }) {
        const { mailbluster, ...data } = this;
        const response = await mailbluster.createLead({
            $,
            data,
        });
        $.export("$summary", `Lead ${data.firstName} ${data.lastName} was successfully created!`);
        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
Mailbluster	`mailbluster`	`app`	This component uses the Mailbluster app.
Email	`email`	`string`	Email address of the lead.
Subscribed	`subscribed`	`boolean`	Lead is subscribed to receive email or not.
First Name	`firstName`	`string`	First name of the lead.
Last Name	`lastName`	`string`	Last name of the lead.
Fields	`fields`	`object`	An object containing field information of the lead. Field merge tag is the key and field value is the value.
Timezone	`timezone`	`string`	Timezone of the lead. View supported timezones from here.
IP Address	`ipAddress`	`string`	IP address of the lead. IP address is used to find country, city, latitude, longitude, timezone (if no timezone is given) etc of this lead & store them as `meta`.
Double Opt-In	`doubleOptIn`	`boolean`	If true, the lead will receive the opt-in confirmation email.
Tags	`tags`	`string[]`	Tag(s) name of the lead. For each tag, if tag already exists, it will be only attached to the lead. Otherwise, it will be created first and then get attached.
Override Existing	`overrideExisting`	`boolean`	If lead exists, should it get overridden? Before creating a lead, we will try to find whether the lead already exists in the system using the provided email. This param controls if lead is found, we should override the lead info or throw an error message.

Action Authentication#

Mailbluster uses API keys for authentication. When you connect your Mailbluster account, Pipedream securely stores the keys so you can easily authenticate to Mailbluster APIs in both code and no-code steps.

To retrieve your API keys,