Channels and connected apps

Pilot. Connected apps work today for a small number of workspaces while we test them. They will open to every workspace after the pilot. Live. Website chat and share links for published agents and workforces, and email for published agents. Next. WhatsApp.

What channels and apps do

A channel is where a conversation happens. It starts a task when a message arrives, and carries the agent's reply back.
A connected app is a business app, such as Google Sheets or HubSpot, that an agent can read or update while it works.

Connected apps

Pilot. Available to a small number of workspaces. While the pilot runs, the Integrations page may show a Pilot mode notice with anything extra you need to do.

Dhanur AI connects to more than 2,000 apps through Pipedream Connect, including Google Sheets, Slack, HubSpot, Zoho CRM, Gmail, Notion and LinkedIn.

Connect an app

You need the Owner or Admin role.

Open Integrations in the sidebar.
Under Browse apps, search for the app your business uses.
Select Connect. The app's own sign-in screen opens in a pop-up, so allow pop-ups if nothing happens.
Sign in to the app and allow access.

The account appears under Connected. Connected accounts belong to the whole workspace, and any agent in it can use them for the actions you add. Dhanur AI keeps the account name and its status, not your app password or sign-in tokens.

Admins can Refresh the list to check each connection, reconnect an account, or disconnect it. Everyone else in the workspace can see which accounts are connected.

Add app actions to an agent

You need the Owner, Admin or Builder role.

Open the agent. On the Build tab, find Apps.
Select Add app action and pick an action from a connected app, such as adding a row to a sheet.
For each input, either fix a value yourself, for example which spreadsheet, picked from a list, or let the agent fill it in.
Choose the approval setting. The action is saved to the draft straight away.
Test it, then publish the agent to use the action in real conversations.

An agent can have up to 20 app actions.

Approval rules for app actions

Kind of action	Starts as	Can you change it?
Only reads data	Runs freely	Yes
Changes data	Ask first	Yes
Deletes data	Ask first	No, it always asks

In the test chat, actions that only read data run for real, so you can check the results. Anything that would change data is simulated.

Each app action is recorded as a step on the task, with its outcome and cost. What runs is what was approved. An action runs once; if the result is unclear, the task says so rather than trying again.

Customer channels

Website chat (live): a chat window on your website, answered by your published agent or workforce. Only the sites you list can show it. See Add chat to your website.
Share link (live): a chat page with its own link and QR code, for businesses without a website. Share it on WhatsApp, social media or print. See Share a chat link.
Email (live): an address for each agent. Forward your business inbox to it, and the agent replies by email or just handles each email. See Answer customer emails. An agent can also follow up when a customer goes quiet.
Slack (live): your team asks an agent questions in your own Slack. See Answer your team in Slack.

Google, Slack and HubSpot

These four connect straight to Dhanur AI with the app's own sign-in, separate from the connected apps pilot: Google Calendar for booking appointments, Gmail for outreach from your own address, Slack for answering your team, and HubSpot for copying leads. See Connect Google, Slack and HubSpot.

Coming next

Next. This is being built now.

WhatsApp: customers message your agent on your WhatsApp Business number and the agent replies there. You will also be able to approve an agent's pending actions from WhatsApp.

Triggers and the API

These work today, for published agents:

Schedules: start a task at set times, such as every morning.
Webhooks: start a task when your own systems send data.
The run API: your own code gives an agent a message with a project API key and reads the reply.

See Triggers, API keys and the run API.

Later

Planned. Razorpay payment links in conversations, and voice agents that answer and make calls, with consent checks. Your own MCP servers can already be connected: see Connect your own MCP server.

Rules for messaging customers

Messaging customers in India comes with rules. Agents already say that they are AI in their first reply. As we open channels, we will build in the other checks, such as recording consent before outbound messages and following the TRAI rules on commercial communication (TCCCPR), including registered templates and Do Not Disturb checks.

As the business, you remain responsible for having your customers' consent.