Follow Avox Docs on Google
Pick Avox Docs as a preferred source and Google shows these pages more often when you search for help with Avox.
Follow Avox Docs on Google
Pick Avox Docs as a preferred source and Google shows these pages more often when you search for help with Avox.
Automations can do more than answer messages. They can start when a row is added to one of your tables, an hour before a booking, or when a customer submits a Flow. Their steps can find, add and change rows, count seats down, make a payment link in a connected app, and put any of those values into the messages they send.
A few examples of what this makes possible:
Everything here is built in the same builder as any other automation, and runs with the same rules: credits, your plan, a paused Switchboard and the 24-hour window.
Pick one of these as the automation's trigger. The first six watch a table; the last one watches a Flow.
A Flow submitted trigger always has a contact: the customer who sent the answers. A table trigger gets its contact from the row. Pick the row's contact or phone column on the trigger, and optionally the WhatsApp number to send from (by default, the number the contact last talked to, else your first connected number).
If the row has no contact or phone, the run still happens, but it can only use table, app and team steps. A message step stops it with AVX-3607.
Every table trigger can check the row before it runs, with up to 10 rules joined by all or any. Each rule takes a column and one of: is, is not, contains, doesn't contain, starts with, is empty, is not empty, is more than / after, is at least / on or after, is less than / before, is at most / on or before, is ticked, is not ticked.
10 is more than 9, and ₹1,299 counts as 1299.2026-11-02, or today or now.Row changed runs on every change of the row. Pick the columns to watch, and it runs only when one of them changes, like an order's Status.
Row matches runs once, at the moment a row starts to match your rules, like Stock at or below Reorder at. It doesn't run again while the row keeps matching, only after it stops matching and then matches again. That's what keeps a low stock alert to one per drop.
Booking triggers work on calendar tables, like the premade Appointments. Pick the status
column and the values that mean cancelled (for example Cancelled). Booking made skips a
booking that's added already cancelled; Booking cancelled runs when the status changes to one
of your cancelled values, and, if you choose, when the booking is deleted.
Date in a row runs before, on or after a date in each row: a reminder an hour before an appointment, a follow-up on the day you set, or a message every year on a birthday.
A few rules keep reminders on time and never confusing:
Flow submitted runs when a customer submits the Flow you pick, once per submission. Their
answers are available as {{flow.<field>}} in every step. This is the only way a submitted Flow
starts an automation: other triggers, like a keyword, never fire on a Flow's answers.
Every change to a table an automation watches is queued, from anywhere: the grid, an import, the API, a Flow, or another automation. Avox works through the queue every 10 seconds and retries anything that fails after 10 seconds, 1 minute, 5 minutes and 30 minutes.
These steps work with tables and connected apps. None of them sends a WhatsApp message, so none of them costs credits.
Change a row, Add to or take from a number and Delete a row each work on one row:
{{reply}}.Find a row looks up the first row that matches all your rules, sorted by a column if you choose. When nothing matches, the step either stops the run (AVX-3619) or carries on with the next step, so a Condition can answer "I couldn't find that order". Every table and app step has the same choice for anything else that goes wrong, like a full table.
Add a row and Change a row fill each column with fixed text, a value, or both, like
Booked by {{contact.name}}. A cell that's exactly one value, like {{row.price}}, keeps its
type, so a number stays a number and a date stays a date. The table's own rules still apply: a
required column needs a value, and a unique column can't repeat one
(AVX-3600).
Add to or take from a number works on a Number, Currency, Rating or Duration column. An empty cell counts as 0. Give it a lowest and highest value if you like, and choose what happens at the limit:
Two runs counting the same row at the same moment never lose a count.
Use a connected app asks an app connected in Connections > Apps to do one thing. You pick what to do; Avox uses whichever connected app does it.
Fill each detail with fixed text or values, like an amount of {{found.price}}. Amounts are
written in normal units, like 499 or 499.50. If no app of the right kind is connected, the step
can't be saved (AVX-3596); if the app says no while running, the step
stops the run or carries on, as you choose (AVX-3605).
Every message, template variable, table cell and app detail can use values written as
{{group.key}}. Click Insert a value next to a text box to pick one instead of typing it.
|: Hi {{contact.first_name|there}} says "Hi there" when the
name is empty.A Condition step can Compare values (a row, a Flow answer...): up to 10 checks like
{{found.status}} is Shipped, or {{row.date}} is today. Numbers compare as numbers, dates
as dates (with today and now), and text ignores capital letters.
A Send a template step fills every variable of the template, in the header, the body and the end of a link button, with fixed text or values. Each variable needs something, or a fallback (AVX-3595). The examples Meta reviewed stay as they are; only the real sends change. The template's page shows which automations fill it, and from which tables, in Filled in by automations (see Template send log).
Only messages cost credits, the same as always: a text 1, buttons or a list 2, a Flow 3, a template 1. Table steps, app steps, conditions and waits are free, whatever values they use. A run that runs out of credits stops before the next message (AVX-3610). See Credits and each automation's credit usage.
These premades use tables. Each one works with a table made from a premade table, like Appointments or Order status; if you don't have it yet, its card says so, with a link to make it. Credits are the most one run can cost.
The templates these premades send are in the Avox template library, ready to submit to Meta.
Automations keep columns by their id, so renaming a column, the table or its API name never breaks them. Deleting a column they use, changing its type, or archiving a table they write to marks them Needs attention on the table's Used by tab, and the automation shows what to fix (AVX-3589, AVX-3590). Archived tables can still be read, so a lookup keeps working.
Every run, and the exact reason one stopped, is in the automation's run log.
Last updated