AI agent actions What the agent does during a conversation
An action is something an agent does for the person it is talking to: check an order in your software, transfer a call, look for the answer in your documents. You create it from the agent that needs it, and it lives on that agent only.
The kinds of action
"Créer une action" (Create an action) offers six kinds to each agent: call transfer only serves a voice agent, relay to another agent only a text agent:
Web service
Calls a web service of your choice: check an order, book an appointment, send information to your software. You copy its address and settings from the service's documentation.
Call transfer
Passes the call to a person or to a number of your choice.
Send an email
Alerts a person on your list by email, readable without access to the console. The email, from "… via Natalia", opens on a card: the "Contact", their "Numéro" (number) to call back in one tap, or "Numéro masqué" (withheld number), "Reçu le" (Received on) and the "Demande" (Request); your text follows, as written, then a "Rappeler" (Call back) or "Voir la conversation" (See the conversation) button. A new action has the subject "Demande d’un interlocuteur : à traiter" (An interlocutor's request: to handle). A deleted conversation sends no email.
Send an SMS
Alerts a person on your list, or the person the agent is talking to, by SMS.
Search in your documents
The agent looks for the answer in the pages of your site, which Natalia reads every day, in the documents you upload, or in the SharePoint and OneDrive files of your connected Microsoft 365 account, read every day and quoted by document visibility.
WhatsApp message
Alerts a person on your list on WhatsApp, from Natalia's WhatsApp number. The message is a fixed template validated by Meta, in which the agent only writes the request. The action does not write to the customer. If Meta refuses the template, a banner at the top of the action says so, with the date: Natalia restores sending, nothing to do on your side.
Relay to another agent
The agent hands the written conversation to another of your agents, for example a specialized one, which replies at once and handles the following messages. In "Créer une action" (Create an action), choose "Relais vers un autre agent" (Relay to another agent), pick the agent under "Agent cible" (Target agent) from "Choisir un agent" (Choose an agent), then say in "Quand l'agent l'utilise" (When the agent uses it) when to relay, for example when the customer asks about an invoice. The relay serves a text agent only, and the target agent does not relay further; without another agent in the organization, or if the target agent is deleted, the relay does not run.
Associating an action with an agent
On the agent's "Configurer" (Configure) tab, "Associer une action" (Associate an action) opens "Créer une action": the action you create joins the agent's diagram. Its panel has three parts.
- "Ce que fait l'action" (What the action does). Its name and its settings, those of a web service included. In the fields of a web service, an email or an SMS, you insert information the agent passes on.
- "Quand l'agent l'utilise" (When the agent uses it). When the action can run at several moments, you pick one: "Quand l'agent le juge utile" (when the agent finds it useful), "Au début de la conversation" (at the start of the conversation), "À la fin de la conversation" (at the end of the conversation), among others. For a voice agent, the end of the conversation is the end of the call; for a text agent, it comes after 30 minutes without a message.
- "Avancé" (Advanced). An optional "Phrase d'attente" (waiting phrase), said during the action to make the person wait, or after it to confirm.
In the header of "Créer une action", "Créer avec Copilot" (Create with Copilot) closes the window and opens Copilot with the request "Crée une action pour « {agent} » qui :" (Create an action for "{agent}" that:) to complete; the plan you apply creates the action, associates it with the agent and imports the documents attached to the conversation. An existing action's panel carries, right of its name, the Copilot button, captioned "Modifier avec Copilot" (Edit with Copilot) on hover: the panel stays open beside Copilot, whose plan shows the changes.
An associated action serves a voice agent as it serves a text agent. On the phone, the agent runs it during the call: the caller hears its "Phrase d'attente", if it has one, at the moment you chose, "Pendant l'action" (During the action) or "Une fois terminée" (Once done). A call transfer says its phrase first, then passes the call.
Setting up a web service
You copy each setting from the service's documentation. At the top, the method (GET, POST, PUT, PATCH or DELETE) and the service address. Below, three sections.
- "En-têtes" (Headers) and "Paramètres" (Parameters). "Ajouter un en-tête" (Add a header) and "Ajouter un paramètre" (Add a parameter) add a row. The Content-Type header follows the body type: you do not type it.
- "Corps" (Body). Sent as "JSON" or as "Formulaire (x-www-form-urlencoded)" (Form). In JSON, you fill in "Champs" (Fields), one per row, or write the JSON by hand. A GET or DELETE call sends no body: its fields stay saved but do not leave.
- A name and a value per row. A typed value leaves as is; an inserted piece of information is passed on by the agent. The padlock, "Valeur sensible" (Sensitive value), hides a secret such as a key: once saved, it shows as dots, and "Remplacer" (Replace) types a new one. A sensitive value holds no inserted information.
Inserting information
In a field of a web service, an email or an SMS, typing { opens the list of information the agent can pass on, as does the "Insérer une info" (Insert an info) button at the end of the field. What you type next filters the list.
-
Three kinds of information. Under "Connu sans le demander" (Known without asking), what the agent's contact points supply, such as "Numéro de l'interlocuteur" (the person's number). Then the agent's variables. Last, "Créer « nom »" (Create "name") adds a new one: "L'agent la récupère pendant l'échange" (the agent gets it during the exchange). A name has no space or accent, for example
email_client. -
The choice inserts
{{name}}. Click an entry, or move with the arrows and press Enter. The field shows the information as a badge; Backspace removes the whole badge, Escape closes the list.
Trying an action without running it
In the "Essayer" (Try) tab, test mode simulates every action: nothing is sent to the service. The action shows in the conversation before the agent's answer, folded into one line, for example « Prendre rendez-vous, simulée : mercredi 7 octobre, 10 h ».
- The request that would leave. Unfolded, a web service action shows its method and path, the service, the status "Non envoyée (mode test)" (Not sent, test mode), and the request body with a copy button. Sensitive values are masked and headers are never shown.
- The source of each variable. Each variable shows its value and one of three sources: "Déduite de la conversation" (deduced from the conversation), "Point de contact" (contact point) or "Valeur fixe" (fixed value). This is how you check what the agent passed on.
- In live mode, actions run. A trial through a real contact point is a real conversation: the actions the agent chooses are carried out.
- A failed action shows on Accueil. When an action fails in a real conversation, the "À traiter" block of Accueil (Home) names it, with the number of conversations concerned: "Action en échec : corrigez l'action ou son service" (Failed action: fix the action or its service).
The full detail of a simulated action is in Try an agent.
Brevo actions
In "Créer une action", the "Brevo" card of the "Marketing" family offers every Brevo action, once Brevo is connected with its API key. A list, a folder, a template, a sender or a contact attribute is chosen from those Brevo lists. An action Brevo carries out shows "Réussi" (Succeeded) on its card; a refusal shows its cause in French. If Brevo refuses the key, or refuses an action to your plan, the Brevo sheet shows "Accès perdu" (Access lost) until you reconnect.
- Contacts. Add, find, update, unsubscribe and delete a contact; list the contacts of a list; import contacts and follow the import; read a contact's statistics; record an event.
- Attributes and lists. List, create, update a choice attribute and delete contact attributes; create, list and read contact lists.
- Companies and CRM. Create, read, list and delete a company; list the CRM notes.
- Senders. List, create and delete senders; list the sending domains.
- Emails and templates. Send an email, written or from a template; list a recipient's events; create, update, read, list and delete email templates.
- Campaigns. Create, update, read, list and send an email campaign; create, read, list and delete an SMS campaign.
- Account. Read the Brevo account.
Two Brevo actions are not offered: sending a transactional SMS, because each SMS is billed and Natalia only offers an action it has tested for real; and calling any Brevo endpoint, which a web service action covers.
Notion actions
In "Créer une action", the "Notion" card of the "Connaissance" (Knowledge) family offers every Notion action, once Notion is connected with your account or an internal integration key. A database, a page or a user is chosen from those Notion lists; Notion only shows Natalia the pages shared with it. An action Notion carries out shows "Réussi" (Succeeded) on its card; a refusal shows its cause in French.
- Pages. Create, read, move a page under another page or into a database, archive or restore a page.
- Page content. Add text to a page, read its content, change a paragraph, delete a block.
- Comments. Comment on a page, read a page's comments.
- Databases. List the databases, read a database's structure, create a database, change a database, search a database with a filter.
- Database rows. Add a row to a database, change a row of a database. "Ajouter une propriété" (Add a property) offers the properties of the chosen database; choosing another database removes the chosen properties. Each value is written in its property's type: title, text, number, select, multi-select, status, checkbox, date, URL, email, phone. A property of another type refuses the write, nothing is written.
- Users. List the users, read a user.
With a key, comments need the "Read comments" and "Insert comments" capabilities of your integration, in Notion's integration settings. Without them, Notion refuses the comment actions and the Notion sheet shows "Accès perdu" (Access lost) until you reconnect.
Some Notion actions are not offered on their own: archiving or restoring a database row, which "Archiver ou restaurer une page" covers, since a row is a page; finding a row or listing a database's pages, which "Chercher dans une base" covers; searching all of Notion, not offered; and calling any Notion endpoint, which a web service action covers.