Signature Declined — Agent Notification Workflow
Signature Declined — Agent Notification Workflow
Available from: v0.1.283
When a signature request is declined by a party, the platform automatically notifies the requesting agent in real time — by both in-app notification and email — so they can take immediate action without manually checking signature statuses.
How It Works
This workflow is event-driven. It activates the moment a signature's status transitions to declined.
Trigger
| Property | Value |
|---|---|
| Event | signature.declined |
| Trigger type | Event-driven (automatic) |
| Actor | System (no manual invocation required) |
Actions Performed
1. In-App Error Notification
An error-level notification is immediately pushed to the agent identified by the signature's requestedById field. The notification includes:
- Party name — the name of the party who declined the signature
- Decline reason — the reason provided at the time of declination
- Action link — a direct link to re-send the signature request or handle the declination from within the platform
2. Email Notification
A corresponding email is sent to the same agent (requestedById) containing the same information:
- Party name
- Decline reason
- Direct action link
3. Audit Log Entry
An audit log record is created capturing the declination event, ensuring a full, traceable history of the signature lifecycle for compliance and dispute-resolution purposes.
Entities Involved
| Entity | Role |
|---|---|
signatures | Source of the declined state transition that triggers the workflow |
notifications | Receives the in-app error notification targeting the requestedById agent |
auditLog | Receives a new entry recording the declination event |
Agent Experience
- A party declines a signature request.
- The requesting agent immediately receives an in-app error notification with the party name, decline reason, and an action link.
- The agent also receives an email with the same details.
- The agent clicks the action link to re-send the request or take alternative steps.
- The full interaction is recorded in the audit log.
Notes
- Notifications are sent only to the agent referenced by
requestedByIdon the signature record. - The workflow fires automatically — no configuration or manual trigger is required.
- Both the in-app notification and email are dispatched as part of the same workflow execution, so the agent receives both regardless of whether they are currently logged in.