List Leads with Hunter API on New Column from PostgreSQL API

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

Trigger workflow on

New Column from the PostgreSQL API

Next, do this

List Leads 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 PostgreSQL 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 Column trigger
1. Connect your PostgreSQL account
2. Configure Polling Interval
3. Select a Schema
4. Select a Table
Configure the List Leads action
1. Connect your Hunter account
2. Optional- Select a Leads List ID
3. Optional- Configure Email
4. Optional- Configure First Name
5. Optional- Configure Last Name
6. Optional- Configure Position
7. Optional- Configure Company
8. Optional- Configure Industry
9. Optional- Configure Website
10. Optional- Configure Country Code
11. Optional- Configure Company Size
12. Optional- Configure Source
13. Optional- Configure Twitter
14. Optional- Configure LinkedIn URL
15. Optional- Configure Phone Number
16. Optional- Select a Sync Status
17. Optional- Select one or more Sending Status
18. Optional- Select one or more Verification Status
19. Optional- Select a Last Activity
20. Optional- Select a Last Contacted
21. Optional- Configure Query
22. Configure Limit
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 Column on PostgreSQL

Description:Emit new event when a new column is added to a table. [See the documentation](https://node-postgres.com/features/queries)

Version:2.0.8

Key:postgresql-new-column

View on GitHub

PostgreSQL Overview#

On Pipedream, you can leverage the PostgreSQL app to create workflows that automate database operations, synchronize data across platforms, and react to database events in real-time. Think handling new row entries, updating records from webhooks, or even compiling reports on a set schedule. Pipedream's serverless platform provides a powerful way to connect PostgreSQL with a variety of apps, enabling you to create tailored automation that fits your specific needs.

Trigger Code#

import common from "../common.mjs"; export default { ...common, name: "New Column", key: "postgresql-new-column", description: "Emit new event when a new column is added to a table. [See the documentation](https://node-postgres.com/features/queries)", version: "2.0.8", type: "source", props: { ...common.props, schema: { propDefinition: [ common.props.postgresql, "schema", ], }, table: { propDefinition: [ common.props.postgresql, "table", (c) => ({ schema: c.schema, }), ], }, }, async run() { const previousColumns = this._getPreviousValues() || []; const columns = await this.postgresql.getColumns(this.table, this.schema); const newColumns = columns.filter((column) => !previousColumns.includes(column)); for (const column of newColumns) { const meta = this.generateMeta(column); this.$emit(column, meta); } this._setPreviousValues(columns); }, };

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
PostgreSQL	`postgresql`	`app`	This component uses the PostgreSQL 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
Schema	`schema`	`string`	Select a value from the drop down menu.
Table	`table`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

Connecting to Restricted Databases

Either enable the shared static IP for this account below, or configure a VPC to deploy any workflow in your workspace to a private network with a dedicated static IP. Learn more in our docs

SSL Setup

Configure SSL on your PostgreSQL database by providing the CA (Certificate Authority), and choosing between Full Verification, Verify Certificate Authority (CA), or Skip Verification. Skipping verification is not recommended as this has serious security implications

About PostgreSQL#

PostgreSQL is a free and open-source relational database management system emphasizing extensibility and SQL compliance.

Action#

List Leads on Hunter

Description:List all your leads with comprehensive filtering options. The leads are returned in sorted order, with the most recent leads appearing first. [See the documentation](https://hunter.io/api-documentation/v2#leads).

Version:0.0.2

Key:hunter-list-leads

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-list-leads", name: "List Leads", description: "List all your leads with comprehensive filtering options. The leads are returned in sorted order, with the most recent leads appearing first. [See the documentation](https://hunter.io/api-documentation/v2#leads).", version: "0.0.2", annotations: { destructiveHint: false, openWorldHint: true, readOnlyHint: true, }, type: "action", props: { app, leadsListId: { propDefinition: [ app, "leadsListId", ], description: "Only returns the leads belonging to this list.", optional: true, }, email: { propDefinition: [ app, "email", ], description: "Filter leads by email. Use `*` for any value, `~` for empty, or specific email.", optional: true, }, firstName: { propDefinition: [ app, "firstName", ], description: "Filter leads by first name. Use `*` for any value, `~` for empty, or specific name.", optional: true, }, lastName: { propDefinition: [ app, "lastName", ], description: "Filter leads by last name. Use `*` for any value, `~` for empty, or specific name.", optional: true, }, position: { propDefinition: [ app, "position", ], description: "Filter leads by position. Use `*` for any value, `~` for empty, or specific position.", optional: true, }, company: { propDefinition: [ app, "company", ], description: "Filter leads by company. Use `*` for any value, `~` for empty, or specific company.", optional: true, }, industry: { propDefinition: [ app, "industry", ], description: "Filter leads by industry. Use `*` for any value, `~` for empty, or specific industry.", optional: true, }, website: { propDefinition: [ app, "website", ], description: "Filter leads by website. Use `*` for any value, `~` for empty, or specific website.", optional: true, }, countryCode: { propDefinition: [ app, "countryCode", ], description: "Filter leads by country code (ISO 3166-1 alpha-2). Use `*` for any value, `~` for empty.", optional: true, }, companySize: { propDefinition: [ app, "companySize", ], description: "Filter leads by company size. Use `*` for any value, `~` for empty, or specific size.", optional: true, }, source: { propDefinition: [ app, "source", ], description: "Filter leads by source. Use `*` for any value, `~` for empty, or specific source.", optional: true, }, twitter: { propDefinition: [ app, "twitter", ], description: "Filter leads by Twitter handle. Use `*` for any value, `~` for empty, or specific handle.", optional: true, }, linkedinUrl: { propDefinition: [ app, "linkedinUrl", ], description: "Filter leads by LinkedIn URL. Use `*` for any value, `~` for empty, or specific URL.", optional: true, }, phoneNumber: { propDefinition: [ app, "phoneNumber", ], description: "Filter leads by phone number. Use `*` for any value, `~` for empty, or specific number.", optional: true, }, syncStatus: { type: "string", label: "Sync Status", description: "Only returns the leads matching this synchronization status.", options: [ "pending", "error", "success", ], optional: true, }, sendingStatus: { type: "string[]", label: "Sending Status", description: "Only returns the leads matching these sending status(es).", options: [ "clicked", "opened", "sent", "pending", "error", "bounced", "unsubscribed", "replied", { value: "~", label: "unset", }, ], optional: true, }, verificationStatus: { type: "string[]", label: "Verification Status", description: "Only returns the leads matching these verification status(es).", options: [ "accept_all", "disposable", "invalid", "unknown", "valid", "webmail", "pending", ], optional: true, }, lastActivityAt: { type: "string", label: "Last Activity", description: "Only returns the leads matching this last activity.", options: [ { value: "*", label: "any", }, { value: "~", label: "unset", }, ], optional: true, }, lastContactedAt: { type: "string", label: "Last Contacted", description: "Only returns the leads matching this last contact date.", options: [ { value: "*", label: "any", }, { value: "~", label: "unset", }, ], optional: true, }, query: { type: "string", label: "Query", description: "Only returns the leads with **First Name**, **Last Name**, or **Email** matching the query.", optional: true, }, limit: { propDefinition: [ app, "limit", ], description: "A limit on the number of leads to be returned. Limit can range between `1` and `1,000`. Default is `20`.", min: 1, max: 1000, }, }, async run({ $ }) { const { app, leadsListId, email, firstName, lastName, position, company, industry, website, countryCode, companySize, source, twitter, linkedinUrl, phoneNumber, syncStatus, sendingStatus, verificationStatus, lastActivityAt, lastContactedAt, query, limit, } = this; const response = await app.listLeads({ $, params: { limit, leads_list_id: leadsListId, email, first_name: firstName, last_name: lastName, position, company, industry, website, country_code: countryCode, company_size: companySize, source, twitter, linkedin_url: linkedinUrl, phone_number: phoneNumber, sync_status: syncStatus, query, last_activity_at: lastActivityAt, last_contacted_at: lastContactedAt, ...(Array.isArray(sendingStatus) && sendingStatus.length && { ["sending_status[]"]: sendingStatus, }), ...(Array.isArray(verificationStatus) && verificationStatus.length && { ["verification_status[]"]: verificationStatus, }), }, }); $.export("$summary", "Successfully retrieved leads"); 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.
Leads List ID	`leadsListId`	`string`	Select a value from the drop down menu.
Email	`email`	`string`	Filter leads by email. Use `*` for any value, `~` for empty, or specific email.
First Name	`firstName`	`string`	Filter leads by first name. Use `*` for any value, `~` for empty, or specific name.
Last Name	`lastName`	`string`	Filter leads by last name. Use `*` for any value, `~` for empty, or specific name.
Position	`position`	`string`	Filter leads by position. Use `*` for any value, `~` for empty, or specific position.
Company	`company`	`string`	Filter leads by company. Use `*` for any value, `~` for empty, or specific company.
Industry	`industry`	`string`	Filter leads by industry. Use `*` for any value, `~` for empty, or specific industry.
Website	`website`	`string`	Filter leads by website. Use `*` for any value, `~` for empty, or specific website.
Country Code	`countryCode`	`string`	Filter leads by country code (ISO 3166-1 alpha-2). Use `*` for any value, `~` for empty.
Company Size	`companySize`	`string`	Filter leads by company size. Use `*` for any value, `~` for empty, or specific size.
Source	`source`	`string`	Filter leads by source. Use `*` for any value, `~` for empty, or specific source.
Twitter	`twitter`	`string`	Filter leads by Twitter handle. Use `*` for any value, `~` for empty, or specific handle.
LinkedIn URL	`linkedinUrl`	`string`	Filter leads by LinkedIn URL. Use `*` for any value, `~` for empty, or specific URL.
Phone Number	`phoneNumber`	`string`	Filter leads by phone number. Use `*` for any value, `~` for empty, or specific number.
Sync Status	`syncStatus`	`string`	Select a value from the drop down menu:`pendingerrorsuccess`
Sending Status	`sendingStatus`	`string[]`	Select a value from the drop down menu:`clickedopenedsentpendingerrorbouncedunsubscribedreplied{ "value": "~", "label": "unset" }`
Verification Status	`verificationStatus`	`string[]`	Select a value from the drop down menu:`accept_alldisposableinvalidunknownvalidwebmailpending`
Last Activity	`lastActivityAt`	`string`	Select a value from the drop down menu:`{ "value": "*", "label": "any" }{ "value": "~", "label": "unset" }`
Last Contacted	`lastContactedAt`	`string`	Select a value from the drop down menu:`{ "value": "*", "label": "any" }{ "value": "~", "label": "unset" }`
Query	`query`	`string`	Only returns the leads with First Name, Last Name, or Email matching the query.
Limit	`limit`	`integer`	A limit on the number of leads to be returned. Limit can range between `1` and `1,000`. Default is `20`.