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.1",
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;
},
};
Chase Roberts@chsrbrts@benedictevans If you haven’t used @pipedream yet, then you haven’t lived.
✨Ellie Day✨@heyelliedayEvaluation update: @pipedream has quite literally been a dream to work with! I’m excited to leverage this tool for all the various workflows I need to write. I’m currently at 11k invocations a day from the initial workflows I’ve written in the past couple weeks.
Michael Braedley@MBraedleyUpdate: I got it working properly, and it's working so well that I'm dropping IFTTT. @pipedream can do everything that IFTTT basic can, and most (if not all things) IFTTT pro can for free or at a reasonable price if you need it. I am recommending it for basically any power user.
Thomas Cutting@mrthomascuttingWant quick+dirty integrations for a serverless workflow - @pipedream is my new go-to 😃
Matthew Roberts@mattdotrobertsday 013 - finally hit node js. This is the secret sauce of taking #nocode projects that one step further. Pumped about getting deeper into @pipedream now
Kenneth Auchenberg 💭@auchenbergYahoo Pipes is back! Kinda 😍 @pipedream
Raymond Camden 🥑@raymondcamdenAwesome video by the @pipedream folks showing real time twitter sentiment analysis integrated with Google Sheets. This is where Pipedream *really* shines, connecting systems together in easy workflows.
Nacho Caballero@nachocaballeroI couldn't recommend @pipedream more. It's an amazing service to integrate different APIs. Much more powerful than Zapier and more user-friendly than AWS Lambda. I'm very proud to wear this t-shirt #NoCode
Jason Snow@jyksnwDeveloped a working prototype environmental sensor IoT solution with @particle Photon, @pipedream, and @MongoDB with full graphing and alerting in less than a day! All amazing technology, will def. be exploring these more.
Steven Terrana@steven_terrana@burgwyn you've inspired me to finally set up my own blog. I'll make sure my first blog post explains the tech behind the setup. think @obsdmd + @GatsbyJS + @pipedream.
🚄 James Augeri, PhD@DotDotJamesWant to low-code your back end, need more horsepower than @Bubble / @KnackHQ, or just miss Yahoo! Pipes? Check out @PipeDream
Sébastien Chopin@AtinuxGitHub issues should be like @linear_app for maintainers. Looking forward more integrations with GH actions or tools like @pipedream 👀
Raul@raul_predescuIf you're a dev and not using @pipedream, you're missing out. Been using it for months, daily. FREE for devs. Plenty of integrations and good limits. Absolutely love it.
Bruno Skvorc@bitfallsSo @pipedream is pretty amazing. In 3 minutes I just made a flow which adds @rickastley's Never Gonna Give You Up to my @spotify playlist whenever a new pull request arrives in an old repo of mine.
Zach Lanich@ZachLanichUm, wow 🤯 @pipedream
Steven Bell@bellontechI just used @pipedream to build a Shopify App. Wow, they make small backed tasks easy.
Jay Hack 🎩🇺🇸@_jayhack_Very impressed with this bad boi - it reminds me of a @PalantirTech internal tool, but geared towards integrations instead of data analysis and far more customizable. Great expectations here 🚀🤩
Tree Sturgeon 🔥🚴♂️🌳@philsturgeonFor context this is day 2 of a really challenging and stupid migration from Notion to @airtable with disparate/missing data. It's going better than expected and thanks to @pipedream I don't have to bother the iOS dev to add W3W.