App Logo
docusign.com

DocuSign whoami (signed-in account)

Report which DocuSign account this browser is signed in as: the user id, email, name, admin flag and permission profile, the current account's number, id and name, its regional DocuSign server, and every account the user belongs to. Being signed out is reported as a normal answer (loggedIn false), not an error. Only a sign-in that persists in the browser ("keep me signed in") is visible to runs.

Input

None

Output

evidence required
loggedIn required
name optional
email optional
userId optional
isAdmin optional
accounts optional
accountId optional

The current account's number (as shown in DocuSign settings).

apiBaseUri optional

The account's regional DocuSign server, e.g. https://eu.docusign.net.

accountName optional
accountIdGuid optional
permissionProfile optional

FAQ

Report which DocuSign account this browser is signed in as: the user id, email, name, admin flag and permission profile, the current account's number, id and name, its regional DocuSign server, and every account the user belongs to. Being signed out is reported as a normal answer (loggedIn false), not an error. Only a sign-in that persists in the browser ("keep me signed in") is visible to runs.
Nothing. It takes no input.
It returns name, email, userId, isAdmin, accounts, evidence, loggedIn, accountId, apiBaseUri, accountName, accountIdGuid, permissionProfile.
Yes. It acts as you on docusign.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the docusign.com cookies saved by the Reduck extension.
It only reads. It looks things up on docusign.com and changes nothing there.
Ask an AI agent connected to Reduck to run reduck/docusign.com/whoami, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/docusign.com/whoami
It is part of Reduck's official curated catalogue.

Start building not clicking