[ More ]
Docusign integration for your workflows.
Connect Docusign to Collabase once and use 8 actions and 11 triggers in your workflows. No code needed, hosted in Switzerland.
Docusign in Collabase
Connect Docusign to Collabase once and use 8 actions and 11 triggers in your workflows. No code needed, hosted in Switzerland.
How to connect it
- Open the integrations in the workspace settings.
- Choose Docusign and connect your account.
- Add a trigger or an action to the workflow.
Docusign triggers
| Name | Description | Fields |
|---|---|---|
| Signing Request CreatedInstant via webhook | Triggers when a new signing request (envelope) is created in DocuSign — whether sent immediately or saved as a draft. |
|
| Signing Request SentInstant via webhook | Triggers when a signing request is emailed out to recipients for the first time. |
|
| Signing Request Opened by AllInstant via webhook | Triggers when every recipient has opened and viewed the signing request at least once. |
|
| Document Fully SignedInstant via webhook | Triggers when everyone has completed their signature and the document is fully signed. |
|
| Signing RefusedInstant via webhook | Triggers when a recipient refuses to sign, stopping the signing process. |
|
| Signing Request CancelledInstant via webhook | Triggers when the sender cancels an in-progress signing request before everyone has signed. |
|
| Signing Email Sent to PersonInstant via webhook | Triggers when DocuSign sends the signing email to a specific person. |
|
| Person Opened Signing RequestInstant via webhook | Triggers when a specific person opens and views the signing request. |
|
| Person Signed DocumentInstant via webhook | Triggers when a specific person completes their signature on the document. |
|
| Person Refused to SignInstant via webhook | Triggers when a specific person refuses to sign the document. |
|
| Person Failed Identity CheckInstant via webhook | Triggers when a recipient fails the identity verification step before signing. |
|
Docusign actions
| Name | Description | Fields |
|---|---|---|
| Search Signing Requests | Find and list signing requests with optional filters like status, date range, or keyword. |
|
| Get Signing Request Details | Look up the full details of a signing request — status, recipients, and dates — using its ID. |
|
| Download Document from Signing Request | Download a document (or all documents) from a signing request as a file. |
|
| Send Document for Signing | Upload a document and send it to one or more people to sign via DocuSign. |
+ 1
|
| Update Signing Request | Send a draft, cancel, resend reminders, or edit the subject line on a signing request. |
|
| Find Templates by Name | Search for reusable signing templates by name. |
|
| Get People on a Signing Request | Get the full list of people on a signing request — signers, viewers, and anyone copied. |
|
| Custom API Call | Make a custom API call to a specific endpoint |
+ 3
|
[ More ]
Related integrations
Tools that often share a workflow.
Questions about Docusign
What can I automate with Docusign in Collabase?
Docusign brings 8 actions and 11 triggers, for example Search Signing Requests, Get Signing Request Details, Download Document from Signing Request, Send Document for Signing and 4 more. You combine them in a workflow without code and mix them with every other integration.
How do I connect Docusign to Collabase?
You open the integrations in the workspace settings, choose Docusign and connect your account once, using custom credentials. After that all triggers and actions are available in the workflow.
Can Docusign start a workflow?
Yes. Docusign provides 11 triggers, for example Signing Request Created, Signing Request Sent, Signing Request Opened by All and 8 more. The workflow runs as soon as the event happens.
Does the Docusign integration cost extra?
No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.
Test it against your own content. A proof of concept is ready within days.
We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.
