Connect eSignatures to Coherence.
. 2 actions can run inside a Coherence workflow.
TRIGGERS AND ACTIONS
Everything eSignatures can do in a workflow.
Actions are the steps a workflow can run in eSignatures. Start the workflow from a Coherence record or another app.
Names as listed in the automation catalog Coherence workflows use.
WORKFLOW IDEAS
What you can automate with eSignatures.
Starting points for a workflow. Choose the exact fields, conditions, and records it updates.
SET UP
How to connect eSignatures.
The exact authentication fields depend on eSignatures. The workflow structure stays straightforward.
RELATED
Apps for the same workflow.
Apps that share a category with eSignatures or provide a complementary trigger or action.
QUESTIONS
eSignatures integration questions.
What can I automate with the eSignatures integration?
eSignatures currently provides 2 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
How many eSignatures triggers and actions are available?
eSignatures currently lists 0 triggers and 2 actions, each named on this page. The list is read from the automation catalog Coherence workflows use, so review those names before building a workflow.
Can eSignatures connect to other apps through Coherence?
Yes. A workflow can combine supported eSignatures 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.
Do I need to write code to connect eSignatures?
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.
