Verify List of Email Address with Verifalia API on New Message In Channels (Instant) from Slack API

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

Trigger workflow on

New Message In Channels (Instant) from the Slack API

Next, do this

Verify List of Email Address with the Verifalia 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 Slack 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 Message In Channels (Instant) trigger
1. Connect your Slack account
2. Optional- Select one or more Channels
3. Configure slackApphook
4. Optional- Configure Resolve Names
5. Optional- Configure Ignore Bots
6. Optional- Configure Ignore replies in threads
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 Message In Channels (Instant) on Slack

Description:Emit new event when a new message is posted to one or more channels

Version:1.0.14

Key:slack-new-message-in-channels

View on GitHub

Slack Overview#

The Pipedream Slack app enables you to build event-driven workflows that interact with the Slack API. When you authorize the Pipedream app's access to your workspace, you can use Pipedream workflows to perform common Slack actions, or write your own code against the Slack API.

The Pipedream Slack app is not a typical app. You don't interact with it directly as a bot, and it doesn't add custom functionality to your workspace out of the box. It makes it easier to automate anything you'd typically use the Slack API for, using Pipedream workflows.

Automate posting updates to your team channels
Create a bot to answer common questions
Integrate with your existing tools and services
And much more!

Trigger Code#

import common from "../common/base.mjs";
import sampleEmit from "./test-event.mjs";
import constants from "../common/constants.mjs";

export default {
  ...common,
  key: "slack-new-message-in-channels",
  name: "New Message In Channels (Instant)",
  version: "1.0.14",
  description: "Emit new event when a new message is posted to one or more channels",
  type: "source",
  dedupe: "unique",
  props: {
    ...common.props,
    conversations: {
      propDefinition: [
        common.props.slack,
        "conversation",
      ],
      type: "string[]",
      label: "Channels",
      description: "Select one or more channels to monitor for new messages.",
      optional: true,
    },
    // eslint-disable-next-line pipedream/props-description,pipedream/props-label
    slackApphook: {
      type: "$.interface.apphook",
      appProp: "slack",
      async eventNames() {
        return this.conversations || [
          "message",
        ];
      },
    },
    resolveNames: {
      propDefinition: [
        common.props.slack,
        "resolveNames",
      ],
    },
    ignoreBot: {
      propDefinition: [
        common.props.slack,
        "ignoreBot",
      ],
    },
    ignoreThreads: {
      type: "boolean",
      label: "Ignore replies in threads",
      description: "Ignore replies to messages in threads",
      optional: true,
    },
  },
  methods: {
    ...common.methods,
    getSummary() {
      return "New message in channel";
    },
    async processEvent(event) {
      if (event.type !== "message") {
        console.log(`Ignoring event with unexpected type "${event.type}"`);
        return;
      }
      if (event.subtype && !constants.ALLOWED_MESSAGE_IN_CHANNEL_SUBTYPES.includes(event.subtype)) {
        // This source is designed to just emit an event for each new message received.
        // Due to inconsistencies with the shape of message_changed and message_deleted
        // events, we are ignoring them for now. If you want to handle these types of
        // events, feel free to change this code!!
        console.log("Ignoring message with subtype.");
        return;
      }
      if ((this.ignoreBot) && (event.subtype == "bot_message" || event.bot_id)) {
        return;
      }
      console.log(event.s);
      // There is no thread message type only the thread_ts field
      // indicates if the message is part of a thread in the event.
      if (this.ignoreThreads && event.thread_ts) {
        console.log("Ignoring reply in thread");
        return;
      }
      if (this.resolveNames) {
        if (event.user) {
          event.user_id = event.user;
          event.user = await this.getUserName(event.user);
        } else if (event.bot_id) {
          event.bot = await this.getBotName(event.bot_id);
        }
        event.channel_id = event.channel;
        event.channel = await this.getConversationName(event.channel);
        if (event.team) {
          event.team_id = event.team;
          event.team = await this.getTeamName(event.team);
        }
      }
      return event;
    },
  },
  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
Slack	`slack`	`app`	This component uses the Slack app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Channels	`conversations`	`string[]`	Select a value from the drop down menu.
	`slackApphook`	`$.interface.apphook`
Resolve Names	`resolveNames`	`boolean`	Instead of returning `channel`, `team`, and `user` as IDs, return their human-readable names.
Ignore Bots	`ignoreBot`	`boolean`	Ignore messages from bots
Ignore replies in threads	`ignoreThreads`	`boolean`	Ignore replies to messages in threads

Trigger Authentication#

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

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

bookmarks:writecalls:readcalls:writechannels:historychannels:readchannels:writednd:readdnd:writeemoji:readfiles:readgroups:historygroups:readgroups:writeim:historyim:readim:writelinks:readlinks:writempim:historympim:readmpim:writepins:readpins:writereactions:readreactions:writereminders:readreminders:writeremote_files:readremote_files:sharestars:readstars:writeteam:readusergroups:readusergroups:writeusers:readusers:read.emailusers:writechat:write:botchat:write:usercommandsfiles:write:userusers.profile:writeusers.profile:readsearch:read

About Slack#

Slack is a channel-based messaging platform. With Slack, people can work together more effectively, connect all their software tools and services, and find the information they need to do their best work — all within a secure, enterprise-grade environment.

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.

More Ways to Connect Verifalia + Slack#

Other Popular Integrations#

Verify Email Address with Verifalia API on New Direct Message (Instant) from Slack API

Slack + Verifalia

Verify List of Email Address with Verifalia API on New Message In Channels (Instant) from Slack API

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

Trusted by 800,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

1-24of2,000+apps by most popular

1
-
24
of
2,000+
apps by most popular