Skip to main content

Chat Actions

Premium Feature

This feature is exclusive to the Standard, Pro, and Enterprise plans, and is not available on the Free plan.

Enable or disable specific actions (also known as AI Tools) that your WiseMind chatbot will use during conversations. These tools expand your assistant's capabilities, allowing it to interact with external systems, collect visitor data, and notify your team in real time.

Current Context

Chat actions are always tied to the selected context. Check the top of the page: "Chat actions are being edited in context: [CURRENT_CONTEXT]".
Each context can have its own enabled and independently configured actions, allowing unique workflows for different pages or situations.

The Actions page displays a panel with cards for the available integration tools:

API Call​

Allows the chatbot to query or send data to external systems using REST endpoints.

Lead Capture​

Enables the chatbot to proactively request, extract, and save the visitor's contact data during the conversation.

Email Notification​

Allows the chatbot to send an automatic email to your team when the user needs direct contact or in specific predefined situations.

API Call​

Set up custom integrations so the chatbot can fetch or send information in real time (e.g.: check order status, retrieve products, create support tickets).

You can add multiple endpoints, respecting your plan's active action limit.

Endpoint Details​

Define the base identity of your request:

  • Endpoint name: A descriptive name (e.g.: Find customer by email).
  • Method: GET, POST, PUT, DELETE, etc.
  • URL: The resource address in the external API.

Authentication​

If your API requires security, click the Authentication button to open the settings modal:

  • Authentication Method and URL: Defines where WiseMind should fetch the token.
  • Body and Headers: Send the required credentials (e.g.: username and password in JSON format).
  • Token path in response: Dot notation to extract the token (e.g.: data.access_token).
  • Expires in (s): Token lifetime so WiseMind knows when to renew it.

Usage and Post-Execution Instructions​

Guide WiseMind on integration behavior:

  • When should this action be used?

    Explain the ideal scenario. E.g.: "Use this action when the customer wants to check an order status. Ask for their CPF before calling the API."

  • Post-execution instructions

    Explain how the assistant should handle the response. E.g.: "Summarize the API response in a user-friendly list format and ask if the customer needs anything else."

Additional Data​

Add optional fields sent in the request when needed. The panel is split into tabs:

  • Headers, Body, Path Params, Querystring
  • You can add multiple items by setting Key and Value in each tab.
Test Endpoint

Before saving, you can expand the Test Endpoint section to simulate a real request with sample values and verify that the configuration is correct.

Lead Capture​

Turn your chatbot into a conversion engine. When enabled, the chatbot starts identifying the ideal moment to collect visitor data.

Additional lead capture instructions​

Use this free-text field to give the chatbot specific guidance on the capture process.

Usage example​

"Wait until the user resolves their main questions before asking for data. Ask for name first, then phone number, and always be polite."

Which lead data should be captured?​

Define the exact fields that the chatbot must extract from the conversation:

  • Automatic Fields: Some essential information (such as Name) is already requested by default.
  • Custom Fields: Click + Add Field to create new requirements, such as phone, job_title, company, etc. The chatbot will understand these names and naturally ask questions to obtain these answers.

Email Notification​

Keep your team informed asynchronously. The chatbot sends an email with the conversation context whenever a configured condition is met.

Who should receive the email?​

  • Recipient Email: The address that will receive notifications (e.g.: sales@yourcompany.com).

Additional email sending instructions​

Define chatbot trigger and sending rules.

Usage example​

"Trigger this email only if the customer requests a complex quote that cannot be answered in chat, or if they explicitly ask to speak with a human agent."

What customer data is required to send the email?​

As with lead capture, you determine which data the chatbot must collect mandatorily before sending the notification.

  • Fields such as Name and Email are usually standard, but you can use the + Add Field button to require other crucial data (e.g.: order_number, role, phone) before sending.

Action Controls​

On the Main List​

  • Enable / Disable button: Quickly turns the chatbot action on or off.
  • Configure button: Opens detailed settings for an already created action.
  • + Add endpoint: Starts creating a new API call.

On Configuration Screens​

  • SAVE CONFIGURATION / SAVE
    • Function: Stores the instructions, variables, and rules defined in the tool.
    • Important: Changes to chatbot behavior only take effect after saving.