Skip to main content
Telara

Integrations / DocuSign

DocuSign logo

DocuSign

DocuSign eSignature for envelopes, templates, recipients, documents, users, and agreement workflow evidence.

OAuth 2.0
Actions
Events

What Telara does

Capability matrix

Indexes NoTracks spend NoDiscovers shadow AI NoRuns actions YesReal-time events Yes

Before you connect

Prerequisites

A DocuSign account that can use the eSignature REST API (typically a plan with API access).
Account admin who can approve connected apps, or a user who can use the Connect button.

Vendor setup

Get the credential

1
Click Connect in Telara
Settings → Integrations → DocuSign. Telara sends you to DocuSign. You do not create an integration key in the DocuSign developer portal unless Telara’s form says you already have one to reuse.
2
Approve access
Sign in. On the consent screen, pick the DocuSign account Telara should see and click Allow.
3
Return to Telara
DocuSign redirects you back. Finish Connect under Settings → Integrations if it is not already marked connected.

Permissions Telara requests

  • signature
    OAuth 2.0
  • impersonation
    OAuth 2.0
  • extended
    OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

DocuSign OAuth integration key. Use production token URL after promotion.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for
  • Account Base Uri

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

Demo / developer accounts and production accounts are different. Promote to production before expecting live envelopes.
The authorizing user must have access to the envelopes you care about.