Integration

DocsAutomator integration

DocsAutomator generates PDF (and optionally Google Doc) documents from Google Doc, Word or PDF templates filled with your data, with optional e-signature or one-click acceptance. An agent can create a document from an automation by passing placeholder values and line items, follow an asynchronous generation job, read the queue statistics, list, read, create, update, duplicate and delete automations, list a template's placeholders, duplicate a Google Doc template, and follow e-signature sessions (list, details, signing links, audit trail, cancel, resend an invitation). The test-email route is not exposed. New automations start in test mode (watermarked, free documents) until isPreview is set to false. Authentication is the workspace API key from the DocsAutomator settings, sent as a Bearer token in the Authorization header.

Connect DocsAutomator How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with DocsAutomator

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.

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

Automation, 2 operations

get_automationGet automationGETGets one automation's full configuration: data source, template link, naming, locale, test mode and e-signature signers.
list_automationsList automationsGETLists every automation in the workspace with its data source, template, test mode (isPreview) and e-signature setup. Use _id as automationId.

Session, 2 operations

get_signing_sessionGet signing sessionGETGets an e-signature session: signer statuses and timestamps, e-sign field values, original and signed PDF URLs, document hashes and completion time.
list_signing_sessionsList signing sessionsGETLists e-signature sessions (page, up to 250 per page), filtered by status or by signer email (partial, case-insensitive). Returns each session's status and signers.

Audit, 1 operation

get_signing_auditGet signing auditGETGets the chronological audit trail of a signing session: invitations, views, consents, signatures, declines, completion, with actor, IP and time.

Cancel, 1 operation

cancel_signing_sessionCancel signing sessionPOSTCancels an active signing session. A completed session cannot be cancelled.

Create automation, 1 operation

create_automationCreate automationPOSTCreates an automation for a data source (API, Airtable, Google Sheets ...) with an optional Google Doc template. It starts in test mode: set isPreview false with update_automation to go live.

Delete automation, 1 operation

delete_automationDelete automationDELETEPermanently deletes an automation and all its settings. Irreversible.

Document, 1 operation

create_documentCreate documentPOSTGenerates a document from an automation, filling its template with data. Waits up to 5 minutes and returns pdfUrl; with async true it returns a jobId: then call get_job_status.

Duplicate automation, 1 operation

duplicate_automationDuplicate automationPOSTCopies an automation, with COPY appended to the title. The copy starts in test mode. Returns newAutomationId.

Duplicate google doc template, 1 operation

duplicate_templateDuplicate templatePOSTCopies the Google Doc template of an automation into your Google Drive. Returns the new template's id and edit url.

Job, 1 operation

get_job_statusGet job statusGETGets an asynchronous generation job: status (waiting, active, completed, failed), progress (10 to 100) and, once completed, result with pdfUrl.

Link, 1 operation

get_signing_linksGet signing linksGETGets the signing link of every signer of a session, for manual delivery or to send a link again.

List placeholders v2, 1 operation

list_placeholdersList placeholdersGETLists the placeholders of an automation's Google Doc template, grouped into main and line item groups (line_items_1, line_items_2 ...): the keys to send in create_document data.

Resend, 1 operation

resend_signing_inviteResend signing invitePOSTSends the signing invitation email again to one signer (signerIndex, 1-based) of a session.

Stats, 1 operation

get_queue_statsGet queue statsGETGets the workspace's document generation queue: number of jobs waiting, active, completed, failed and delayed.

Update automation, 1 operation

update_automationUpdate automationPUTUpdates an automation's settings; only the fields sent change. Set isPreview false to make live (unwatermarked, billed) documents.

Use DocsAutomator from Claude Code, Cursor or Codex

Connect DocsAutomator in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its DocsAutomator 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 DocsAutomator

Create your workspace
Sign up free. Nothing to install.
Connect DocsAutomator once
Add your DocsAutomator 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.