Integration
Connect Documenso to DNSFilter
When something happens in Documenso, your agent does the next thing in DNSFilter. 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 DNSFilter 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 DNSFilter
When Document Completed in Documenso
then Add to Allow List in DNSFilter
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 DNSFilter
Triggers and actions 11 triggers · 7 actions
- Document Cancelled
Fires 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.
- Document Completed
Triggers when a document is signed by all recipients.
- Document Created
Triggers when a new document is created.
- Document Opened
Triggers when a document is opened by a recipient.
- Document Rejected
Fires 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).
- Document Sent
Triggers when a document is sent to recipient(s).
- Document Signed
Triggers when a document is signed by a recipient.
- Blocked Page Form Submitted
Triggers when a user submits the form on the blocked page.
- Blocked Page Visited
Triggered when someone in your DNSFilter account hits a blocked page.
- Invoice Available
Triggered when a new DNSFilter invoice becomes available.
- Policy Changed
Triggered when a DNSFilter policy is created or changed.
- Add to Allow List
Adds a single domain to a DNSFilter policy's allow list, with a note explaining why.
- Add to Block List
Adds a single domain to a DNSFilter policy's block list, with a note explaining why.
- Allow Category in a Policy
Allows a content category in a DNSFilter policy by taking it off that policy's blocked-category list.
- Assign Policy to a Roaming Client
Assigns a DNSFilter policy to a roaming client, so that device filters against that policy.
- Assign Policy to a Site
Assigns a DNSFilter policy to a site, so traffic from that site filters against that policy.
- Block Category in a Policy
Blocks a content category in a DNSFilter policy by adding it to that policy's blocked-category list.
- Create Site
Creates a new site (network) in DNSFilter, optionally on a chosen policy and block 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 DNSFilter
ActiveCampaign to DNSFilterActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to DNSFilterOrganize anything with Airtable, a modern database created for everyone.
Asana to DNSFilterAsana is a collaborative information manager for workspace.
ClickUp to DNSFilterClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Discord to DNSFilterDiscord is an all-in-one voice and text chat for gamers.
Brevo to DNSFilterBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Questions
Documenso and DNSFilter, 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 DNSFilter when something happens in Documenso?
Any of DNSFilter's 7 actions, including Create Site, Add to Allow List, Add to Block List and Allow Category in a Policy. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from DNSFilter to Documenso?
DNSFilter has no triggers in the catalog today, so automations start in Documenso. If you need the other direction, ask: your agent reads DNSFilter's API documentation and adds it.
Do I have to build a connector for Documenso or DNSFilter?
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.