Garuda help centre
Short, task-shaped guides to running a Garuda agent. Each one answers a single question completely: what to click, in what order, and what to do when it does not work.
Checked against the running product on 30 August 2026. Where something is not built yet, the article says so rather than describing a screen that does not exist.
14 articles, grouped into 4 sections.
Getting started
From an empty workspace to a working chat widget on your own site.
- Creating your first agentAnswer four setup questions to get a drafted agent, or build one by hand in Agents. Either way it stays a draft until you add an allowed domain and publish it.
- Adding knowledge your agent can answer fromPaste approved text into the Knowledge section of the agent editor. Each agent holds up to five sources of up to 100,000 characters each. Website crawling is not built.
- Installing the widget on your websiteCopy the one-line script from Widget, Install and paste it before the closing body tag on every page that should show the chat. Step-by-step guides for Webflow, WordPress, Shopify and Framer are on the same tab.
- Approving the domains your agent may run onThe allowed domain is set in the agent editor, under Appearance. Garuda compares it to the browser origin exactly, with no wildcards and no automatic subdomain matching.
Configuring
How the widget looks, what it asks for, and where the answers go.
- Customising the widget's appearanceWidget, Customize holds six numbered sections: bot identity, theme, chat logo, placement, nine toggles and the lead form. Changes preview live and are written when you save.
- Setting up lead capture and consentLead capture is on by default and offers the contact form from the visitor's third message. Nothing is stored until the visitor ticks the consent box, and the server refuses submissions without it.
- Building a custom lead formSection 6 of Widget, Customize lets you set the heading, the submit text and up to 20 fields, each with a type and an identifier that decides where the answer is stored.
- Handing a conversation to a person on WhatsAppSwitch on Handoff rules in the agent editor and add your WhatsApp number. A button appears in the widget, and tapping it opens WhatsApp with a message already typed. Your number is never published on your website.
- Connecting an integration such as Google Calendar or a CRMIntegrations in the workspace sidebar holds a searchable catalogue of third-party apps. Choose one, sign in with the provider in its own tab, and the connection belongs to your workspace.
- Sending 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.
Operating
Living with it: reading what came in, getting it out, and turning it off.
- Reading 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.
- Exporting 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.
- Pausing or unpublishing an agentPause takes a published agent off the air from its detail page and keeps every setting; resuming is one click back. Unpublishing to Draft has no button in the portal yet.
Troubleshooting
The problems people actually hit, in the order worth checking them.
Not what you were looking for?
The frequently asked questions cover what Garuda is and what it costs. The security and data handling page covers consent, visitor identity and the third parties in the data path. The blog is for the wider questions about website chat rather than for operating this product.
Still stuck?
Every article here is written from the product as it works today. If something on this page does not match what you see in your workspace, trust the product and tell us — include the page you were on and what you expected.