Integration
Connect Dasha and Rendobar
When something happens in Dasha or Rendobar, 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 Dasha and Rendobar 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 Dasha and Rendobar can do together
From Dasha to Rendobar
When Added a SIP Trunk in Dasha
then Add asset in Rendobar
When Added a SIP Trunk in Dasha
then Add job in Rendobar
From Rendobar to Dasha
When Job completed in Rendobar
then Add an Outbound SIP Trunk in Dasha
When Job completed in Rendobar
then Add knowledge base in Dasha
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 Rendobar
Triggers and actions 2 triggers · 22 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.
Trigger
Job completedFires when a job finishes (success/failure). Backed by the vendor's webhook endpoint delivery mechanism, filtered to job-completion events.
Action
Add assetInitialize an asset (media file) upload.
Action
Add jobCreate a media processing job (transcode, caption, watermark, etc).
Action
Cancel jobCancel a running job.
Action
Delete assetDelete an asset by id.
Action
Get assetGet details of an asset by id.
Action
Get jobGet details of a job by id.
Action
Get job logsGet execution logs for a job.
Action
Get job outputGet the download URL/content for a completed job's output.
Action
List assetsList uploaded assets.
Action
List jobsList jobs for the account.
Action
List job typesList available job types (transcode, caption, watermark, etc).
Action
List modelsList available generation/processing models.
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 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...
Dasha to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Rendobar
HubSpot to RendobarHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to RendobarGoogle Sheets
Gmail to RendobarGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to RendobarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to RendobarGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to RendobarMailchimp marketing automation and email platform.
Questions
Dasha and Rendobar, 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 Rendobar when something happens in Dasha?
Any of Rendobar's 12 actions, including Add asset, Add job, Get asset and Get job. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Rendobar to Dasha?
Yes. When something happens in Rendobar, your agent can act in Dasha too. This page covers both directions: Rendobar's triggers and Dasha's actions are listed here as well.
Do I have to build a connector for Dasha or Rendobar?
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.