Verify Email Address with Verifalia API on New Collection from MongoDB API

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

Trigger workflow on

New Collection from the MongoDB API

Next, do this

Verify 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 MongoDB 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 Collection trigger
1. Connect your MongoDB account
2. Configure Polling Interval
3. Select a Database
Configure the Verify Email Address action
1. Connect your Verifalia account
2. Configure Email address
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 Collection on MongoDB

Description:Emit new an event when a new collection is added to a database

Version:0.0.7

Key:mongodb-new-collection

View on GitHub

MongoDB Overview#

The MongoDB API provides powerful capabilities to interact with a MongoDB database, allowing you to perform CRUD (Create, Read, Update, Delete) operations, manage databases, and execute sophisticated queries. With Pipedream, you can harness these abilities to automate tasks, sync data across various apps, and react to events in real-time. It’s a combo that’s particularly potent for managing data workflows, syncing application states, or triggering actions based on changes to your data.

Trigger Code#

import common from "../common/base.mjs";

export default {
  ...common,
  key: "mongodb-new-collection",
  name: "New Collection",
  description: "Emit new an event when a new collection is added to a database",
  version: "0.0.7",
  type: "source",
  dedupe: "unique",
  props: {
    ...common.props,
    database: {
      propDefinition: [
        common.props.mongodb,
        "database",
      ],
    },
  },
  methods: {
    ...common.methods,
    _getCollectionIds() {
      return this.db.get("collectionIds");
    },
    _setCollectionIds(collectionIds) {
      this.db.set("collectionIds", collectionIds);
    },
    isRelevant(uuid, collectionIds) {
      return !collectionIds.includes(uuid);
    },
    async processEvent(client, ts) {
      const collectionIds = this._getCollectionIds() || [];
      const collections = await this.mongodb.listCollections(client, this.database);
      for (const collection of collections) {
        const uuid = JSON.stringify(collection.info.uuid);
        if (!this.isRelevant(uuid, collectionIds)) {
          continue;
        }
        collectionIds.push(uuid);
        this.emitEvent(collection, ts);
      }
      this._setCollectionIds(collectionIds);
    },
    generateMeta({
      info, name,
    }, ts) {
      return {
        id: info.uuid,
        summary: name,
        ts,
      };
    },
  },
};

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
MongoDB	`mongodb`	`app`	This component uses the MongoDB app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Polling Interval	`timer`	`$.interface.timer`	Pipedream will poll the API on this schedule
Database	`database`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

Before you connect to your Mongo database from Pipedream, please make sure your database is accessible from the public internet. You may need to add a firewall rule allowing connections from 0.0.0.0/0.

Then, enter the details of your Mongo host / database below.

About MongoDB#

MongoDB is an open source NoSQL database management program.

Action#

Verify Email Address on Verifalia

Description:Verify an 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:1.1.0

Key:verifalia-verify-email

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 Email Address",
  description: "Verify an 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-email",
  version: "1.1.0",
  type: "action",
  props: {
    verifalia,
    emailAddress: {
      type: "string",
      label: "Email address",
      description: "Enter the 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 {
        job = await this.verifalia.wrapVerifaliaApiInvocation(async () => {
          return await verifaliaClient
            .emailValidations
            .submit({
              quality: this.quality,
              entries: [
                {
                  inputData: this.emailAddress,
                },
              ],
              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 address	`emailAddress`	`string`	Enter the 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.