Create Lead with Hunter API on New Row Added from Supabase API

Pipedream makes it easy to connect APIs for Hunter, Supabase and 2,900+ other apps remarkably fast.

Trigger workflow on

New Row Added from the Supabase API

Next, do this

Create Lead with the Hunter 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 Supabase trigger and Hunter action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Row Added trigger
1. Connect your Supabase account
2. Configure Table
3. Optional- Configure Row Identifier
4. Optional- Configure Column
5. Optional- Select a Filter
6. Optional- Configure Value
7. Configure Order By
8. Optional- Select a Sort Order
9. Configure timer
Configure the Create Lead action
1. Connect your Hunter account
2. Configure Email
3. Optional- Configure First Name
4. Optional- Configure Last Name
5. Optional- Configure Position
6. Optional- Configure Company
7. Optional- Select a Company Industry
8. Optional- Configure Company Size
9. Optional- Configure Confidence Score
10. Optional- Configure Website
11. Optional- Configure Country Code
12. Optional- Configure LinkedIn URL
13. Optional- Configure Phone Number
14. Optional- Configure Twitter
15. Optional- Configure Notes
16. Optional- Configure Source
17. Optional- Select a Leads List ID
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 Row Added on Supabase

Description:Emit new event for every new row added in a table. [See documentation here](https://supabase.com/docs/reference/javascript/select)

Version:0.0.5

Key:supabase-new-row-added

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 {
  DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
  ConfigurationError,
} from "@pipedream/platform";
import constants from "../../common/constants.mjs";

export default {
  key: "supabase-new-row-added",
  name: "New Row Added",
  description: "Emit new event for every new row added in a table. [See documentation here](https://supabase.com/docs/reference/javascript/select)",
  version: "0.0.5",
  type: "source",
  props: {
    ...base.props,
    column: {
      propDefinition: [
        base.props.supabase,
        "column",
      ],
      optional: true,
    },
    filter: {
      propDefinition: [
        base.props.supabase,
        "filter",
      ],
      optional: true,
    },
    value: {
      propDefinition: [
        base.props.supabase,
        "value",
      ],
      optional: true,
    },
    orderBy: {
      propDefinition: [
        base.props.supabase,
        "column",
      ],
      label: "Order By",
      description: "Column name to order by",
    },
    sortOrder: {
      propDefinition: [
        base.props.supabase,
        "sortOrder",
      ],
    },
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
  },
  methods: {
    _getOffset() {
      return this.db.get("offset") || 0;
    },
    _setOffset(offset) {
      this.db.set("offset", offset);
    },
  },
  async run() {
    const {
      table,
      column,
      filter,
      value,
      orderBy,
      sortOrder,
      rowIdentifier,
    } = this;

    if ((column || filter || value) && !(column && filter && value)) {
      throw new ConfigurationError("If `column`, `filter`, or `value` is used, all three must be entered");
    }

    const offset = this._getOffset();
    const client = await this.supabase._client();
    const query = client
      .from(table)
      .select()
      .order(orderBy, {
        ascending: sortOrder,
      })
      .range(offset, offset + constants.MAX_OFFSET);

    if (filter) {
      const filterMethod = this.supabase[filter];
      filterMethod(query, column, value);
    }

    const { data } = await query;
    this._setOffset(offset + data.length);

    for (const row of data) {
      let summary = "New row in table";
      if (row[rowIdentifier]) {
        summary = `${summary}: ${row[rowIdentifier]}`;
      }
      this.$emit(row, {
        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
Column	`column`	`string`	Column name to search by
Filter	`filter`	`string`	Select a value from the drop down menu:`{ "label": "Equal", "value": "equalTo" }{ "label": "Not Equal", "value": "notEqualTo" }{ "label": "Greater Than", "value": "greaterThan" }{ "label": "Greater Than or Equal To", "value": "greaterThanOrEqualTo" }{ "label": "Less Than", "value": "lessThan" }{ "label": "Less Than or Equal To", "value": "lessThanOrEqualTo" }{ "label": "Contains (Case Sensitive)", "value": "patternMatch" }{ "label": "Contains (Case Insensitive)", "value": "patternMatchCaseInsensitive" }`
Value	`value`	`string`	Value of the column specified to search for
Order By	`orderBy`	`string`	Column name to order by
Sort Order	`sortOrder`	`string`	Select a value from the drop down menu:`ascendingdescending`
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`

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.

About Supabase#

Supabase is an open source Firebase alternative.

Action#

Create Lead on Hunter

Description:Create a new lead in your Hunter account. [See the documentation](https://hunter.io/api-documentation/v2#create-lead).

Version:0.0.2

Key:hunter-create-lead

View on GitHub

Hunter Overview#

The Hunter API on Pipedream provides a potent suite for automating email discovery and verification processes. By interfacing with Hunter, you can programmatically find email addresses associated with a domain, verify the deliverability of emails, and retrieve other data points like the organization behind an address. This capability is invaluable for lead generation, sales outreach, and data enrichment workflows, where accurate contact information is crucial.

Action Code#

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

export default {
  key: "hunter-create-lead",
  name: "Create Lead",
  description: "Create a new lead in your Hunter account. [See the documentation](https://hunter.io/api-documentation/v2#create-lead).",
  version: "0.0.2",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: false,
  },
  type: "action",
  props: {
    app,
    email: {
      propDefinition: [
        app,
        "email",
      ],
      description: "The email address of the lead.",
    },
    firstName: {
      propDefinition: [
        app,
        "firstName",
      ],
      description: "The first name of the lead.",
      optional: true,
    },
    lastName: {
      propDefinition: [
        app,
        "lastName",
      ],
      description: "The last name of the lead.",
      optional: true,
    },
    position: {
      propDefinition: [
        app,
        "position",
      ],
      description: "The job title of the lead.",
      optional: true,
    },
    company: {
      propDefinition: [
        app,
        "company",
      ],
      description: "The name of the company the lead is working in.",
      optional: true,
    },
    companyIndustry: {
      type: "string",
      label: "Company Industry",
      description: "The sector of the company.",
      options: [
        "Animal",
        "Art & Entertainment",
        "Automotive",
        "Beauty & Fitness",
        "Books & Literature",
        "Education & Career",
        "Finance",
        "Food & Drink",
        "Game",
        "Health",
        "Hobby & Leisure",
        "Home & Garden",
        "Industry",
        "Internet & Telecom",
        "Law & Government",
        "Manufacturing",
        "News",
        "Real Estate",
        "Science",
        "Retail",
        "Sport",
        "Technology",
        "Travel",
      ],
      optional: true,
    },
    companySize: {
      propDefinition: [
        app,
        "companySize",
      ],
      description: "The size of the company the lead is working in.",
      optional: true,
    },
    confidenceScore: {
      type: "integer",
      label: "Confidence Score",
      description: "Estimation of the probability the email address returned is correct, between 0 and 100.",
      min: 0,
      max: 100,
      optional: true,
    },
    website: {
      propDefinition: [
        app,
        "website",
      ],
      description: "The domain name of the company.",
      optional: true,
    },
    countryCode: {
      propDefinition: [
        app,
        "countryCode",
      ],
      description: "The country of the lead (ISO 3166-1 alpha-2 standard).",
      optional: true,
    },
    linkedinUrl: {
      propDefinition: [
        app,
        "linkedinUrl",
      ],
      description: "The address of the public profile on LinkedIn.",
      optional: true,
    },
    phoneNumber: {
      propDefinition: [
        app,
        "phoneNumber",
      ],
      description: "The phone number of the lead.",
      optional: true,
    },
    twitter: {
      propDefinition: [
        app,
        "twitter",
      ],
      description: "The Twitter handle of the lead.",
      optional: true,
    },
    notes: {
      type: "string",
      label: "Notes",
      description: "Some personal notes about the lead.",
      optional: true,
    },
    source: {
      propDefinition: [
        app,
        "source",
      ],
      description: "The source where the lead has been found.",
      optional: true,
    },
    leadsListId: {
      propDefinition: [
        app,
        "leadsListId",
      ],
      description: "The identifier of the list the lead belongs to. If not specified, the lead is saved in the last list created.",
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      app,
      email,
      firstName,
      lastName,
      position,
      company,
      companyIndustry,
      companySize,
      confidenceScore,
      website,
      countryCode,
      linkedinUrl,
      phoneNumber,
      twitter,
      notes,
      source,
      leadsListId,
    } = this;

    const response = await app.createLead({
      $,
      data: {
        email,
        first_name: firstName,
        last_name: lastName,
        position,
        company,
        company_industry: companyIndustry,
        company_size: companySize,
        confidence_score: confidenceScore,
        website,
        country_code: countryCode,
        linkedin_url: linkedinUrl,
        phone_number: phoneNumber,
        twitter,
        notes,
        source,
        leads_list_id: leadsListId,
      },
    });

    $.export("$summary", "Successfully created lead");
    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
Hunter	`app`	`app`	This component uses the Hunter app.
Email	`email`	`string`	The email address of the lead.
First Name	`firstName`	`string`	The first name of the lead.
Last Name	`lastName`	`string`	The last name of the lead.
Position	`position`	`string`	The job title of the lead.
Company	`company`	`string`	The name of the company the lead is working in.
Company Industry	`companyIndustry`	`string`	Select a value from the drop down menu:`AnimalArt & EntertainmentAutomotiveBeauty & FitnessBooks & LiteratureEducation & CareerFinanceFood & DrinkGameHealthHobby & LeisureHome & GardenIndustryInternet & TelecomLaw & GovernmentManufacturingNewsReal EstateScienceRetailSportTechnologyTravel`
Company Size	`companySize`	`string`	The size of the company the lead is working in.
Confidence Score	`confidenceScore`	`integer`	Estimation of the probability the email address returned is correct, between 0 and 100.
Website	`website`	`string`	The domain name of the company.
Country Code	`countryCode`	`string`	The country of the lead (ISO 3166-1 alpha-2 standard).
LinkedIn URL	`linkedinUrl`	`string`	The address of the public profile on LinkedIn.
Phone Number	`phoneNumber`	`string`	The phone number of the lead.
Twitter	`twitter`	`string`	The Twitter handle of the lead.
Notes	`notes`	`string`	Some personal notes about the lead.
Source	`source`	`string`	The source where the lead has been found.
Leads List ID	`leadsListId`	`string`	Select a value from the drop down menu.

Action Authentication#

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

About Hunter#

Verify professional email addresses

More Ways to Connect Hunter + Supabase#

Other Popular Integrations#

Delete Lead with Hunter API on New Row Added from Supabase API

Supabase + Hunter

Try it

Delete Lead with Hunter API on New Webhook Event (Instant) from Supabase API

Supabase + Hunter

Try it

Combined Enrichment with Hunter API on New Row Added from Supabase API

Supabase + Hunter

Try it

Combined Enrichment with Hunter API on New Webhook Event (Instant) from Supabase API

Supabase + Hunter

Try it

Account Information with Hunter API on New Row Added from Supabase API

Supabase + Hunter

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