Integration
Connect DNSFilter and Trengo
When something happens in DNSFilter or Trengo, your agent does the next thing in the other. 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 DNSFilter and Trengo 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 DNSFilter and Trengo can do together
From DNSFilter to Trengo
When Blocked Page Form Submitted in DNSFilter
then Add internal note to ticket in Trengo
From Trengo to 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 DNSFilter and Trengo
Triggers and actions 7 triggers · 22 actions
- 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.
- New Internal Note
Fires when an internal note is added to a Trengo ticket.
- New Outbound Message
Triggers when an outbound message is created.
- Ticket Label Added
Triggers when a label is added to a conversation.
- Add internal note to ticket
Adds an internal note (visible only to agents) to a Trengo ticket.
- Add ticket
Create a new support ticket.
- Add ticket label
Attaches an existing label to a Trengo ticket.
- Create a Contact
Creates a contact on a Trengo channel. If a contact with the same identifier already exists on that channel, Trengo returns the existing contact instead of creating a duplicate.
- Create webhook
Subscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation.
- Delete contact
Delete a contact by id.
- Delete ticket
Delete a ticket by id.
- Find a Contact
Returns the Trengo contacts that match the search term.
- Get contact
Retrieve a single Trengo contact by its id.
- Get webhook
Fetches a webhook by ID, including the event it listens for, the address it sends to and its signing secret. An error occurs if the webhook is not found.
- List contacts
List all contacts.
- List labels
Lists the ticket labels defined in the Trengo account (first page).
- List tickets
Returns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time.
- Send a Message
Sends a reply message on an existing Trengo ticket, over the ticket's own channel.
- Update contact
Update an existing contact by id.
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 DNSFilter
DNSFilter to SupadataSupadata is a service for transcribing YouTube, TikTok, Twitter and Instagram video content, providing...
DNSFilter to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DNSFilter to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
DNSFilter to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
DNSFilter to Google SheetsGoogle Sheets
DNSFilter to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Trengo
Google Calendar to TrengoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
DNSFilter and Trengo, answered
What can start an automation from DNSFilter?
Any of DNSFilter's 4 triggers in the catalog, including Blocked Page Form Submitted, Policy Changed, Blocked Page Visited and Invoice Available. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Trengo when something happens in DNSFilter?
Any of Trengo's 15 actions, including Create a Contact, Create webhook, Send a Message and Update contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Trengo to DNSFilter?
Yes. When something happens in Trengo, your agent can act in DNSFilter too. This page covers both directions: Trengo's triggers and DNSFilter's actions are listed here as well.
Do I have to build a connector for DNSFilter or Trengo?
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.