Integration

TurboDocx integration

TurboDocx generates Word and PowerPoint documents from templates and collects legally binding e-signatures (TurboSign). With this API an agent can manage templates, reusable variables and tags, generate documents (deliverables) from a template and download them as DOCX, PPTX or PDF, prepare or send documents for signature one by one or in bulk batches, follow signers, status and audit trail, void, resend or remind, and manage the signature webhook and its deliveries. The webhook signing secret is never returned: TurboDocx shows it once, in E-Signature Settings, Webhooks, when it is created or regenerated there, and deliveries are verified with it. Not included: TurboQuote quoting, partner (reseller) management, embedded signing (its signing URLs act as signer credentials), AI variable generation, draft signer editing, webhook secret rotation and the duplicate notify route. Authentication: an API key (Settings, Developers, API keys) sent as a Bearer token, plus the Organization ID from the Features and integrations page in the x-rapiddocx-org-id header.

Connect TurboDocx How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in TurboDocx.Built from the 47 TurboDocx tools below, on the connection you add once.

What you can do with TurboDocx

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Deliverable, 5 operations

create_deliverableCreate deliverablePOSTAgents: ask firstGenerates a document (deliverable) from a template by filling its placeholders; a PDF is made too. Returns the new deliverable id for download_deliverable_file, download_deliverable_pdf or send_signature_request.
delete_deliverableDelete deliverableDELETEAgents: ask firstSoft-deletes a deliverable: it is marked inactive and leaves the lists, its data is retained.
get_deliverableGet deliverableGETAgents: ask firstReturns one deliverable with its template, creator email, file type, fonts and the variable values it was generated with; tags with showTags=true.
list_deliverablesList deliverablesGETAgents: ask firstLists the organization's deliverables (documents generated from templates), page by page: name, template, creator email, file type and size, optionally tags. Filter by name with query.
update_deliverableUpdate deliverablePATCHAgents: ask firstRenames a deliverable, changes its description or replaces its tags. Send only the fields to change; tags replaces the whole tag list ([] removes every tag).

Template, 4 operations

delete_templateDelete templateDELETEAgents: ask firstDeletes a template so it can no longer generate documents; documents already generated stay. There is no undelete.
get_templateGet templateGETAgents: ask firstReturns one template: name, folder, creator, fonts, whether it is a read-only TurboDocx library template, and every variable it can fill (its own, its folder's and the knowledge base's).
update_templateUpdate templatePATCHAgents: ask firstRenames a template, changes its description or folder, or replaces its tags, without touching its file or variables. Send only the fields to change.
upload_templateUpload templatePOSTAgents: ask firstUploads a DOCX or PPTX file as a new template with its variable definitions (a PDF becomes a signature-only template). Use extract_template_placeholders first to get the variables. Counts toward plan limits.

Signature, 3 operations

delete_webhookDelete webhookDELETEAgents: ask firstPermanently deletes the signature webhook and all its delivery history. This cannot be undone; update_webhook with isActive=false only pauses it.
get_webhookGet webhookGETAgents: ask firstReturns the signature webhook: URLs, subscribed events, active state, whether a secret is set, the organization's last-30-days delivery counts and every event type it can subscribe to.
update_webhookUpdate webhookPATCHAgents: ask firstChanges the signature webhook's URLs, events, name or active state; send only what changes. urls and events each replace the whole list. isActive=false pauses delivery.

Tag, 3 operations

create_tagCreate tagPOSTAgents: ask firstCreates an organization-wide tag (a label) to attach to templates, deliverables and variables.
list_tagsList tagsGETAgents: ask firstLists the organization's active tags (id and label), sorted by label by default; search with query.
update_tagUpdate tagPUTAgents: ask firstRenames a tag; every template or variable that carries it keeps the same tag id.

Variable, 3 operations

create_variableCreate variablePOSTAgents: ask firstCreates a reusable text, HTML or image variable in a template folder or in the organization knowledge base, for templates to reference by placeholder.
list_variablesList variablesGETAgents: ask firstLists reusable variables of the organization knowledge base (isGlobal=true) or of one template folder: name, placeholder, content, type. Pass variableMapId to update_variable and delete_variables.
update_variableUpdate variablePUTAgents: ask firstReplaces a reusable variable: a full replace, so send every field to keep (read it with list_variables first); mimeType and text are required on every call.

Action, 2 operations

delete_tagsDelete tagsDELETEAgents: ask firstDeactivates (soft-deletes) one or more tags; ids that do not exist are skipped.
delete_variablesDelete variablesDELETEAgents: ask firstDeletes one or more reusable variables with their versions, tags and stored image files.

File, 2 operations

download_deliverable_fileDownload deliverable fileGETAgents: ask firstDownloads a deliverable in its source format (DOCX or PPTX) as a file. Needs the hasFileDownload license feature and a role other than viewer.
extract_template_placeholdersExtract template placeholdersPOSTAgents: ask firstReads a DOCX or PPTX file and returns the placeholders and fonts it contains, without creating a template. Pass its vars as the variables of upload_template.

Audit trail, 1 operation

get_signature_audit_trailGet signature audit trailGETAgents: ask firstReturns a document's tamper-evident audit trail: every action (prepared, sent, viewed, signed, voided, resent) with time, actor and hash. Details may hold IP addresses and user agents.

Batch, 1 operation

list_signature_batchesList signature batchesGETAgents: ask firstLists the organization's bulk signature batches with their status and job counts (succeeded, failed, pending); filter by name, status or creation dates.

Cancel, 1 operation

cancel_signature_batchCancel signature batchPOSTAgents: ask firstCancels a bulk batch: its pending and processing jobs stop and their credits are refunded; jobs already sent are not affected. This cannot be undone.

Delivery, 1 operation

list_webhook_deliveriesList webhook deliveriesGETAgents: ask firstLists the signature webhook's delivery attempts, newest first: event, URL, HTTP status, attempts, status. Today only isDelivered=false filters correctly.

Download, 1 operation

get_signed_document_linkGet signed document linkGETAgents: ask firstReturns a download URL of the final signed PDF, valid 1 hour, once every signer has signed (status COMPLETED); before that it answers an error.

Ingest, 1 operation

create_signature_batchCreate signature batchPOSTAgents: ask firstSends many documents for e-signature at once: one job per document, processed in the background, each emailing its signers. TurboSign signatures are legally binding. Costs 1 credit per recipient; poll list_signature_batch_jobs.

Job, 1 operation

list_signature_batch_jobsList signature batch jobsGETAgents: ask firstLists the jobs of a bulk batch: each document's status, TurboSign document id, recipient emails and error, plus the batch totals. Poll it after create_signature_batch.

Pdf, 1 operation

download_deliverable_pdfDownload deliverable pdfGETAgents: ask firstDownloads the PDF version of a deliverable as a file.

Prepare for review, 1 operation

prepare_signature_reviewPrepare signature reviewPOSTAgents: ask firstCreates a TurboSign signature request WITHOUT emailing anyone and returns a preview URL where the fields are checked before sending. Give one of file, deliverableId, templateId or fileLink.

Prepare for signing, 1 operation

send_signature_requestSend signature requestPOSTAgents: ask firstSends a document for e-signature: TurboSign emails the signers their links, in signing order (unless sendEmail is false). TurboSign signatures are legally binding. Give one of file, deliverableId, templateId or fileLink.

Previewpdflink, 1 operation

get_template_preview_linkGet template preview linkGETAgents: ask firstReturns a link to a PDF preview of a template.

Recipient, 1 operation

get_signature_recipientsGet signature recipientsGETAgents: ask firstReturns who has signed and who TurboSign still waits on: each signer's effectiveStatus, signing time and email history, the sender and counts. Branch on effectiveStatus, not status.

Replay, 1 operation

replay_webhook_deliveryReplay webhook deliveryPOSTAgents: ask firstRe-sends one past webhook delivery to the URL it targeted, as a new delivery; check it with list_webhook_deliveries.

Resend email, 1 operation

resend_signature_emailResend signature emailPOSTAgents: ask firstEmails the original signing invitation again to signers whose turn it is and who have not signed. Only works once the document was sent for signing.

Save signature setup, 1 operation

delete_template_signature_setupDelete template signature setupDELETEAgents: ask firstRemoves a template's saved signature setup (roles, fields, CC, message, reminders, name). Documents already sent are not affected. Needs the administrator or contributor role.

Send reminder, 1 operation

send_signature_reminderSend signature reminderPOSTAgents: ask firstEmails a reminder now to the signers whose turn it is, outside the automatic schedule; leave recipientIds out to remind every eligible signer. Each result says sent or why it was skipped.

Settings, 1 operation

update_template_signature_settingsUpdate template signature settingsPATCHAgents: ask firstChanges a template's saved signing settings: CC emails, email message, reminders and expiration, document name. Roles and fields never change. Send at least one; a setting left out is kept. Needs the administrator or contributor role.

Signature setup, 1 operation

get_template_signature_setupGet template signature setupGETAgents: ask firstLists the signer roles saved on a template (key, label, order, saved signer, field count). Pass the key as a recipient's role in send_signature_request with that templateId.

Stats, 1 operation

get_webhook_statsGet webhook statsGETAgents: ask firstReturns delivery statistics of the signature webhook over the last N days (1 to 365, default 30): success rate, average response time, and counts per event type.

Status, 1 operation

get_signature_statusGet signature statusGETAgents: ask firstReturns a TurboSign document's status (under_review, completed, voided, expired and so on) and its signing deadline. For who signed, use get_signature_recipients.

Template item, 1 operation

list_templatesList templatesGETAgents: ask firstLists the templates and folders at the workspace root (or, with type=template, every template in every folder): id, name, type, folder, creator email, counts, tags. Template ids feed create_deliverable.

Test, 1 operation

test_webhookTest webhookPOSTAgents: ask firstSends a sample event to every URL of the signature webhook and returns each delivery's result. It creates real delivery records. The webhook must be active.

Void, 1 operation

void_signature_documentVoid signature documentPOSTAgents: ask firstVoids (cancels) a signature request that is not completed: its signing links stop working. This cannot be undone.

Webhook, 1 operation

create_webhookCreate webhookPOSTAgents: ask firstRegisters the signature webhook (name signature) TurboDocx calls on TurboSign events, at up to 10 HTTPS URLs; needs an administrator key. The signing secret is withheld: regenerate it in E-Signature Settings, Webhooks, which shows it once.

With recipient, 1 operation

get_signature_draftGet signature draftGETAgents: ask firstReturns a draft signature request and its signers (name, email, signing order, passcode channel, phone, template role label).

Use TurboDocx from Claude Code, Cursor or Codex

Connect TurboDocx in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its TurboDocx operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect TurboDocx

Create your workspace
Sign up free. Nothing to install.
Connect TurboDocx once
Add your TurboDocx connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.