File signed Docusign documents into the right Clio matter

When an engagement letter or agreement is signed in Docusign, we file the executed PDF into the matching Clio matter, add a note that it was executed, and confirm in Slack.

Agentic Task
ClioDocusignSlackOperationsData SyncNotifications & AlertsDocument Processing
PromptCreate

Watch Docusign for newly completed envelopes (poll for envelopes that have just reached completed status). Each time an envelope is completed, file the executed document into the right client matter in Clio, then confirm in Slack.

First, get the signed document. Use Docusign List Envelope Documents to list the documents in the completed envelope, then use Docusign Download Document to download the executed PDF as binary content. Read the client or matter name and the signer from the envelope subject and the recipient details so you know which matter this belongs to.

Next, find the matter. Use Clio List Matters to search for the matching matter by the client name or matter name taken from the envelope subject or recipient. Only continue to filing if you have a confident, unambiguous match to a single matter.

If there is a confident match, file it. Use Clio Create Document to upload the signed PDF to that matter, passing the binary content and associating the document to the matter with a nested id object. Then use Clio Create Note to add a note to the matter recording that the engagement letter or agreement was executed, including the document or envelope name, the signer, and the completion date.

Then confirm. Use Slack Send a Message to post a short confirmation to the team channel with the matter name, the signer, and a note that the executed document was filed into Clio.

Handle the no-match case explicitly. If you cannot confidently match the envelope to a single Clio matter, do not upload anything and do not guess. Instead, use Slack Send a Message to ask a human to file it manually, including the envelope subject, the signer, and a link or reference so they can locate it in Docusign. Never file a signed document to a matter you are unsure about.

Additional information

What does this prompt do?
  • Watches Docusign for newly completed envelopes and grabs the executed, signed PDF
  • Finds the matching client matter in Clio using the envelope subject and the signer
  • Files the signed document into that matter and adds a note that the engagement letter or agreement was executed
  • Confirms in Slack with the matter name and signer, or asks a person to file it manually when there is no confident match
What do I need to use this?
  • A Docusign account where your engagement letters and agreements get signed
  • A Clio account with your client matters set up
  • A Slack workspace and channel for confirmations and manual-filing requests
How can I customize it?
  • Choose which Slack channel receives confirmations and manual-filing requests
  • Adjust how strictly an envelope must match a Clio matter before anything is filed
  • Change the wording of the note added to the matter, for example engagement letter versus fee agreement

FAQs

What happens if the workflow cannot tell which matter a document belongs to?
It never guesses. It skips the upload and posts a Slack message asking someone on your team to file it manually, including the envelope subject and the signer so they can find it quickly.
Does this work for any signed document, or only engagement letters?
It works for any completed Docusign envelope. It is especially useful for engagement letters and fee agreements, but you can use it for any executed document that belongs in a client matter.
How does it find the right client matter in Clio?
It reads the envelope subject and the signer details, then looks for the matching matter in Clio by client name or matter name before filing anything.
Will it file the same signed document twice?
No. It only acts on newly completed envelopes, so each signed document is filed once, right after it is finished.
Do I still need to move signed documents by hand?
No. Once a document is signed, it lands in the right matter automatically, with a note recording that it was executed and a confirmation in Slack.

Related templates

Nudge Dynamics 365 deal owners about stale pipeline in Slack

Every weekday morning, an agent reviews your open Dynamics 365 pipeline and privately DMs each rep only the deals that need attention today.

Microsoft Dynamics 365
Slack
Agentic Task
Catch deployments that made your app slower or less reliable

Every hour we compare the 30 minutes before and after each release, and only speak up when a deployment genuinely degraded speed or reliability.

New Relic
Slack
Linear
Agentic Task
Log daily Mercury balances and alert when cash runs low

Every weekday morning, every account balance is logged to a spreadsheet, and you only hear about it in Slack when one drops below the limit you set.

Mercury
Google Sheets
Slack
Deterministic Code
Update Dynamics 365 deals automatically after every Gong call

After every recorded sales call, an agent updates the right deal in Dynamics 365 and posts a Slack recap of exactly what changed.

Gong
Microsoft Dynamics 365
Slack
Agentic Task
File contact sales form leads into Dynamics 365 without duplicates

Every contact sales form submission lands in Dynamics 365 as a clean lead, updating the record you already have instead of creating a second one.

Google Forms
Microsoft Dynamics 365
Slack
Deterministic Code
Turn every New Relic alert into a tracked Jira ticket

Every New Relic alert opens a Jira bug with the full context and a Slack heads up, then closes itself with the incident duration when it recovers.

New Relic
Jira
Slack
Deterministic Code

Stop letting signed agreements pile up in Docusign.

File every executed engagement letter into the right Clio matter automatically, the moment it is signed.

Explore more promptsCreate