WhatConverts currently provides 2 triggers that can start a workflow and 4 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 received.
Updated Lead
Fires when an existing lead is updated in WhatConverts.
Create Lead
Create a new lead in WhatConverts.
Export Leads
Retrieves all leads from an account, handling pagination automatically.
Update Lead
Update an existing lead's attributes by its ID.
Find Lead
Find a lead by various criteria.
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 WhatConverts 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 WhatConverts 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
Create Lead
Combine WhatConverts 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
Create Lead, then preserve the outcome in Coherence
The exact authentication fields depend on WhatConverts. The workflow structure stays straightforward:
Authorize the WhatConverts 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 WhatConverts or provide a complementary trigger or action.
WhatConverts currently provides 2 triggers that can start a workflow and 4 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
WhatConverts currently lists 2 triggers and 4 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 WhatConverts 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.
