Integration
Connect Dasha to Huntress
When Added a SIP Trunk fires in Dasha, your agent runs Add organization in Huntress. 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 Dasha and Huntress to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.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 Dasha can start in Huntress
When Added a SIP Trunk in Dasha
then Add organization in Huntress
When Added a SIP Trunk in Dasha
then Update organization in Huntress
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 Dasha and Huntress
Triggers and actions 1 trigger · 16 actions
Trigger
Added a SIP TrunkTriggers when SIP trunk list is changed with dasha sip create-outbound .
Action
Add an Outbound SIP TrunkAdd a SIP trunk for making outbound calls.
Action
Add knowledge baseCreate a new knowledge base.
Action
Add knowledge base documentUpload a document into a knowledge base.
Action
Add phone numberCreate/provision a SIP phone number.
Action
Delete agentDelete an agent by id.
Action
Delete callCancel/delete a queued or in-progress call by id.
Action
Deploy ApplicationDeploy Application to the Dasha Cloud
Action
List knowledge basesList all knowledge bases in the organization.
Action
Synthesize speechConvert text to speech audio using a selected voice.
Action
Update agentUpdate an existing agent's configuration.
Action
Add organizationCreates a new organization in your Huntress account with a name and agent key.
Action
Delete organizationDeletes an organization from your Huntress account, optionally revoking its organization key.
Action
Get organizationReturns the details of a single Huntress organization, including its name, key, agent and incident counts, report recipients and product usage.
Action
List membershipsReturns the user memberships in your Huntress account, optionally filtered by organization, user or permission level.
Action
List organizationsReturns the organizations in your Huntress account, optionally filtered by name or key.
Action
Update organizationUpdates a Huntress organization's name, key or report recipients and returns the updated organization.
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 Dasha
Dasha to GatewayAPI SMSGatewayAPI SMS is an API service providing out- and ingoing SMS message services at competitive prices.
Dasha to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Dasha to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Dasha to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Dasha to Google SheetsGoogle Sheets
Dasha to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Huntress
HubSpot to HuntressHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to HuntressSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to HuntressSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to HuntressGoogle Sheets
Gmail to HuntressGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to HuntressGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Dasha and Huntress, answered
What can start an automation from Dasha?
Any of Dasha's 1 trigger in the catalog, including Added a SIP Trunk. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Huntress when something happens in Dasha?
Any of Huntress's 6 actions, including Update organization, Add organization, Get organization and List memberships. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Huntress to Dasha?
Huntress has no triggers in the catalog today, so automations start in Dasha. If you need the other direction, ask: your agent reads Huntress's API documentation and adds it.
Do I have to build a connector for Dasha or Huntress?
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 Dasha and Huntress without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app 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.