Function calling
The LLM can select a configured tool when a request needs an action or external information.

SANIA can use configured functions, APIs, webhooks and actions during a conversation, going beyond document answers when a project needs external data or a specific action.
A knowledge base answers from supplied content. Some requests require dynamic information or an action, in which case SANIA can use a tool included in the configuration.
The tool may call an HTTP endpoint, retrieve data, trigger a client-side action or use a business function exposed by the application.
The LLM can select a configured tool when a request needs an action or external information.
SANIA can call configured HTTP endpoints to exchange data with a third-party system.
A web or application interface can expose actions that SANIA may trigger within the defined scope.
Current data can be used when an integration provides it at conversation time.
The visitor asks for something.
SANIA determines that external data or an action is needed.
The model selects the configured tool.
The API or webhook exchanges the expected data.
SANIA uses the result to continue the conversation.
This does not mean SANIA is connected by default to every CRM, ERP, booking, payment, ticketing or business system.
Each integration must define data exchange, authentication, business rules, failure handling and action boundaries.
Yes. SANIA can use a configured function, API or webhook when a request needs external information or a planned action.
No. The integration capability exists, but a specific system connection must be configured or developed for the relevant project.
Yes, when an integration provides that data at conversation time. SANIA should not be presented as automatically knowing real-time data that has not been supplied.
Tell us which system you need to connect, what data is useful and what actions are expected. We can define the appropriate technical scope.