Verify List of Email Address with Verifalia API on New Submission from Typeform API

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

Trigger workflow on

New Submission from the Typeform API

Next, do this

Verify List of Email Address with the Verifalia 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 Verifalia 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 Verify List of Email Address action
1. Connect your Verifalia account
2. Configure Email Addresses
3. Optional- Select a Quality Level
4. Optional- Configure Data Retention Period
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#

Verify List of Email Address on Verifalia

Description:Verify a list of email address and check if it is properly formatted, really exists and can accept mails, flagging spam traps, disposable emails and much more. [See the docs](https://verifalia.com/developers#email-validations-creating) for more information

Version:0.1.0

Key:verifalia-verify-list-emails

View on GitHub

Verifalia Overview#

Verifalia's API provides robust email validation and verification services, ensuring that email addresses in your lists are accurate and deliverable. Leveraging Verifalia within Pipedream workflows can automate the process of cleaning up email lists, improve email marketing efficiency, and maintain communication channel integrity. By integrating Verifalia's capabilities, you can cut down on bounces, identify disposable email addresses, and segment lists based on quality scores.

Action Code#

import { axios } from "@pipedream/platform";
import verifalia from "../../verifalia.app.mjs";
import common from "../../common.mjs";

import {
  CancellationToken,
  OperationCanceledError,
} from "verifalia";

export default {
  name: "Verify List of Email Address",
  description: "Verify a list of email address and check if it is properly formatted, really exists and can accept mails, " +
    "flagging spam traps, disposable emails and much more. [See the docs](https://verifalia.com/developers#email-validations-creating) for more information",
  key: "verifalia-verify-list-emails",
  version: "0.1.0",
  type: "action",
  props: {
    verifalia,
    emailAddresses: {
      type: "string[]",
      label: "Email Addresses",
      description: "Enter a list of email address to verify (e.g. `batman@gmail.com`)",
      optional: false,
    },
    quality: {
      type: "string",
      label: "Quality Level",
      description: "The higher the quality level the longer it could take to complete the verification; by default, we use the configured default quality level for your Verifalia user.",
      optional: true,
      options: common.qualityLevelOptions,
    },
    retention: {
      type: "string",
      label: "Data Retention Period",
      description: "The data retention period to observe for the validation job, expressed in the format `dd.hh:mm:ss` " +
        "(where dd: days, hh: hours, mm: minutes, ss: seconds); the initial `dd.` part is added only for periods of " +
        "more than 24 hours. The value has a minimum of 5 minutes (`0:5:0`) and a maximum of 30 days (`30.0:0:0`): " +
        "Verifalia will delete the job and its data once its data retention period is over, starting to count when " +
        "it gets completed.",
      optional: true,
    },
  },

  async run({ $ }) {
    const { run } = $.context;
    const verifaliaClient = this.verifalia.buildVerifaliaRestClient();

    // This component takes advantage of the new Pipedream's flow suspension: we handle
    // the first run vs. callback scenarios hereafter.

    if (run.runs === 1) {
      // Check the format of the data retention period and report a user-friendly error

      if (this.retention && !this.verifalia.isValidTimeSpan(this.retention)) {
        throw new Error(`The specified data retention period '${this.retention}' is incorrect: must be in the ` +
          "format dd.hh:mm:ss (where dd: days, hh: hours, mm: minutes, ss: seconds).");
      }

      // HACK: Pausing a workflow is not supported in test mode, as the editor would just
      // output the message "Would have paused until...". To overcome this, we are *not*
      // suspending runs in test mode and, in that case, proceed with a standard polling
      // to the API, backed by the usual Promise support. If the execution time approaches
      // the one we are allowed by Pipedream, we just let the user know.

      let resumeUrl = null;
      let waitForResults = false;
      let cancellationToken = null;

      if ($.context.test) {
        // In test mode, we will wait for the verification results during this execution
        // and cancel the token after 20s (the actual lowest limit is 30s).
        // See: https://pipedream.com/docs/limits/#time-per-execution

        waitForResults = true;
        cancellationToken = new CancellationToken();
        setTimeout(() => cancellationToken.cancel(), 20 * 1000);
      } else {
        // In deployment mode, we won't wait for the verification results during this
        // execution and, instead, rely on the Verifalia completion callback support and
        // on the Pipedream's new ability to suspend execution flows.

        resumeUrl = $.flow.rerun(86400 * 1000, {}, 1).resume_url;
      }

      // Submit the verification to Verifalia

      let job;

      try {
        const parsedEmails = !Array.isArray(this.emailAddresses)
          ? JSON.parse(this.emailAddresses)
          : this.emailAddresses;

        const formattedEmails = parsedEmails.map((emailAddress) => ({
          inputData: emailAddress,
        }));

        job = await this.verifalia.wrapVerifaliaApiInvocation(async () => {
          return await verifaliaClient
            .emailValidations
            .submit({
              quality: this.quality,
              entries: formattedEmails,
              retention: this.retention,
              callback: {
                url: resumeUrl,
              },
            },
            waitForResults,
            cancellationToken);
        });
      } catch (error) {
        // If the error is an OperationCanceledError it means that we are in test mode and
        // have manually cancelled the submission: just let the user know why that happened.

        if (error instanceof OperationCanceledError) {
          // Had to replace the word req*ire with a synonym because of https://github.com/PipedreamHQ/pipedream/issues/3187 :)

          throw new Error("This operation would need some more time to complete and that would not work properly in " +
            "Pipedream's test mode. Please deploy your workflow to get a meaningful email verification result.");
        }

        throw error;
      }

      // Handle the verification outcome, if available

      if (job.overview.status === "Completed") {
        if (!resumeUrl) {
          // We are in test mode and the validation just completed in a single request

          return job;
        }

        // TODO: If the validation completed, abort the suspension and return the results
        // Blocked by https://github.com/PipedreamHQ/pipedream/issues/3151

        // We are *not* in test mode and the job is complete: simulate an instantaneous
        // webhook completion callback, as the external one may take a few seconds to
        // fire and we wish to continue the flow as fast as possible.

        return axios($, {
          method: "POST",
          url: resumeUrl,
          data: {
            event: {
              type: "email-validation.completed",
              data: {
                id: job.overview.id,
              },
            },
          },
          returnFullResponse: true,
        });
      }

      // If we are here, the validation is not yet completed and the flow is going to
      // be suspended by Pipedream.
    } else {
      const callbackRequest = run.callback_request;

      // We are only interested in a specific callback type

      if (callbackRequest.body.event.type === "email-validation.completed") {
        // Retrieve and return the job

        const jobId = callbackRequest.body.event.data.id;

        return await this.verifalia.wrapVerifaliaApiInvocation(() => verifaliaClient
          .emailValidations
          .get(jobId));
      }

      // We have just received a callback we weren't waiting for :/

      console.log(callbackRequest);
      throw new Error("An error occurred while processing your request, sorry.");
    }
  },
};

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
Verifalia	`verifalia`	`app`	This component uses the Verifalia app.
Email Addresses	`emailAddresses`	`string[]`	Enter a list of email address to verify (e.g. `batman@gmail.com`)
Quality Level	`quality`	`string`	Select a value from the drop down menu:`{ "label": "Standard quality", "value": "standard" }{ "label": "High quality", "value": "high" }{ "label": "Extreme quality", "value": "extreme" }`
Data Retention Period	`retention`	`string`	The data retention period to observe for the validation job, expressed in the format `dd.hh:mm:ss` (where dd: days, hh: hours, mm: minutes, ss: seconds); the initial `dd.` part is added only for periods of more than 24 hours. The value has a minimum of 5 minutes (`0:5:0`) and a maximum of 30 days (`30.0:0:0`): Verifalia will delete the job and its data once its data retention period is over, starting to count when it gets completed.

Action Authentication#

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

In order to connect Verifalia with Pipedream, enter your Verifalia username and password below.

To learn more about how Verifalia handles authentication, see their documentation.
Make sure to use a strong and unique password for Verifalia.

About Verifalia#

Verifalia is a fast and accurate email verification service which identifies deliverable, invalid, or otherwise risky email addresses in real-time: it stops bad and low-quality emails getting into your systems, reduces bounce rates and keeps your campaigns deliverable.