Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Hunter

Find, verify and manage professional email addresses at scale. Automate email discovery, validation, lead tracking, and campaign outreach with Hunter.io.

CategorySales And Crm
Authenticationcustom
Version0.1.6
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Hunter with Flows360

Find, verify and manage professional email addresses at scale. Automate email discovery, validation, lead tracking, and campaign outreach with Hunter.io.

Use the Hunter connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 9 actions and 1 trigger.

Available actions

  • Add Recipients
  • Count Emails
  • Create Lead
  • Delete Lead
  • Find Email
  • Get Lead
  • Search Leads
  • Update Lead
  • Plus 1 additional declared action.

Available triggers

  • New Lead

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Hunter
  • Package: @activepieces/piece-hunter@0.1.6
  • Exact artifact digest: sha256:9f7ada3699131a63c3d3bf327f48bceb1dfd20350a3de833e0e7e1acee62f1d6
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Add Recipients (add-recipients), Add one or multiple recipients to a campaign. Classification: read.
  • Count Emails (count-emails), Returns the number of email addresses found for a domain or company. Classification: read.
  • Create Lead (create-lead), Create and store a lead record. Classification: read.
  • Delete Lead (delete-lead), Delete a specific lead record by ID. Classification: read.
  • Find Email (find-email), Retrieve/propose the most likely email for a person at a domain. Classification: read.
  • Get Lead (get-lead), Retrieve details of a specific lead. Classification: read.
  • Search Leads (search-leads), List and filter leads in the account. Classification: read.
  • Update Lead (update-lead), Modify existing lead data. Classification: read.
  • Verify Email (verify-email), Check email deliverability and validation status. Classification: read.

Trigger contracts

  • New Lead, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects10
Supported actionsNot published
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Recipients Yes No Add one or multiple recipients to a campaign.
Count Emails Yes No Returns the number of email addresses found for a domain or company.
Create Lead Yes No Create and store a lead record.
Delete Lead Yes No Delete a specific lead record by ID.
Find Email Yes No Retrieve/propose the most likely email for a person at a domain.
Get Lead Yes No Retrieve details of a specific lead.
Search Leads Yes No List and filter leads in the account.
Update Lead Yes No Modify existing lead data.
Verify Email Yes No Check email deliverability and validation status.
New Lead Yes No polling trigger declared by the pinned package.

Triggers

New Lead · Poll

Fires when a new lead is created.

Setup

Setup

  1. Add the Hunter connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-hunter@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 9 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Hunter connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-hunter@0.1.6 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com