Integration

Actions

Connect your assistant to your own systems. Custom actions let it call your HTTP API mid-conversation; presets are ready-made abilities you just switch on.

Behaviour

What actions are

An action is something the assistant can DO during a conversation, beyond answering from its knowledge base.

A custom action is an HTTPS request you define: a name, a description, a URL and optional inputs. When a visitor asks something the action can answer (an order status, stock availability, a delivery date), the assistant fills in the inputs, calls your endpoint and works the JSON response into its reply.

A preset is a built-in action maintained by Breezaro. You do not configure any URL; you just switch it on. The first presets are Call an operator and Product search.

Step-by-step

Build your first custom action

Five steps from an empty form to a working action. Have the endpoint URL from your own API ready.

  1. Create the action
    In the dashboard, open Custom actions and choose New action. Name it Order status and describe it: Look up an order by its number and return its shipping status.
  2. Point it at the endpoint
    Choose method GET and paste the URL of your endpoint. HTTPS is required, and the host cannot contain a placeholder. Use {{variable}} anywhere in the path or query to insert an input.
  3. Add the input
    Add an input named orderId with a short description (The customer's order number). The assistant extracts its value from the conversation and sends it as a query parameter.
  4. Test it
    Run the built-in test with a sample orderId. You will see the exact response the assistant would receive. An action cannot be enabled until a test has passed.
  5. Enable it
    Flip the switch. From now on, when a visitor asks about their order, the assistant calls your action and answers with live data.
breezaro.com
The Breezaro custom action editor showing method, URL, inputs and secret headers
The action editor: method, URL, inputs and encrypted secret headers
Setup

Import from cURL

If you already have a working curl command (from your API docs or a tool like Postman), paste it into Import from cURL in the action editor. The method, URL, headers and body are prefilled for you.

Behaviour

Presets

Ready-made actions you switch on per assistant.

Call an operator: when a visitor asks for a human, is stuck or frustrated, the assistant escalates immediately without asking any extra questions, notifies your team (email, push notification and a dashboard notification with the reason, plus the visitor's name if they already gave it) and pauses AI replies in that conversation. The visitor can keep writing; everything is saved and waiting for you in the inbox.

The pause ends when an operator takes over the conversation (or resumes the assistant). Repeated requests in the same conversation are rate-limited, so your inbox is not flooded.

Product search: available automatically when your assistant has a product catalog connected. The assistant searches your products and recommends them with live prices and availability. Manage it under Sources → Products.

Templates

Start from a template

A faster path to a working action: pick a template from the presets gallery and the editor arrives pre-filled.

The presets gallery includes full templates, not just toggles. WooCommerce order status is the first one: choosing "Use template" opens the custom action editor with the name, description, request, inputs and suggested response fields already filled in.

What it creates is an ordinary custom action that belongs to you. Review, edit, test or delete it like any other action, and it counts toward the same action limit.

Behaviour

What the AI sees

Run a test call, then tell the assistant exactly which parts of the response it is allowed to see.

After a successful test, the response appears as a checkbox tree. Tick the fields the assistant may use in its replies; everything you leave unchecked never reaches the model, no matter what the endpoint returns.

breezaro.com
The response field selection tree in the test step
Field selection: choose which response fields the assistant may use
Privacy

Ownership check

An optional rule that stops one visitor from reading another visitor's data through the same action.

Pick an input and a response field that must match, for example the visitor's email against the order's billing email. The action only answers when they match, exactly like the WooCommerce order status template does by default. A check can combine one or more conditions, requiring all of them or just one to match.

On a mismatch the assistant sees the same result as a genuine not-found, so it cannot tell a wrong order number from someone else's order. Repeated failed attempts in the same conversation are throttled, so guessing does not pay off.

Privacy

Limits and security

Custom actions are deliberately constrained so a misconfigured endpoint cannot hurt your assistant or your visitors.

  • HTTPS only, GET and POST only. Requests to private or internal network addresses are blocked.
  • Responses must be JSON, up to 16 KB, and arrive within 10 seconds; anything else is cut off.
  • Secret headers are encrypted at rest and never shown again after saving.
  • The assistant may call at most two actions per reply.
  • An action must pass a test before it can be enabled.
  • Actions are available on the Pro plan and higher (and during a trial).
  • Each action call is billed as one extra reply at your assistant's model rate (a 1-credit model adds 1 credit, a 3-credit model adds 3).