Boldsign
for LuumenAI
See every signature request in flight, then extend or resend with approval
Connect BoldSign and ask about signature status without opening the dashboard. List documents in My Documents, team documents, and anything sent on behalf of another user, filtered by status or signer. When something is about to expire or needs to go back out, the agent proposes the change, shows you the document and the new date, and waits for your approval before it touches anything.
The Boldsign toolbox
14 tools: 6 read, 8 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Brand DetailsGet brand details by brand ID.
- ReadList BrandsList all brands in the account.
- ReadList Behalf DocumentsList documents sent on behalf of users.
- ReadList DocumentsList documents in My Documents with filters.
- ReadList Team DocumentsList team documents.
- ReadGet API Credits CountGet remaining BoldSign API credits count.
- WriteCreate Custom FieldCreate a brand-scoped custom field. Approval by default
- WriteEdit Custom FieldEdit an existing custom field. Approval by default
- WriteEdit Document (Beta)Edit a draft or sent document. Approval by default
- WriteExtend Document ExpiryExtend a document's expiry date. Approval by default
- WriteRemove Document AuthenticationRemove authentication from a document. Approval by default
- WriteSend DocumentSend a document for eSignature. Approval by default
- WriteCreate Embedded Request LinkCreate an embedded request link. Approval by default
- WriteUpload File (Helper)Helper action to upload a file to R2 temp via the Composio file pipeline, returning a key that can be passed to FileUploadable fields in other actions (e.g., BrandLogo in brand create). Approval by default
One prompt, start to finish
What a governed Boldsign run looks like inside Luumen.
Questions
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create custom field, edit custom field, edit document (beta), extend document expiry, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Boldsign — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
ConfluenceSOPs and runbooks that become skills the whole team can run.
NotionRunbooks in Notion, followed and turned into skills.
SharePointRead SharePoint sites for context, then change files and permissions on approval.
Google DriveSearch Drive for the file you need, then write the change back as an approved stepPut Boldsign to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.