The jobs that should just happen, happening.
Automations does the small reliable things you would otherwise do by memory: the follow-up two days later, the low-stock warning, the tag on a customer who bought twice, the reminder before the appointment.
- Free for 14 days
- No card needed
- All sixteen apps included
- When this, then that
- Wait, then check again
- Start from a working example
- See what it did
- Edit without breaking it
- Off is one click
All of it, in the $99 plan, from your first day.
Most software calls this workflow automation. In Piggles it is called Automations, because that is what you are actually doing.
- marketing automation
- triggers and actions
What Automations does
When this, then that
Built from things that already happen in your business: an order paid, a booking made, stock below a level, a quote gone quiet.
Wait, then check again
Steps can pause for a day or a week and then confirm the situation still applies, so nobody gets chased for something they already did.
Start from a working example
A set of ready-made ones for the common jobs. Turn one on, change the wording, done.
See what it did
Every run is listed with what it acted on and what it changed. An automation you cannot inspect is one you will not trust.
Edit without breaking it
Changes wait as a draft until you publish them. The running version keeps going, and every earlier version is kept to go back to.
Off is one click
Pause anything immediately, without deleting it and rebuilding it later.
Start with the ones that already work.
You should not have to invent an automation to get something out of one. The recipe library arranges the ready-made ones by what they are for, such as getting paid or winning back a quiet customer, and each has a plain on and off switch. Which ones you see depends on the apps you use: a business with no online shop is not shown cart reminders.
- Arranged by what you want
- Welcome new customers, recover lost sales, keep customers coming back, reward loyalty, get paid on time, keep customers in the loop, stay on top of things, and grow your audience.
- Getting paid, handled
- A reminder before an invoice is due, notices at a week, two weeks and a month late, and a receipt when it is paid.
- The sale that nearly got away
- A reminder about a cart somebody left behind, a nudge to retry a payment that failed, and one before a quote runs out.
- After the sale
- Tell customers their order arrived, confirm a refund or a return, and ask the happy ones for a review.
- Things you should hear about
- An alert for a big order, stock running low, something selling out, or a chat nobody has answered.
- An ordinary automation underneath
- Open any of them to change the timing, the conditions or the steps. Nothing about a ready-made one is locked away from you.
Built from what already happens in your business.
Every automation starts from a moment: something that just happened, or a check that runs on a clock. The moments come from across the business (selling, customers, bookings, invoices, your team, your site and your campaigns), and each one carries the details you would expect to be able to test.
- When something happens
- An order is paid, a form on your site is filled in, somebody books or misses an appointment, a support request is running out of time, a team member’s license is about to expire.
- Or on a clock
- Every day, week or month, every so many minutes, or once at a set time, looking over your customers, invoices, quotes awaiting a decision, abandoned carts or chat conversations.
- Only when it applies
- Add conditions in plain words, such as is more than, is one of or is empty. "Order total is more than 500" works the way it reads.
- The details you invented
- If you keep a renewal date or a warranty expiry on your customers, an automation can start when that detail changes and act on it.
- Only the steps you can use
- Steps belonging to apps you have not added are left out of the list, so what you choose from is about your business.
Steps that wait, check, and choose.
Most useful jobs are not one action. They are "wait two days, see whether they paid, and only then send the reminder." Automations lays out steps one after another, with pauses and forks, and looks at the record again at every step, so nobody is chased for something they have already done.
- Wait a while
- Pause for an hour, a day or a week before the next step.
- Go one way or the other
- Ask a question about the record, then do one thing if the answer is yes and something else if it is no.
- Fresh at every step
- Details are looked up again at each step rather than remembered from the start, so a customer who paid yesterday is not treated as unpaid today.
- Stop once it has worked
- Say what you are aiming for, such as a booking or a payment. When it happens for someone, the remaining steps stop for them and they count as a success.
- What a step can do
- Label a customer, add a note, change a detail, create a task or a record, open a support request, share work evenly across the team, put someone on a list, write to them personally, start or stop an email sequence, email your staff, post a notice for your team, or draft a social post for you to approve.
- Hand the details to other software
- Send what happened to another tool you use, at a web address that tool gives you.
- Words that fill themselves in
- Write "Hi {{customer.firstName}}" and each customer’s own name goes in when it sends.
You can see what it did, and why.
An automation you cannot look inside is one you will quietly switch off. Every run is kept with each step it took, and a rule that keeps failing says so on the list instead of sitting there switched on and looking fine.
- Every run, step by step
- What started it, which steps ran, what each one changed, and where it stopped if it did.
- Failing is not the same as on
- A rule whose runs are failing is flagged on the list and on its own page, with the failures one click away.
- Where people drop out
- For a rule with an aim: how many started, how many got there, how long it took them, and the step where most people fell away.
- Activity across all of them
- How many runs there were and how many succeeded, for the period you pick. Open two side by side to compare one month with another.
Change it without breaking it.
Editing something that is already running is how a business ends up sending the wrong email to four hundred people. Changes to a live automation wait as a draft until you publish them, and every version you publish is kept.
- Draft, then publish
- Edit freely. The running version keeps going until you publish, and a draft you do not like can be thrown away.
- Every version kept
- See what changed and when, with a note on why, and go back to an earlier version if the new one is worse.
- Pause without losing it
- Switch one off and back on again, with its steps and history intact.
- Copy one to start another
- Duplicate an automation that works and change only the parts that differ.
Works with the rest of it
Nothing here is a separate product that has been made to talk to the others. They are the same business, looked at from different angles.
Running it also includes My Team and Connections.
