Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Docusign

Docusign integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.3.0
Published scopes0 published scopes
Last updatedSeptember 29, 2026

Overview

Connect Docusign with Flows360

Docusign integration for Flows360 workflows.

Use the Docusign connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 8 actions and 11 triggers.

Available actions

  • Search Signing Requests
  • Get Signing Request Details
  • Download Document from Signing Request
  • Send Document for Signing
  • Update Signing Request
  • Find Templates by Name
  • Get People on a Signing Request
  • Custom API Call

Available triggers

  • Signing Request Created
  • Signing Request Sent
  • Signing Request Opened by All
  • Document Fully Signed
  • Signing Refused
  • Signing Request Cancelled
  • Plus 5 additional declared triggers.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Docusign
  • Package: @activepieces/piece-docusign@0.3.0
  • Exact artifact digest: sha256:7894aa3582a717109c2bddd82f0b439230694f4c222e1d2d833ef06f40c44eea
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Search Signing Requests (listEnvelopes), Find and list signing requests with optional filters like status, date range, or keyword. Classification: read.
  • Get Signing Request Details (getEnvelope), Look up the full details of a signing request, status, recipients, and dates, using its ID. Classification: read.
  • Download Document from Signing Request (getDocument), Download a document (or all documents) from a signing request as a file. Classification: read.
  • Send Document for Signing (createAndSendEnvelope), Upload a document and send it to one or more people to sign via DocuSign. Classification: read.
  • Update Signing Request (updateEnvelope), Send a draft, cancel, resend reminders, or edit the subject line on a signing request. Classification: read.
  • Find Templates by Name (listTemplates), Search for reusable signing templates by name. Classification: read.
  • Get People on a Signing Request (findEnvelopeRecipients), Get the full list of people on a signing request, signers, viewers, and anyone copied. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Signing Request Created, webhook.
  • Signing Request Sent, webhook.
  • Signing Request Opened by All, webhook.
  • Document Fully Signed, webhook.
  • Signing Refused, webhook.
  • Signing Request Cancelled, webhook.
  • Signing Email Sent to Person, webhook.
  • Person Opened Signing Request, webhook.
  • Person Signed Document, webhook.
  • Person Refused to Sign, webhook.
  • Person Failed Identity Check, webhook.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects19
Supported actionsNot published
Triggers11

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Integration key / Client ID Required
  • RSA private key Required · protected credential
  • Environment Required
  • Impersonated user ID Required
  • scopes Required

Supported objects

ObjectReadWriteNotes
Search Signing Requests Yes No Find and list signing requests with optional filters like status, date range, or keyword.
Get Signing Request Details Yes No Look up the full details of a signing request u2014 status, recipients, and dates u2014 using its ID.
Download Document from Signing Request Yes No Download a document (or all documents) from a signing request as a file.
Send Document for Signing Yes No Upload a document and send it to one or more people to sign via DocuSign.
Update Signing Request Yes No Send a draft, cancel, resend reminders, or edit the subject line on a signing request.
Find Templates by Name Yes No Search for reusable signing templates by name.
Get People on a Signing Request Yes No Get the full list of people on a signing request u2014 signers, viewers, and anyone copied.
Custom API Call Yes No Make a custom API call to a specific endpoint
Signing Request Created Yes No webhook trigger declared by the pinned package.
Signing Request Sent Yes No webhook trigger declared by the pinned package.
Signing Request Opened by All Yes No webhook trigger declared by the pinned package.
Document Fully Signed Yes No webhook trigger declared by the pinned package.
Signing Refused Yes No webhook trigger declared by the pinned package.
Signing Request Cancelled Yes No webhook trigger declared by the pinned package.
Signing Email Sent to Person Yes No webhook trigger declared by the pinned package.
Person Opened Signing Request Yes No webhook trigger declared by the pinned package.
Person Signed Document Yes No webhook trigger declared by the pinned package.
Person Refused to Sign Yes No webhook trigger declared by the pinned package.
Person Failed Identity Check Yes No webhook trigger declared by the pinned package.

Triggers

Signing Request Created · Webhook

Triggers when a new signing request (envelope) is created in DocuSign u2014 whether sent immediately or saved as a draft.

Inputs

  • accountId · string
Signing Request Sent · Webhook

Triggers when a signing request is emailed out to recipients for the first time.

Inputs

  • accountId · string
Signing Request Opened by All · Webhook

Triggers when every recipient has opened and viewed the signing request at least once.

Inputs

  • accountId · string
Document Fully Signed · Webhook

Triggers when everyone has completed their signature and the document is fully signed.

Inputs

  • accountId · string
Signing Refused · Webhook

Triggers when a recipient refuses to sign, stopping the signing process.

Inputs

  • accountId · string
Signing Request Cancelled · Webhook

Triggers when the sender cancels an in-progress signing request before everyone has signed.

Inputs

  • accountId · string
Signing Email Sent to Person · Webhook

Triggers when DocuSign sends the signing email to a specific person.

Inputs

  • accountId · string
Person Opened Signing Request · Webhook

Triggers when a specific person opens and views the signing request.

Inputs

  • accountId · string
Person Signed Document · Webhook

Triggers when a specific person completes their signature on the document.

Inputs

  • accountId · string
Person Refused to Sign · Webhook

Triggers when a specific person refuses to sign the document.

Inputs

  • accountId · string
Person Failed Identity Check · Webhook

Triggers when a recipient fails the identity verification step before signing.

Inputs

  • accountId · string

Setup

Setup

  1. Add the Docusign connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Integration key / Client ID (clientId), required.
  • RSA private key (privateKey), required; stored as a sensitive connection value.
  • Environment (environment), required.
  • Impersonated user ID (impersonatedUserId), required.
  • scopes (scopes), required.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-docusign@0.3.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 8 actions and 11 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Docusign connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-docusign@0.3.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com