Connecting an integration such as Google Calendar or a CRM
Open Integrations in the sidebar, search the catalogue for the app you want, and choose Connect. You sign in on the provider's own site, and the connection appears against your workspace when you come back.
Last checked against the running product on 30 August 2026.
You connect your own accounts. Garuda does not hold a shared company account for Slack or Google that everybody borrows: you sign in at the provider, the authorisation is stored against your workspace, and no other Garuda customer can see or use it.
The Integrations screen has two halves. This article covers the top one, Connect your apps. The other half, outbound webhooks, is the route for pushing captured leads into a CRM or an automation tool, and has its own article.
Open Integrations
It is in the workspace sidebar, under Widget, at
/app/integrations. Settings, Integrations also links to it.Find the app
The catalogue runs to well over a thousand products, so it arrives a page at a time rather than all at once. Type into Search apps — the results update as you stop typing — or narrow it with the Category dropdown. Show more apps at the foot of the grid fetches the next page, and the line above the grid tells you how many apps are available and how many you have connected.
Choose Connect
Garuda asks the provider for a sign-in link and opens it in a new tab. You authenticate and approve the access on the provider's own site — Garuda never sees or asks for that password.
Allow pop-ups if nothing opens
The sign-in has to open in a new tab, and a browser that blocks one does it silently — no website can tell a blocked tab from a tab that opened behind the window. So if nothing appears, allow pop-ups for this site and choose Connect again. Nothing is authorised until you finish at the provider, so a second attempt costs you nothing.
Finish signing in, then come back
Until the provider confirms, the card reads Awaiting sign-in. Nothing is authorised at that point — a started link is not a connection. Finish in the provider's tab and return to Garuda; the screen rechecks your accounts when you come back to it, and Refresh does the same on demand.
A card that got interrupted keeps Finish connecting and a Cancel beside it, so an abandoned attempt can be discarded rather than left sitting there.
Confirm it says Connected
A live connection carries a green Connected badge and its button changes to Disconnect. Disconnecting removes the authorisation at the provider and takes effect immediately; connecting again means signing in again.
Agents cannot use these connections during a conversation
Connecting an account does not give the agent a tool. Nothing in the chat pipeline calls out to a third party, so an agent cannot check your calendar, look up a contact or write to your CRM mid-conversation. A connection is an authorisation Garuda holds for your workspace, not something the model can reach for while a visitor is typing.
Connecting an app needs an active subscription
Browsing the catalogue is free. Starting a connection is refused without a live plan, with a message saying so. Check Billing if you see it.
Your connections are scoped to your workspace on the server, not just hidden in the interface: the account is taken from your session rather than from anything the browser sends, and a disconnect request for a connection that is not yours comes back as though it does not exist.
If it still does not work
The screen says there is no app catalogue here
This deployment has no integration credentials configured, so there is nothing to browse. That is a property of the installation rather than of your account, and outbound webhooks remain available on the same screen.
The catalogue will not load
A red bar carries the reason. The catalogue is fetched live from the integration provider, so a failure there shows up here; try again in a moment. If it persists, sign out and back in, because an expired session produces the same symptom.
The card still says Awaiting sign-in after you signed in
Nothing tells the workspace tab when the provider's tab finishes. Choose Refresh. If it stays that way, the provider did not complete the authorisation: use Cancel and start again.
The app you need is not in the catalogue
Search a shorter word first — the catalogue lists products under their own names. If it genuinely is not there, an outbound webhook reaches anything with an HTTP endpoint; see Sending leads to your CRM with a webhook, or write to info@ravan.ai and describe what you are trying to connect.
Related articles
- ConfiguringSending leads to your CRM with a webhookRegister a signed HTTPS endpoint on the Integrations screen and Garuda posts every new lead and conversation event to it. Zapier, Make, n8n, Pipedream and most CRMs accept one directly.
- OperatingReading conversations and leadsConversations holds every stored transcript with its page metadata; Leads holds the contacts captured with consent. Both screens are read-only: you cannot type a reply into a visitor's chat from here.
- OperatingExporting your leadsExport CSV on the Leads screen downloads every lead in your workspace as a spreadsheet file, optionally filtered to one status, with eleven columns and a UTF-8 byte order mark.