Build event and scheduled workflows with tasks, approvals and branches, then connect your own print, email and HTTPS services.
Build workflows that react to store events or run on a schedule, with typed conditions, staff tasks, approvals and waits. Test a draft without side effects, publish a fixed revision and find every run in its history. Connect your own PrintNode, SMTP and HTTPS accounts for print, email and web requests.
Twelve templates cover paid orders to picking sheets, collection tasks, high-value approvals, low stock, receipt labels, return finance tasks and more. Templates that depend on another product stay disabled until it is installed.
Declare event fields with types such as money, quantity, timestamp and list. Group conditions as all or any, and send missing data down its own review path.
Arrange steps with true, false and unavailable branches. Add staff tasks, role-based approvals, timers and waits for a matching event.
Check a draft against typed sample values without sending requests or creating tasks. Publishing saves a fixed revision, and runs already waiting keep the revision that started them.
Schedule a published workflow at a local time in your timezone and preview the next five runs. Skipped and repeated clock times follow the rule you choose, and missed runs catch up once.
Save PrintNode, SMTP or HTTPS credentials privately and verify each connection before use. Acceptance by a provider is recorded separately from physical printing or delivery to the recipient.
When payment is confirmed, the template checks the delivery method. Collection orders create a staff task, delivery orders produce a picking sheet PDF that can print to an approved printer, and missing data creates a review task. The sheet reminds staff to check the current order before fulfilment.
A high-value order above your threshold pauses for an Administrator approval that expires after 24 hours. The decision records who approved, why and against which revision. Edits made to the workflow after the run started do not change what that approver reviewed.
Screens from the Botble edition, using sample data. Explore the features and requirements below.
Screenshots and interactive demos are coming soon. Product features and setup requirements are listed below.
WooCommerce screenshots are being prepared. The screenshots under Botble show that edition with sample data.
Start from a template or a blank draft, declare the event fields and set the store scope.
Add conditions, branches, tasks and approvals, then test the draft with sample values.
Publish the revision, work through staff tasks and approvals, and find completed runs in the history.
These details describe the Botble edition. Check the platform, services and equipment your shop uses.
Native WooCommerce edition.
Every plan has the same features. Pick the term that suits your business, or buy a perpetual licence and keep it.
GBP reference prices, including applicable VAT/sales tax. Stripe confirms available local-currency pricing before payment. Local currency estimates use current Stripe FX quotes.
Plugin, updates and support — one monthly price
Launch price · save 20%a month
For new customers after the offer: £24 a monthYour rate stays while your subscription remains active
Plugin, updates and support — one yearly price
Launch price · save 20%a year
For new customers after the offer: £240 a yearSame purchased rate on uninterrupted renewals
Yours to keep
Launch price · save 21%once
£699 after the offer
Perpetual licences include 12 months of updates and support. After that, extend them a year at a time for £120 a year, whenever you like, even before the current year ends. Monthly and yearly plans always include updates and support.
Prices include applicable VAT/sales tax. One plugin and one platform edition per licence.
Marketplace, hosting, hardware and external API charges are separate. No payment processing surcharge. See how licensing works →
The workflow, its limits and what is separate.
Still need a hand?Only through supported actions in installed operations products, such as a purchase-order draft or a refund request, and each needs its own approval of the exact inputs in that run. Workflows never sends money.
PrintNode acceptance means the request reached your account, and client-reported completion means it reached the computer's print queue. Check the paper at the printer. A reprint needs its own review.
A repeated event reference does not start a second run, and business actions are checked for duplicates. If a provider result is uncertain, the step waits for review rather than sending again.
Full run detail is kept for 30 days and summaries for 12 months. Event and business keys continue to block duplicate work after the detail expires.
Cookie preferences
