DOCUMENT OPS
Route Declined and Voided Signatures to an Owner for Recovery
When a signer declines or an envelope is voided, captures the stated reason, reassigns the deal to its owner in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerSignature declined/voided webhookHTTP webhook
- LogicSeparate rejections from expirations
- ActionLook up owner and decline reason in AirtableAirtable
- ActionDM the document owner in Slack with the reasonSlack
- OutputOpen Asana recovery task and mark statusAsana
What it does
Makes sure a declined signature never silently kills a deal. When your e-signature provider reports a decline or void, this flow pulls the signer's stated reason, notifies the document's owner directly in Slack, and creates a tracked recovery task so someone follows up to amend terms and resend.
When to use it
Use it when declines currently disappear into a provider dashboard nobody checks, costing you closeable deals. Good for revenue and legal ops teams that want every rejection to land on a named owner with a next step.
How it works
- 1An inbound webhook fires on the provider's "declined" or "voided" event.
- 2A branch separates true rejections from expirations, which are handled elsewhere.
- 3The flow looks up the document's owner and the decline reason from the Airtable tracker.
- 4It sends the owner a direct Slack message with the reason and a link to the original.
- 5It creates an Asana recovery task assigned to that owner and updates the tracker status to "declined - recovering" as the output.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect AirtableBases, tables, views, automations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect AsanaTasks, projects, milestones — everywhere.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Document Ops workflows
Flag redline deviations when a contract lands in Drive
Watches a Google Drive folder for incoming counterparty contracts, diffs each clause against your approved template library.
Gate contract signing on clause-deviation approval
When a contract is submitted for signature via webhook, diffs its clauses against approved templates and either auto-approves clean documents or holds them in Slack for explicit…
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
Log contract clause deviations to a Notion review register
On a daily schedule, scans a Drive contracts folder, diffs clauses against approved templates with OpenAI.
Weekly audit of clause drift across the contract repository
Each week, scans all executed contracts in Drive, measures how far each clause has drifted from approved templates.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.