Built-in tools ship with every agent. They don't need a third-party credential — they either touch chatzuri internals or are pure helpers. Toggle them on under Tools & Actions on any agent.
Lead capture form
Tool id: lead_capture_form.
Renders a structured form (name, email, phone, message, custom fields) inside the chat so the agent can collect lead data without cramming everything into a single sentence. The submission is saved to the conversation's Contact record and shows up under Customers & Conversations → Leads.
Pair this with Leads in the dashboard to configure which fields are required.
Contact manager
Tool id: contact_manager.
Updates the conversation's bound Contact — name, email, phone, tags, custom metadata. The agent reaches for this when the customer reveals their email or phone mid-conversation so subsequent messages from the same person are linked to a single contact across channels.
Remember fact (long-term memory)
Tool id: remember_fact.
Writes a long-term memory entry tied to either the agent or the specific contact. Memory written this way is recalled at the start of future conversations — useful for things like “customer prefers email replies” or “account region is EU”. See How memory works for the full retention model.
Custom button
Tool id: custom_button.
Renders a clickable button inline in the chat reply. Useful for “Book a demo”, “Open dashboard”, “View invoice”. The agent supplies the label and destination URL at call time; the chat widget renders it as a real button instead of a bare link.
Tavily web search
Tool id: tavily_web_search.
Live web search powered by Tavily. The agent uses it to look up current information not in your knowledge base — competitor pricing, today's news, a public company's latest filings.
This is the one built-in that needs a credential. Grab an API key from app.tavily.com and add it as a Tavily credential under Team settings → Credentials.
HTTP request
Tool id: http_request.
A generic outbound HTTP client. The agent picks the method, URL, headers, and body. Use it when the provider you need isn't in the catalogue and you don't want to write a custom action. Optional generic credential (api key, bearer token, basic auth) for adding auth headers.
http_request is the broadest tool you can give an agent. Treat it as an escape hatch — most of the time a first-class tool (e.g. github, stripe) is more constrained and safer.Webhook trigger
Tool id: webhook_trigger.
Fires an HTTP call into your stack with a JSON payload. Useful for “notify Slack when a lead lands”, “ping our analytics endpoint when intent X is detected”, or “forward escalations to PagerDuty”. See Trigger webhooks for setup.
Code execution
Tool id: code_execution.
Runs short snippets of code (Python / JavaScript) for one-off calculations the agent decides it needs. Useful for date math, currency conversion with a known formula, or string manipulation.