Tools

This section requires Python familiarity. If you are a non-technical operator, share this page with your developer. For no-code alternatives, see FAQs (actions) or no-code flows.

Functions let your agent perform actions during a conversation — looking up a booking, calling an API, validating input, or writing to a CRM.

If you are looking for a function that only exists inside a single flow, visit the transition functions page.

Functions are Python scripts for deterministic logic and API integrations. Use conv.log to write logs visible in Conversation review → Diagnosis.

For detailed guides, explore the subpages below:

Guides

Reference

If you are looking to use functions to enable multi-site configuration – for example, handling enquiries for multiple store or branch locations – visit the Variants feature page.

Best practices

• Use descriptive names – Action-oriented names like book_reservation or send_notification help the LLM understand when to call the function.
• Write clear descriptions – Explain what the function does, its parameters, and when it should be triggered.
• Use meaningful parameter names – reservation_date is clearer than r_date.
• Control triggering – Define specific rules to prevent over-triggering or under-triggering.
• Test thoroughly – Use Test Cases and Test Sets to validate function behavior across scenarios.

Troubleshooting

• Function not triggering – Check Conversation review → Diagnosis to see if the function was considered. Refine your function description or add clearer rules.
• Wrong parameters – Review conv.log entries to see what the LLM extracted. Adjust parameter descriptions or add validation.
• Unexpected behavior – Simplify function logic and test in isolation before integrating with the agent.