Integration
Connect Documenso to Microlink.io
When something happens in Documenso, your agent does the next thing in Microlink.io. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Documenso and Microlink.io to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Documenso can start in Microlink.io
When Document Completed in Documenso
then Convert file in Microlink.io
When Document Created in Documenso
then Convert URL to markdown in Microlink.io
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Documenso and Microlink.io
Triggers and actions 7 triggers · 11 actions
Trigger
Document CancelledFires on the DOCUMENT_CANCELLED webhook event when a document/envelope is cancelled/voided before completion. Part of Documenso's documented full document lifecycle webhook set.
Trigger
Document CompletedTriggers when a document is signed by all recipients.
Trigger
Document CreatedTriggers when a new document is created.
Trigger
Document OpenedTriggers when a document is opened by a recipient.
Trigger
Document RejectedFires on the DOCUMENT_REJECTED webhook event when a recipient rejects/declines a document. Part of Documenso's documented full document lifecycle webhook set (created, sent, opened, signed, completed, rejected, cancelled).
Trigger
Document SentTriggers when a document is sent to recipient(s).
Trigger
Document SignedTriggers when a document is signed by a recipient.
Action
Convert fileConvert a file (document/image) into HTML, Markdown, or plain text.
Action
Convert URL to markdownConvert the content of any URL into clean, LLM-ready markdown.
Action
Extract textExtract clean, LLM-ready plain text from any page.
Action
Generate embed cardTurn any URL into a rich, embeddable card for display.
Action
Generate PDFCreate a production-ready PDF from a live webpage URL.
Action
Generate screenshotCapture a pixel-perfect screenshot image of any URL.
Action
Get avatarServe a reliable avatar image for an email address or domain via Unavatar.
Action
Get logoFetch the favicon or logo image for a given website.
Action
Get metadataExtract normalized metadata (title, description, image, author, etc.) from any URL.
Action
Get rendered HTMLFetch the fully rendered HTML of a page after JavaScript executes.
Action
Resolve media fileResolve the direct video or audio file URL behind any page.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Documenso
Documenso to ErpnextOpen-source ERP system for accounting, inventory, manufacturing, sales, projects, and CRM.
Documenso to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Documenso to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Documenso to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Documenso to Google SheetsGoogle Sheets
Documenso to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Microlink.io
HubSpot to Microlink.ioHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Microlink.ioSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Microlink.ioSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Microlink.ioGoogle Sheets
Gmail to Microlink.ioGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Microlink.ioGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Documenso and Microlink.io, answered
What can start an automation from Documenso?
Any of Documenso's 7 triggers in the catalog, including Document Completed, Document Created, Document Opened and Document Rejected. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Microlink.io when something happens in Documenso?
Any of Microlink.io's 11 actions, including Convert file, Convert URL to markdown, Extract text and Generate embed card. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Microlink.io to Documenso?
Microlink.io has no triggers in the catalog today, so automations start in Documenso. If you need the other direction, ask: your agent reads Microlink.io's API documentation and adds it.
Do I have to build a connector for Documenso or Microlink.io?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.