---
title: "DocuSign channel"
slug: "docusign-channel"
updated: 2026-04-29T16:40:50Z
published: 2026-04-29T16:40:50Z
canonical: "help.quickbase.com/docusign-channel"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.quickbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# DocuSign channel

> *Go to the*[*Channels*](https://team.quickbase.com/nav/main/action/pipelines/channels)*page to learn more about what plans have access to this channel. Sign into Quickbase, and then go to Pipelines > Channels.*

DocuSign allows organizations to upload and send documents for electronic signature, select envelope templates, fill the merge fields based on the selection and send them for signing.

Terms used in the DocuSign channel categories are DocuSign-specific terminology.

## How to connect

1. On the My pipelines page, select **Create Pipeline**.
2. Search for or select a step, and then select it to add it to the pipeline. When you add a step to a pipeline, it is added to the canvas of the pipeline designer.
3. Expand the Connection section of the step, and add the required information.

### Connect to DocuSign

1. Expand **DocuSign** in the list of channels on the right side of the page and select **Connect**.
2. In the pop-up window, select **Connect**. ![DocuSign connect dialog with Connect button](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471431006868.png) **Note:** You may be offered to connect with a developer account. Developer (sometimes called Demo) accounts are not used for sending binding contracts, but to test new and existing features. In most cases you should leave the option unchecked. For more information, review DocuSign's [account types](https://support.docusign.com/s/articles/What-are-my-options-for-a-DocuSign-Trial-account?language=en_US).
3. Enter your email and select **Continue**, then enter your password and select **Log in**.
4. Finally, select **Accept** to allow Pipelines to connect to your DocuSign account. ![DocuSign permissions dialog with Accept button](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471424019860.png)

## How to reconnect

You may need to reconnect your account to a channel. Reasons may be (but not limited to):

- If you need to connect a different account.
- Authorization updates, such as a changed password.
- Editing the access rights that Pipelines has to the channel.

To reconnect:

1. Select a pipeline that already has this channel in it.
2. Open a step that contains this channel.
3. Under account, select **Connect (or reconnect)** and follow the steps in [Connect to DocuSign](/v1/docs/docusign-channel#how-to-connect). ![Connection panel showing Connect (or reconnect) option](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/17568569801620.png)

## Steps

The steps you can use with DocuSign fall into two categories: Envelopes and Envelope Statuses.

You cannot use jinja expressions in trigger conditions unless explicitly specified as possible.

| Type | Name | Description |
| --- | --- | --- |
| Envelopes |  |  |
| Action | Upload a Document and Request Signatures | Request signatures on a *single document* from one or more recipients. For more complex scenarios such as requesting multiple signatures on multiple documents, you can use the Send an Envelope for Signatures using a Template step. The file limit is 100MB. |
| Action | Upload and Request a Signature | *Deprecated—Not available for new pipelines Requests a signature on a *single document* with a single recipient. For more complex scenarios you can use the Send an Envelope for Signatures using a Template step. The file limit is 100MB. |
| Action | Send an Envelope for Signatures using a Template | Requests envelope signatures using a template you have already created using the DocuSign My Templates web interface. The file limit is 100MB. |
| Action | Request a Signature from Template | *Deprecated—Not available for new pipelines Requests a signature using a template you have already set up in the DocuSign My Templates web interface. |
| Action | Fetch a Linked Envelope | Fetches a linked envelope. |
| Action | Update Envelope | Updates envelope status - Sending a Draft Envelope - changing the status to Sent - Voiding an In-Process Envelope - changing the status to Voided - Modifying Envelope Email Information - changing the email's subject and body (applicable only for envelopes in Draft status) The file limit is 100MB. |
| Query | List Envelope's Documents | Use this step to query envelope's documents, download them or retrieve document's metadata. |
| Action | Look Up Envelope | Looks up for an envelope based on search criteria (by id). |
| Envelope Statuses |  |  |
| Trigger | Envelope Status Change | Triggers when one of the following events is detected on an envelope: Sent, Delivered, Completed, Declined, and Voided. Not all intermediate events are sent by DocuSign, so it is possible, for example, that an envelope with a single signer gets only the Completed event, without getting Signed status beforehand. This trigger relies on DocuSign Connect functionality, which is not available in all DocuSign subscription plans. To use DocuSign Connect, it must be enabled in your DocuSign account. It is not enabled by default. |
| Trigger | Envelope Completed | Triggers when an envelope is marked completed which means all signers signed the envelope's documents. This trigger relies on DocuSign Connect functionality, which is not available in all DocuSign subscription plans. To use DocuSign Connect, it must be enabled in your DocuSign account. It is not enabled by default. |
| Trigger | Envelope Voided | Triggers when an envelope is voided. You can check the void reason (field) for more details. This trigger relies on DocuSign Connect functionality, which is not available in all DocuSign subscription plans. To use DocuSign Connect, it must be enabled in your DocuSign account. It is not enabled by default. |
| The triggers in this category have settings that can be used to filter incoming events by envelope subject. The filter value can be treated as a regular expression or as text, which should be withing the envelope subject. ![Envelope trigger settings showing subject filter field](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471411785236.png) |  |  |

## Envelope Documents

We have couple of options to access the envelope's documents:

### Option 1

Knowing the envelope id, we can use the List Envelope's Documents step to iterate over each document attached to it.

Useful fields returned within the document record are:

- **name** - The document's file name. Example: Q1-Report.docx
- **browser_url** - Preview file in a browser (Authentication required)
- **file_transfer_handle** - File URL used for internal transfer between different steps
- **document_fields** - An object containing information about the custom fields on the document ![Example of document_fields object with custom field data](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471306892308.png)

### Option 2

The other option is to fetch all the documents combined in one PDF file. To be able to do this you need to have already looked up an envelope in a previous step and use *documents_combined_transfer_handle* field as a Source URL for upload steps from Box, Dropbox, etc. channel. This functionality is coming from DocuSign: ![DocuSign step showing documents_combined_transfer_handle field](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471424093332.png)

You can download an envelope's documents at any time, but the documents may not be signed yet. If you are only interested in downloading signed documents, create a pipeline starting with the Envelope Completed trigger and then use the documents_combined_transfer_handle field or List Envelope's Documents step in combination with the file_transfer_handle field to fetch the signed documents.

## DocuSign templates (Design) + Pipelines (Automate) = Fire and forget

- 
  1. Create an envelope template. (DocuSign) Using the DocuSign My Templates web interface, select **NEW** to prepare your envelope template and then create a name and description on the next window. ![DocuSign new template dialog with name and description fields](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471414110228.png)
  2. Upload Documents. (DocuSign) Upload documents which should be signed and/or enriched with merging fields. ![DocuSign template document upload screen](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471431149460.png)
  3. Define roles and a signing process/order. (DocuSign) Define your signing process and roles responsible for that (signing order can be defined too). **Notes:** it is important to define your recipients' roles, the recipient name and email fields can be left empty and filled later via Pipelines. ![DocuSign recipient role configuration for signing order](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471306898580.png)
  4. Set email details - subject and message. (DocuSign)
    - `Email Subject` can be used for additional filtration, without losing step runs, check for more details the trigger steps.
    - `Email Subject` and `Email Message` can be changed or replaced later via Pipelines. ![DocuSign template email subject and message fields](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471414140564.png)
  5. Add merging fields and signatures on the document's pages. (DocuSign)
    1. Select your recipient's fields and drag-and-drop those which should be filled in by the particular recipient. The fields can be populated later via Pipelines. ![DocuSign recipient's fields panel for drag-and-drop placement](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471306902932.png)
    2. Select the fields you need and put them within the document pages. ![Document page with signature and merge fields placed](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471431242004.png) ![Additional document fields placement example](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471431271956.png) **Note:** Only fields created as a merge field will be shown and fillable via Pipelines. ![Merge field indicator showing field is fillable via Pipelines](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471438750228.png)
  6. Save and close. (DocuSign) ![Save and close button in DocuSign template editor](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471424291092.png)
  7. Go to Pipelines and automate the process. (Pipelines) Using `Send and Envelope for Signatures using a Template` step we can automate the usage of the newly created template. ![Send an Envelope for Signatures using a Template step in Pipelines](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471431347988.png)
  8. Fill the merge fields and recipient's details. (Pipelines) ![Merge fields configuration in Pipelines step](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471414211732.png) ![Recipient details fields in Pipelines step](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471438907796.png)
  9. Schedule or trigger the pipeline. (Pipelines)

You can now schedule the pipeline for example, at the end of the month, to send the employee's paycheck. You also can have the pipeline you created activate with a trigger as your first step. An enabled pipeline will wait until a confirmation email from a candidate is received. Once that happens the pipeline will trigger the Job Offer procedure (for example) and send all the necessary documents to all the signers for signing.