Products and availability
Provide features, pricing, and availability to support questions about your catalog.
Allow the agent to consult orders, products, registrations, and settings during the conversation. Your API provides the data; Whatsplaid uses the relevant information to help the customer.
The connector can receive JSON objects or lists with different structures. You decide what to expose in the API and in which situations the agent should consult it, without limiting the integration to a single type of information.
Provide features, pricing, and availability to support questions about your catalog.
Return the order status, items and delivery information authorized for the customer.
Make relevant customer registration information available to contextualize support.
Help the agent understand the customer's context with configuration, consumption, or limit data returned by your software.
The technical configuration is located under Developers. After testing and activating the connector, choose the API as the knowledge source in the AI agent settings.
01In Developers, open External connectors and select Knowledge base via API. Enter the HTTPS base URL and the Bearer token, when required.
02Configure the endpoint, the query identifier and the name of the parameter expected by the API. Test with an existing record before proceeding.
03In the activation step, describe when the connector should be triggered in the conversation. For example: fetch account data when the customer reports a technical issue and request the registered email if it’s not yet available.
04Enable and save the connector. In AI Agent, open Knowledge Base, select External connector via API, enable its use and save the changes.
05Test conversations with and without the identifier, check the responses, and monitor calls in Recent activity. Adjust the guidelines to your API's purpose.
A consulta acontece quando o contexto e as orientações configuradas pedem informações da fonte externa. Perguntas gerais e saudações continuam seguindo o atendimento do agente.
Yes. Your system must provide a public HTTPS endpoint that receives the configured identifier and returns a JSON object or list with data. The team responsible for the system prepares the integration and its access rules.
Yes. The response can aggregate different authorized data into the same JSON structure. Each agent uses a connector; you can extend the data returned by your system's API.
No. It takes into account the conversation context and the guidance defined in When the connector should be triggered in the conversation. If it needs the identifier and it is not yet available, it requests that information from the customer.
This feature performs GET requests to retrieve information. It is not a mechanism for creating, updating, or deleting records in the connected system.
Without an external connector, Whatsplaid queries your API to support conversations. In a public API setup, your system calls Whatsplaid to operate platform features. Explore the public API and webhooks.
Choose the knowledge source that fits your operation: external API, spreadsheets, or documents. Google Sheets · Document import