Validate Email with Abstract - Email Verification API API on New Webhook Event (Instant) from Supabase API

Pipedream makes it easy to connect APIs for Abstract - Email Verification API, Supabase and 2,000+ other apps remarkably fast.

Trigger workflow on

New Webhook Event (Instant) from the Supabase API

Next, do this

Validate Email with the Abstract - Email Verification API API

No credit card required

▶

Watch us build a workflow

8 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 Supabase trigger and Abstract - Email Verification API action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Webhook Event (Instant) trigger
1. Connect your Supabase account
2. Configure Table
3. Optional- Configure Row Identifier
Configure the Validate Email action
1. Connect your Abstract - Email Verification API account
2. Configure Email Address
3. Optional- Configure Auto Correct
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 Webhook Event (Instant) on Supabase

Description:Emit new event for every `insert`, `update`, or `delete` operation in a table. This source requires user configuration using the Supabase website. More information in the README. [Also see documentation here](https://supabase.com/docs/guides/database/webhooks#creating-a-webhook)

Version:0.0.2

Key:supabase-new-webhook-event

View on GitHub

Supabase Overview#

Supabase is a real-time backend-as-a-service that provides developers with a suite of tools to quickly build and scale their applications. It offers database storage, authentication, instant APIs, and real-time subscriptions. With the Supabase API, you can perform CRUD operations on your database, manage users, and listen to database changes in real time. When integrated with Pipedream, you can automate workflows that react to these database events, synchronize data across multiple services, or streamline user management processes.

Trigger Code#

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

export default {
  key: "supabase-new-webhook-event",
  name: "New Webhook Event (Instant)",
  description: "Emit new event for every `insert`, `update`, or `delete` operation in a table. This source requires user configuration using the Supabase website. More information in the README. [Also see documentation here](https://supabase.com/docs/guides/database/webhooks#creating-a-webhook)",
  version: "0.0.2",
  type: "source",
  props: {
    ...base.props,
    http: {
      type: "$.interface.http",
    },
  },
  hooks: {
    async deploy() {
      const client = await this.supabase._client();
      const query = client
        .from(this.table)
        .select()
        .range(0, constants.HISTORICAL_EVENT_LIMIT);
      const { data } = await query;
      for (const row of data) {
        this.$emit({
          record: row,
        }, {
          summary: "Historical row in table",
        });
      }
    },
  },
  async run(event) {
    const { body: data } = event;
    let summary = `New ${data.type} event in table`;
    if (data.record?.[this.rowIdentifier]) {
      summary = `${summary}: ${data.record[this.rowIdentifier]}`;
    }
    this.$emit(data, {
      summary,
    });
  },
};

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
Supabase	`supabase`	`app`	This component uses the Supabase app.
Table	`table`	`string`	The name of the table to watch for new rows
Row Identifier	`rowIdentifier`	`string`	The column name to use as the row identifier
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.

Trigger Authentication#

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

Supabase provides a Service Key to get started. You can find the service_role in the API Settings page.

Finding the Supabase subdomain

About Supabase#

Supabase is an open source Firebase alternative.

Action#

Validate Email on Abstract - Email Verification API

Description:Check the deliverability of a specified email address. [See the documentation](https://docs.abstractapi.com/email-validation)

Version:0.0.1

Key:abstract-validate-email

View on GitHub

Abstract - Email Verification API Overview#

The Abstract - Email Verification API allows you to verify the validity and quality of an email address. With this API, you can confirm if an email exists, is formatted correctly, and is not a temporary or disposable address. Integrating this API with Pipedream workflows offers numerous possibilities, such as filtering out fake email addresses from sign-up processes, maintaining email list hygiene, or automating customer outreach by ensuring that communications only go to verified emails.

Action Code#

import abstract from "../../abstract.app.mjs";

export default {
  key: "abstract-validate-email",
  name: "Validate Email",
  description: "Check the deliverability of a specified email address. [See the documentation](https://docs.abstractapi.com/email-validation)",
  version: "0.0.1",
  type: "action",
  props: {
    abstract,
    emailAddress: {
      propDefinition: [
        abstract,
        "emailAddress",
      ],
    },
    autoCorrect: {
      propDefinition: [
        abstract,
        "autoCorrect",
      ],
    },
  },
  async run({ $ }) {
    const response = await this.abstract.checkEmailDeliverability({
      $,
      params: {
        email: this.emailAddress,
        auto_correct: this.autoCorrect,
      },
    });

    $.export("$summary", `Checked email ${this.emailAddress} (${response.deliverability})`);
    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
Abstract - Email Verification API	`abstract`	`app`	This component uses the Abstract - Email Verification API app.
Email Address	`emailAddress`	`string`	The email address to validate.
Auto Correct	`autoCorrect`	`boolean`	You can choose to disable auto correct. By default, it is turned on.

Action Authentication#

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

Sign in your Abstract Dashboard. Abstract requires a unique API key per API. Please enter your email validation api key below.

About Abstract - Email Verification API#

Do more, build better, ship faster with Abstract APIs.

More Ways to Connect Abstract - Email Verification API + Supabase#

Other Popular Integrations#

Validate Email with Abstract - Email Verification API API on New Row Added from Supabase API

Supabase + Abstract - Email Verification API

Try it

Popular Triggers#

New Row Added from the Supabase API

Emit new event for every new row added in a table. See documentation here

Try it

New Webhook Event (Instant) from the Supabase API

Emit new event for every insert, update, or delete operation in a table. This source requires user configuration using the Supabase website. More information in the README. Also see documentation here

Try it