DigitalPilot currently provides 2 triggers that can start a workflow and 2 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
New High Intent Visit
Triggers when a business exhibits high intent behavior on your website
New Target Account Visit
Triggers when a business you've identified as a high-priority target account browses your site
Add Target Account
Add a target account to a list
Remove Target Account
Remove a target account from a list
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 DigitalPilot event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New High Intent Visit
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported DigitalPilot 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 Target Account
Combine DigitalPilot with another integration and Coherence records to move information into the same workspace as the people, records, and next steps it affects.
Starts with
New High Intent Visit
Finishes with
Add Target Account, then preserve the outcome in Coherence
The exact authentication fields depend on DigitalPilot. The workflow structure stays straightforward:
Authorize the DigitalPilot 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 DigitalPilot or provide a complementary trigger or action.
DigitalPilot currently provides 2 triggers that can start a workflow and 2 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
DigitalPilot currently lists 2 triggers and 2 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 DigitalPilot 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.
