DocsAutomator MCP integration for AI agents.
Connect AI agents to DocsAutomator through 7 structured actions, including get automation, create document, and create document async. Review authentication…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the DocsAutomator integration exposes
The DocsAutomator Agent App exposes 7 provider-backed actions for productivity and design & media work. Its current contract lets an authorized agent get one docsautomator automation by automationid or docid and return its current generation-related settings, generate one docsautomator document synchronously and return the resulting file urls plus signing metadata when available, and queue one docsautomator document generation job and return the job handle for later polling. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected DocsAutomator account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real DocsAutomator capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_automationREADGet one DocsAutomator automation by automationId or docId and return its current generation-related settings.
INPUTS: automationId / docId
create_documentWRITEGenerate one DocsAutomator document synchronously and return the resulting file URLs plus signing metadata when available.
INPUTS: automationId / docId / data / documentName / webhookParams
create_document_asyncWRITEQueue one DocsAutomator document generation job and return the job handle for later polling.
INPUTS: automationId / docId / data / documentName / webhookParams
get_document_jobREADGet the current status of a DocsAutomator async document generation job and return the finished document result when available.
INPUTS: jobId
get_queue_statsREADReturn current DocsAutomator queue statistics for the connected workspace.
list_automationsREADList DocsAutomator automations in the current workspace with the core fields needed for document generation setup.
list_template_placeholdersREADList the placeholder groups extracted from a DocsAutomator Google Doc template for one automation.
INPUTS: automationId / docId
INPUT CONTRACTS
Know what the action needs before it runs.
get_automation
automationIdOPTIONAL- The DocsAutomator automation ID to target for this request.
docIdOPTIONAL- Alias for automationId accepted by the DocsAutomator API.
create_document
automationIdOPTIONAL- The DocsAutomator automation ID to execute.
docIdOPTIONAL- Alias for automationId accepted by DocsAutomator.
dataOPTIONAL- Template placeholder values forwarded to DocsAutomator. Keys should match your template placeholders.
documentNameOPTIONAL- An optional output document name override.
webhookParamsOPTIONAL- Custom webhook parameters forwarded to DocsAutomator as additionalParams.
create_document_async
automationIdOPTIONAL- The DocsAutomator automation ID to execute.
docIdOPTIONAL- Alias for automationId accepted by DocsAutomator.
dataOPTIONAL- Template placeholder values forwarded to DocsAutomator. Keys should match your template placeholders.
documentNameOPTIONAL- An optional output document name override.
webhookParamsOPTIONAL- Custom webhook parameters forwarded to DocsAutomator as additionalParams.
get_document_job
jobIdOPTIONAL- The DocsAutomator job identifier returned by create_document_async.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Automation
Get one DocsAutomator automation by automationId or docId and return its current generation-related settings. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_automationControl Create Document
Generate one DocsAutomator document synchronously and return the resulting file URLs plus signing metadata when available. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_documentVerify with Get Document Job
Get the current status of a DocsAutomator async document generation job and return the finished document result when available. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_document_jobSAFETY BOUNDARY
Operate DocsAutomator with explicit limits
- Authorize DocsAutomator with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in DocsAutomator rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the DocsAutomator task completed successfully.
CONNECTION MODEL
API key
DocsAutomator API key used with the Authorization Bearer header. Create or copy it from Workspace Settings > API.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by DocsAutomator.