Data connectors

A data connector is a call to your own system — for example "find an order" in your shop. You set it up once; then Are AI, Flows and Workflows can use it.

Create a connector

Go to Settings → Data connectors → New connector.

1. Name and When to use it — Are AI reads this to decide when to call it, e.g. "When the customer asks where their order is."
2. Request — method and URL, for example https://shop.example.com/api/orders/{{input.order_id}}.
3. Headers — for example Authorization: Bearer …. Values are stored encrypted and never shown again.
4. Inputs — what the call needs, like order_id. Give each a short description.
5. Fields to use from the answer — run a test and click the fields you need, like order.status. Only these fields are passed on.

You can use {{input.key}}, {{contact.email}}, {{contact.user_id}}, {{contact.name}} and {{contact.attributes.key}} in the URL, headers and body.

Keep personal data safe

• Only for identified users (on by default): anonymous visitors can't trigger the connector. Use identity verification on your site.
• Calls go only to public internet addresses, never follow redirects, and time out after 8 seconds.
• Responses are not stored; only whether the call worked.

With Are AI

Switch on Are AI may use it. When a question needs live data, Are AI calls the connector, asks the customer for missing inputs (like the order number) and answers from the result. It can call up to three connectors in a row — for example look an order up, then change it.

Connectors that change something (cancel an order, change an address) need the customer's OK. Are AI first says exactly what it will do and asks the customer to confirm; the call runs only after the customer agrees, and only with exactly the same inputs. This is on by default for every method except GET — change it with Ask the customer before running it.

If your system answers "not found" (for example HTTP 404), Are AI tells the customer and asks them to check what they typed. The conversation goes to your team only when your system can't be reached.

In Flows

Add the step Call a data connector. Fill the inputs from the contact or from earlier answers ({{answer.<step>}}), save fields on the contact, and choose where to go if it works or fails. Later messages can show a field with {{result.status}}.

In Workflows

Use the action Call a data connector. Inputs come from the contact (email, user ID, or an attribute with the same name); the chosen fields are saved on the contact.