BoldSign delivers eSignature solutions, letting organizations create, send, and manage legally binding documents through streamlined digital signing workflows
BoldSign delivers eSignature solutions, letting organizations create, send, and manage legally binding documents through streamlined digital signing workflows On Nagent, Boldsign is exposed as a fully-configurable signatures integration that any agent can call — 14 actions, and OAuth authentication. No code is required to wire Boldsign into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Boldsign to automate the kinds of tasks signatures teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Boldsign into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Boldsign, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BOLDSIGN_BRAND_GETTool to get brand details by brand ID. Use after obtaining the brand identifier.
Input parameters
Unique identifier of the brand to fetch.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOLDSIGN_BRAND_LISTTool to list all brands in the account. Use after confirming account is authenticated.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOLDSIGN_CUSTOM_FIELD_CREATETool to create a brand-scoped custom field. Use when you need to define and register a new custom field for a specific brand.
Input parameters
Brand identifier to associate the custom field.
Name of the custom field.
Custom form field definition.
Position/order of the custom field.
Whether the field is shared across the organization.
Description/info about the custom field.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOLDSIGN_CUSTOM_FIELD_EDITTool to edit an existing custom field. Use when you need to update a custom field's properties after creation.
Input parameters
Brand identifier to associate the field
Name of the custom field
Custom form field settings as a JSON object, follow API spec for nested properties
Order/position of the custom field
Whether the field is shared across the organization
The ID of the custom field to edit
Description of the custom field
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOLDSIGN_DOCUMENT_BEHALF_LISTTool to list documents sent on behalf of users. Use when fetching and filtering documents you've sent or on behalf of others.
Input parameters
Page number to retrieve (1-based). Default is 1.
Filter by document labels.
Filter by document status. One or more of: None, WaitingForMe, WaitingForOthers, NeedAttention, Completed, Declined, Revoked, Expired, Draft.
End of date range (ISO 8601 date-time string).
Filter by signer email address(es).
Filter by brand ID(s); applies to docs created on/after Oct 4, 2024.
Number of items per page (1-100). Default is 10.
Which documents to list: 'BehalfOfOthers' or 'BehalfOfMe'. Default is 'BehalfOfOthers'.
Keyword to search across title, document ID, sender or signer names.
Start of date range (ISO 8601 date-time string).
Cursor for deep pagination beyond 10,000 records.
Filter by sender identity email address(es).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOLDSIGN_DOCUMENT_EDIT_BETATool to edit a draft or sent document. Use when updating files, recipients, or document settings before finalizing the document.
Input parameters
CC recipients list of objects with EmailAddress.
List of file edits (add/update/remove).
Document title (draft-only).
List of document labels (<=255 chars, no whitespace).
Apply brand by ID (draft-only).
Message for all recipients.
Signer edits (add/update/remove recipients).
Custom metadata key/value pairs.
Disable SMS notifications.
Group rule settings for form fields.
ID of the document to edit.
Expiry value matching ExpiryDateType.
Convert text tags to fields.
Per-signer document settings.
Disable email notifications.
Expiry type unit.
Hide document ID in UI.
Custom download filename format.
Auto reminder configuration.
Unix timestamp to schedule send; null sends immediately.
Enable signing order (draft-only).
List of text tag definition objects.
Localize audit trail.
Notification toggles for document recipients and CC.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOLDSIGN_DOCUMENT_EXTEND_EXPIRYTool to extend a document's expiry date. Use before signing to prolong a document's deadline.
Input parameters
Whether to send notification email one day before expiry. null uses existing setting; true enables notification; false disables.
Email of the user on whose behalf the request is made.
ID of the document to extend expiry for.
New expiry value for the document. Must not exceed 180 days from creation. Format depends on document's default expiry type: 'yyyy-MM-dd' for days, integer hours (e.g., '12') for hours, or ISO 8601 datetime for specific date/time (e.g., '2022-12-15T10:58:04.863Z').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOLDSIGN_DOCUMENT_LISTTool to list documents in My Documents with filters. Use when you need to fetch and filter documents based on various criteria.
Input parameters
Page number to retrieve (1-based). Default is 1.
Filter by document labels.
Filter by sender email address(es).
Filter by document status. One or more of: None, WaitingForMe, WaitingForOthers, NeedAttention, Completed, Declined, Revoked, Expired, Scheduled, Draft.
End of date range (ISO 8601 date-time string).
Filter by brand ID(s).
Number of items per page (1 or more). Default is 10.
Keyword to search across title, document ID, sender or recipient names.
Start of date range (ISO 8601 date-time string).
Cursor for deep pagination beyond 10,000 records.
Filter by recipient email address(es).
Filter by transmission type: 'Sent', 'Received', or 'Both'.
Filter documents by sent between dates or expiring date.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOLDSIGN_DOCUMENT_REMOVE_AUTHENTICATIONTool to remove authentication from a document. Use when you need to disable signer authentication on an existing document before the signing process.
Input parameters
Signer order in recipient list, used to target specific signer when multiple roles share same email.
Email address of the signer whose authentication is to be removed.
ID of the document from which to remove authentication.
Sender's identity email when performing this action on behalf of another user.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOLDSIGN_DOCUMENT_SENDTool to send a document for eSignature. Use when you need to deliver documents to recipients for signing.
Input parameters
List of CC recipients
Base64-encoded files to send. Use either files or fileUrls, not both
Document title displayed in UI and emails
Tags for categorization; no spaces; max 255 chars each
Apply existing brand ID to document emails and pages
Message/instructions for all recipients
List of signers/recipients for the document
Public URLs to files to send. Use either files or fileUrls, not both
Custom key-value metadata (max 50 entries)
Disable document-related SMS messages
Days until document expires
Rules for grouped form fields
Send on behalf of this email address
Convert text tags into BoldSign fields
Per-signer override settings for document metadata
Disable document-related emails
Hide the document ID in communications
Automatically detect fillable fields in files
Custom filename pattern for downloaded document
Configuration for automatic reminders.
Unix timestamp for scheduling send (≥30 min in future)
ISO8601 datetime when generated signing link expires
Enforce sequential signing order
Definitions for text tag conversion
Download option: Combined or Individually
Toggle notifications for all recipients
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOLDSIGN_DOCUMENT_TEAM_LISTTool to list team documents. Use when a team or account admin needs to retrieve all team documents with optional filters.
Input parameters
Page number to retrieve (1-based). Default is 1.
Filter by document labels (tags).
Filter by document status. One or more of: None, WaitingForMe, WaitingForOthers, NeedAttention, Completed, Declined, Revoked, Expired, Draft.
Filter by team ID(s).
Filter by team user ID(s).
End of date range (ISO 8601 date-time string).
Filter by associated brand ID(s).
Number of items per page. Default is 10.
Keyword to search across title, document ID, sender or recipient names.
Start of date range (ISO 8601 date-time string).
Cursor for deep pagination beyond 10,000 records.
Transmission type: 'Sent', 'Received', or 'Both'.
Date filter type: SentBetween or Expiring.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOLDSIGN_EMBEDDED_REQUEST_CREATE_LINKTool to create an embedded request link. Use after specifying title and signers to generate an embeddable URL for in-app document preparation and sending.
Input parameters
Optional files to upload (.pdf,.png,.jpg,.docx).
Document title shown in UI and emails
UI language for embedded experience
Optional message for all recipients
List of signers with their name and email
Optional publicly accessible file URLs (e.g., https://...). Use this instead of uploading files. Do not provide Files when using FileUrls.
URL to redirect after embedded UI finishes
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOLDSIGN_FILE_UPLOADHelper 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).
Input parameters
Base64 encoded file content
MIME type of the file
Filename to use when uploading
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BOLDSIGN_PLAN_GET_API_CREDITS_COUNTTool to get remaining BoldSign API credits count. Use after authenticating your BoldSign account.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 34 agents privately built on Nagent that already use Boldsign.
Build on Nagent
Connect Boldsign to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Boldsign, and click "Connect Now." You'll authenticate with OAuth — Nagent handles credential storage and refresh automatically. Once connected, Boldsign is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Boldsign is connected, you configure its 14 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Boldsign steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Boldsign event fires, the agent kicks off automatically.
Every Boldsign action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Boldsign ships with 14 pre-built signatures actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Boldsign together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Boldsign-based workflows tailored to your business.