Integration

Connect Documenso to Slack

When Document Cancelled fires in Documenso, your agent runs Find User by Email in Slack. 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 Slack to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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.ai

Start 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)

Documenso tells you where each document stands, and Slack is where your team actually reads that news. Joining them means a signature, a rejection or a cancellation in Documenso shows up as a Slack message, direct message, reminder or channel, addressed to the people who handle the paperwork.

Example flows

What Documenso can start in Slack

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 Slack

Triggers and actions 22 triggers · 60 actions

Each app on its own

Reviews

What our customers say

More from Documenso

More into Slack

Questions

Documenso and Slack, answered

Can the agent message the specific person who owns a document, not just a channel?

Yes. Documenso passes the recipient or owner email, and the agent uses Find User by Email in Slack to get the user ID before sending a direct message. If no Slack user matches that address, the scenario can fall back to a channel post instead.

Can anything be written back into Documenso from Slack?

No. Documenso provides triggers only here, such as Document Sent, Document Opened, Document Signed and Document Completed, so Slack receives the events. Everything built runs one way, from Documenso activity into Slack messages, channels, reminders and pins.

What can start an automation from Documenso?

Any of Documenso's 7 triggers in the catalog, including Document Cancelled, Document Completed, Document Created and Document Rejected. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Slack when something happens in Documenso?

Any of Slack's 60 actions, including Create Channel, Create Reminder, Find User by Email and Send Direct Message. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Slack to Documenso?

Slack has no triggers in the catalog today, so automations start in Documenso. If you need the other direction, ask: your agent reads Slack's API documentation and adds it.

Do I have to build a connector for Documenso or Slack?

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.

Can my AI client use Documenso and Slack without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in Slack once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

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.