Integration
Connect Documenso to Userback
When Document Completed fires in Documenso, your agent runs Add comment in Userback. Describe the whole flow 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 Userback 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 Userback
When Document Completed in Documenso
then Add comment in Userback
When Document Created in Documenso
then Update comment in Userback
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 Userback
Triggers and actions 7 triggers · 12 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
Add comment/1.0/feedback/{id}/comment - comment on a feedback.
Action
Add feedbackCreate a feedback item.
Action
Delete comment/1.0/comment/{id} - delete a comment.
Action
Delete feedback/1.0/feedback/{id} - delete a feedback.
Action
Get comment/1.0/comment/{id} - get a comment.
Action
Get feedback/1.0/feedback/{id} - retrieve a feedback by id.
Action
Get project/1.0/project/{id} - retrieve a project by id.
Action
List feedbacks/1.0/feedback - list feedbacks with filtering, sorting, pagination.
Action
List members/1.0/member - list available members.
Action
List projects/1.0/project - list available projects.
Action
Update comment/1.0/comment/{id} - update a comment.
Action
Update feedback/1.0/feedback/{id} - update a feedback.
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 SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Documenso to ErpnextOpen-source ERP system for accounting, inventory, manufacturing, sales, projects, and CRM.
Documenso to ResendResend is the email API for developers. It's designed for you to build, test, and send transactional and...
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 Google SheetsGoogle Sheets
More into Userback
HubSpot to UserbackHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to UserbackSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to UserbackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to UserbackGoogle Sheets
Gmail to UserbackGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to UserbackGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Documenso and Userback, 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 Userback when something happens in Documenso?
Any of Userback's 12 actions, including Update comment, Update feedback, Add comment and Add feedback. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Userback to Documenso?
Userback has no triggers in the catalog today, so automations start in Documenso. If you need the other direction, ask: your agent reads Userback's API documentation and adds it.
Do I have to build a connector for Documenso or Userback?
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.