Describe a repeating task in words, choose when it runs (by the clock or when something happens), and the builder writes it. Run, test, pause and see its history.
An automation saves you a task that repeats: a daily report, a reminder to customers, cleaning out old data. You write what should happen in plain words, choose when, and the builder writes the automation for you. After that it runs by itself.
Screen recording: Settings, Automations: New automation and the ideas for this app.
1. Open Automations: In Settings, group Automation and connections, choose Automations.
2. Start one: Press New automation, or Ideas for this app to get suggestions that fit your tables. Pick the ones you want and press Add what I picked.
3. Say what it should do: Under What should it do, write it the way you would explain it to a person. Give it a Name.
4. Choose when: Under When should it run: At a set time (every few minutes, hours or days, at a day and hour, by your clock) or When something happens.
5. Create: Press Create and write it. The builder writes it as a regular build request, with the same use of credits. You can follow it in the chat.
When something happens: options |
A record is added | For example, a new lead or booking.
A record changes | For example, a booking status becomes cancelled.
A record is deleted |
A user signs up | Someone signs up to your app.
An event automation starts within seconds of the event, in the table you choose.
Daily leads report: "Send me an email every morning with all the leads that came in yesterday: name, phone and what they asked for."
Class reminder: "Every day at 18:00, send a reminder email to everyone booked for a class tomorrow, with the class time and teacher."
Weekly unpaid list: "Every Sunday at 8:00, email me a list of members whose payment status is unpaid, with name, phone and amount."
Welcome a new sign-up: "When a user signs up, send them a welcome email with our address, opening hours and a link to book a first class."
Clean old test data: "Every day at 3:00, delete leads older than 30 days whose name contains the word test."
You see | What it means and what to do
The test failed. | The automation has a problem. Open its history to read why, then use Change what it does and write the fix in plain words, for example "the email field is called email_address".
The automation failed. The reason is in its history. | A real run failed. Open Latest runs to read the reason.
Paused: it ran more than 30 times in one minute. An automation that changes the record that started it starts itself again. Change what it does, then turn it back on. | An automation that runs when a record changes, and itself changes that record, started a loop. The platform paused it. Ask to change only other fields, or to run on new records only, then turn it on.
We could not update the automation. | The change was not saved. Try again in a moment.
Automations are part of the Photon plan and above. | Your plan does not include automations. See Plans and billing.
Plan: Automations are part of the Photon plan and above. See Plans and billing.
Messages to you or to customers: For a quick note to yourself on each new record, Notifications are simpler. For agents that follow up customers, see Agent tasks.
Q: It ran but nothing happened.
A: Open its history to see the result, and use Test to run it once with the newest record.
Q: Which time zone does it use?
A: Your own clock; the screen shows the zone next to the hour.
Q: Why is one under Run only when you start them?
A: It waits for an event the platform does not fire, so it runs only when you press Run.
Q: Is there a data backup automation?
A: Saved versions keep your records with every change. See Saved versions.
Related: Studio settings, section by section, Tasks and schedules, The database: tables and records, Credits basics, Saved versions and restore