Catalogue

Connect the systems your business already runs on, and your agents can read and write to them during a call.

External systems — CRMs, calendars, spreadsheets and similar tools — are connected from the Tools page, one vendor at a time, through that vendor's own sign-in. The catalogue is vendor-branded: you connect to Slack as Slack, never through an unnamed intermediary.

Connecting a system authorises Woise to act on your behalf against that vendor's API. It does not wire the system into any particular workflow — that happens separately, in the builder.

What's in the catalogue

  • Airtable
  • Asana
  • Calendly
  • Gmail
  • Google Calendar
  • Google Sheets
  • HubSpot
  • Microsoft Teams
  • Notion
  • Outlook
  • Pipedrive
  • Salesforce
  • Slack
  • Stripe
  • Zendesk

What a connection can do

Each vendor exposes a curated set of actions — create a record, search contacts, post a message, and the like — rather than its entire API. The curation is deliberate: a vendor with hundreds of endpoints is not a useful menu for an agent mid-conversation, and every action that updates or deletes ships alongside a search or list action the agent can chain to first.

What a given vendor's connection can do inside a workflow is scoped to those actions.

Connecting and disconnecting

A connection is created once per vendor per organization and reused by every workflow that uses it. One organization holds at most one connection per vendor.

Disconnecting removes that authorisation, and the effect is not symmetrical with reconnecting:

  • In-call actions stop working. A workflow still referencing that vendor has nothing to authenticate with.
  • Post-call actions are recorded as permanently failed, with the reason attached. They are not retried once you reconnect, so reconnecting restores future calls rather than replaying past ones.

Either way, a missing connection never crashes the call it belongs to.

Using a connection in a workflow

Wiring a connected vendor into a specific workflow happens in the builder, not here. See integration action node for how a workflow calls out to a connected system mid-conversation.

Common questions

What is Woise?

Woise lets you build AI agents that answer and make phone calls and chat on your website. You lay out the conversation on a visual canvas, try it in your browser, then connect it to a phone number.

Do I need a phone number to start?

No. You can build and test an agent in the browser without one. When you are ready, connect a phone number and choose which agent answers it.

How does billing work?

You pay for the minutes your agents use, from your credit balance. There are no seat fees and no per-agent fees, so an agent that is not taking calls costs nothing.

Which languages can an agent speak?

Agents can listen and speak in more than 40 languages, including English, Spanish, Hindi, Tamil and Arabic. You pick the language and the voice for each agent.

Can an agent connect to my CRM or calendar?

Yes. An agent can look things up and make changes in 26 apps, such as Salesforce, HubSpot, Google Calendar, Slack and WhatsApp, while the caller is still on the line. You connect each app once.

Do I need engineers to build an agent?

No. Everything is built in a visual editor, so you can create and change an agent without writing code. If your team prefers code, there is also a REST API and an MCP server.

What happens to call recordings and transcripts?

Every call keeps a transcript and its outcome, and audio is only recorded if you turn it on. Only people in your account can see your calls, and your account lives in the region you chose when you signed up.

What do I have to set up or run?

None. We run the speech, the language models, the recordings and the phone connections, and scale them with your call volume. There is nothing for you to set up or keep running.

How do I reach the team?

Email contact@woise.ai, call or WhatsApp +91 83412 34080, or use the form on our contact page. A person reads every message.

Still stuck? Talk to our team.