Bring Hunter activity into Coherence
Start from a supported Hunter event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Lead
Finishes with
Create or update a Coherence record

Find, verify and manage professional email addresses at scale. Automate email discovery, validation, lead tracking, and campaign outreach with Hunter.io.
Hunter currently provides 1 trigger that can start a workflow and 9 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
New Lead
Fires when a new lead is created.
Add Recipients
Add one or multiple recipients to a campaign.
Count Emails
Returns the number of email addresses found for a domain or company.
Create Lead
Create and store a lead record.
Delete Lead
Delete a specific lead record by ID.
Find Email
Retrieve/propose the most likely email for a person at a domain.
Get Lead
Retrieve details of a specific lead.
Search Leads
List and filter leads in the account.
Update Lead
Modify existing lead data.
Verify Email
Check email deliverability and validation status.
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Hunter event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Lead
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Hunter action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Add Recipients
Combine Hunter with another integration and Coherence records to keep account, contact, and deal context attached to the work around it.
Starts with
New Lead
Finishes with
Add Recipients, then preserve the outcome in Coherence
The exact authentication fields depend on Hunter. The workflow structure stays straightforward:
Authorize the Hunter account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Hunter or provide a complementary trigger or action.
Hunter currently provides 1 trigger that can start a workflow and 9 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Hunter currently lists 1 trigger and 9 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Hunter triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.