List · reads automation
Automations
Triggered flows.
One row per item, the plainest possible view.
- Invoice chaseInvoice 7 days overdue
- Low stock alertStock below reorder point
- Trade routingEnquiry mentions wholesale
- Weekend handoverFriday 17:00
How it works
- 1
Items are listed newest first unless a sort is set.
- 2
Each row shows its title and the two or three fields that matter.
- 3
Filters narrow it without leaving the page.
Best for
Reading and scanning. It is the right default more often than it looks.
Not the right choice for
Comparing many fields at once — use a table.
Questions
What data does the Automations page use?
It reads automation records the agent has collected. Triggered flows. Nothing has to be imported first — the page appears once there is something to show.
Do I have to build or configure it?
No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.
When is a list the wrong choice?
Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.
Does it stay up to date?
Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.
More in Dev & automation
Stripe
Payments and invoices
Connected
Resend
Outbound email
Connected
Google Places
Address lookup
Key expired
Slack
Internal alerts
Not configured
API connectors
Connected live APIs.
Webhooks
Outgoing event hooks.
Datasets
Elastic uploaded data.
Stripe
Payments
Take payment in chat, reconcile invoices
Google Calendar
Scheduling
Two-way sync of bookings
Shopify
Commerce
Read products and stock
Xero
Accounting
Push invoices
Integrations
Third-party links.
Ask for it in a sentence
You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.
Build your agent free