Creates, duplicates, and updates document automations, checks the generation queue, and reports where signing sessions stand.
9actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro sets up a new document generation automation with specified data sources and optional Google Doc templates. Automations run on demand or on schedule to eliminate manual generation.
Ayro retrieves all configured automations in the workspace so customers can find and manage their document workflows. Pagination supports browsing large automation collections.
Ayro copies an existing automation with a modified title, enabling quick setup of similar workflows without rebuilding from scratch. Duplicated automations maintain all original settings.
Each card is one request a support team gets, and the Docsautomator actions Ayro runs to close it.
Ayro creates the automation with its data source and Google Doc template link, or duplicates one that already works when the new variant differs by only a few settings.
Ayro lists the automations in a workspace and opens any of them to report the data source settings and template it points at, which is the first question when a generated document comes out wrong.
Ayro updates only the fields that need to move - title, template link, locale settings, activation status - or permanently deletes an automation and its data once nothing depends on it.
Ayro reads the current generation queue statistics for the workspace and lists signing sessions filtered by status or signer email, so a question about a document nobody has received has an answer.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Docsautomator actions it has and picks the ones a request needs.
Authorize the Docsautomator account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Docsautomator actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeDocsautomator · Ayro
What can you do in Docsautomator without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Docsautomator.
Not through this toolkit. Its actions create, read, update, duplicate, and delete automations and report on the queue and signing sessions, but none of them fires a document run. Ayro configures the automation and reports on throughput, while generation is triggered from DocsAutomator or its data source.
All 9 actions your agent can call on Docsautomator, straight from the live MCP connection.
Create a new DocsAutomator automation with specified data source and optional Google Doc template.
Permanently delete an automation and all associated data.
Create a copy of an existing automation with ' COPY' appended to the title.
Retrieve details of a specific automation by its ID.
Retrieve current document generation queue statistics for your workspace.
Retrieve all automations in your workspace with their basic details.
Retrieve signing sessions with optional filtering by status or signer email.
Send a test email with a sample PDF attachment to verify email configuration.
Update an existing automation's settings in DocsAutomator.
Same connection, same setup. Pick the next one your team already uses.
Checks which conversions and engine options exist, exports finished files to S3 or Google Cloud Storage, tracks task status, and manages job webhooks.
Finds the right template, merges conversation data into it, returns the finished document with its download URL, and tidies up what is no longer needed.
Converts files between formats, assembles and watermarks PDFs, runs OCR on scans, and validates addresses and links before they are used.
Reports extracted field values and confidence scores, tracks workflow documents, and creates, trains and tunes OCR models.
Lists the templates a workspace holds with the IDs a render needs, and confirms the workspace behind the API key is active.
Reads a waiver site's required fields, age restrictions, and email settings from the live account, and confirms the event service is still responding.

Authorize the account and your agent has all 9 actions from the first conversation.
