Actions and WhatsApp
An action is what Qlar does with the result once the task is finished. There are exactly two, and an automation can use one or both.
| Action | Shown to users as | What it does |
|---|---|---|
| Create conversation | New conversation | Puts the result in a new conversation on this agent and notifies the user. |
| Send WhatsApp message | WhatsApp message | Sends the result to a phone number as a WhatsApp message. |
Which of them users may choose is set by Allowed Actions on the policy. There is no email, SMS or other channel; if a user asks for one, the agent says it is not available.
Create conversation
The result becomes a new conversation on the same agent, owned by the user who created the automation.
Time trigger → Generate the sports brief → Create conversation → Notification
| What happens | Detail |
|---|---|
| A conversation appears | In the sidebar list, marked as unread and with an automation icon so it is recognisable. |
| A notification appears | On the bell in the top bar, with an unread badge. Opening it goes to the conversation. |
| The user can continue | It is a normal conversation. The agent knows which automation produced it and what its task was, so "Now compare it with last week" just works. |
A conversation is created only when the run got as far as the action. Runs that failed or whose condition was not met leave nothing in the list.
Send WhatsApp message
The result is delivered as a WhatsApp message to the number stored in the automation.
| Point | Detail |
|---|---|
| Sent from | The platform's shared WhatsApp numbers — not from a number you connect to the agent. |
| Recipient | Any valid phone number the user gives. There is no verification that the number belongs to the user. |
| How the number is read | Qlar normalises it to international format (a leading 0 becomes the country code) and writes it back in the summary — for example +62 812… — so the user can check it. A number that cannot be valid is refused. |
| If no number is given | On WhatsApp, the number the user is chatting from is offered. Otherwise the agent asks. |
| Never sent twice | If Qlar cannot tell whether a message arrived, it does not try again, so nobody gets a duplicate. The history shows "outcome unknown". |
Because there is no verification, two protections exist:
- The user sees the number before agreeing, and must confirm it.
- Limits. The policy's Maximum WhatsApp Messages per Day caps the whole agent, and Qlar allows at most 10 messages an hour to the same number.
Consider the risk for your agent. A typo sends a private result to a stranger, and an agent open to the public could be used to send unwanted messages. If that is not acceptable, allow only Create conversation on the policy, or set a low daily WhatsApp limit.
Using both
An automation may create a conversation and send a WhatsApp message. Each action is recorded separately in the history, so a failed WhatsApp does not hide that the conversation was created — and the reverse.
When an action is not allowed any more
Actions are checked on every run. If you remove one from the policy, automations that use it skip it from then on. If none of an automation's actions is allowed any more, it is stopped with an explanation.