Can Lyro create the document itself?

No. This toolkit acts on documents that already exist in Docnify: adding recipients and fields, sending, resending, reading status, and deleting. Get Template and List Templates read template details but do not instantiate one, so the document is created in Docnify and Lyro takes it from there.

Can Lyro control who signs first?

Yes. Add Document Recipient takes an optional signing order along with authentication options, so a countersignature can be sequenced behind the customer's signature instead of both notifications going out together.

When can fields still be changed on a document?

Before it is sent. Create Document Fields is used after fetching a document and before sending, and Update Document Fields changes labels or requirements on existing fields at the same stage. After a send, a correction means a new request rather than an edit in place.

Is a deleted Docnify document recoverable?

No. Delete Document permanently removes it by ID, so confirm the right document with Get Document or List Documents first. When only one person should lose access, Delete Document Recipient is the narrower action.

Docnify MCP integration

Adds recipients and fields to a document, sends it for signature, resends when it stalls, and reports where signing stands.

Connect Docnify See all integrations

13actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Create document fields
Lyro adds signature, text, and data fields to documents, transforming static files into interactive signing forms. Field creation is the first step before sending for signatures.
Send document
Lyro dispatches a document for signing and notifies all recipients of their signing tasks. Completion status is tracked automatically from send until all signatures are collected.
Get document
Lyro retrieves document details including signing progress and status to update the customer on completion. Signer responses are available immediately after retrieval.

See all 13 actions

How businesses use Docnify + Lyro

Each card is one request a support team gets, and the Docnify actions Lyro runs to close it.

Prepare a document for the people who must sign it
Lyro adds each recipient with their signing order and authentication option, then creates the fields they need to complete, so routing is correct before the document leaves draft.
Add Document RecipientCreate Document FieldsGet Document
Send it out and chase it when it stalls
Lyro sends the document for signature, corrects a recipient's name or email if the first attempt bounced, and re-triggers the signing notification when nobody has acted on it.
Send DocumentUpdate Document RecipientResend Document
Answer where a signature request stands
Lyro fetches a document by ID for its current state and metadata, lists what is outstanding across the account, and reads the templates the team builds requests from.
Get DocumentList DocumentsList Templates
Fix a request that was set up wrong
Lyro changes a field's label or whether it is required, removes a field or a recipient who should not have access, and deletes the document when it has to be reissued from scratch.
Update Document FieldsDelete Document RecipientDelete Document

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Docnify actions it has and picks the ones a request needs.

01
Connect Docnify
Authorize the Docnify account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Docnify actions that close it and chains as many as the request needs.
03
Watch it work
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 free

Docnify · Lyro

Everything else about Docnify

Setup, permissions, and the limits of what Lyro can do inside Docnify.

No. This toolkit acts on documents that already exist in Docnify: adding recipients and fields, sending, resending, reading status, and deleting. Get Template and List Templates read template details but do not instantiate one, so the document is created in Docnify and Lyro takes it from there.

Every action available in Docnify

All 13 actions your agent can call on Docnify, straight from the live MCP connection.

Add document recipient
Add a recipient to a document.
Create document fields
Create one or more fields on a document.
Delete document
Delete a specific document by its ID.
Delete document field
Delete a field from a document.
Delete document recipient
Remove a recipient from a document.
Get document
Fetch a specific document by its ID.
Get template
Fetch a specific template by its ID.
List documents
List documents in the Docnify account.
List templates
List templates in the Docnify account.
Resend document
Resend a document for signing.
Send document
Send a document for signing.
Update document fields
Update metadata of document fields.
Update document recipient
Update a recipient's details (name, email, role) on a document.