A workflow is a rule that runs without you: when something happens, do this, then that. Salesive's builder has four trigger types and enough actions to cover order updates, customer messages, content publishing and internal tasks. These ten are the ones most Nigerian stores can run in their first week.

How does the workflow builder work?

There are four triggers: a store event, an incoming webhook, a schedule and a manual run. A store event is something happening in your shop, such as a new order or a status change. An incoming webhook lets another system start the workflow. A schedule runs on a cron, so it can fire every morning or every Monday. A manual run is a button you press.

Actions include WhatsApp messages, images, buttons and typing indicators, chat messages, email to the customer and to the owner, push notifications, order status updates, product, menu, service, blog and coupon updates, customer tags and updates, task and note creation, HTTP calls, AI agent steps, memory read and write, record lookups, Telegram steps, LinkedIn publishing and lookups, and TikTok steps and lookups.

Trigger-level filters let a workflow run only when the event matches, for example only when an order is above a certain value. Before and after operations let you do work around the main action, and the variable catalog lets you drop order, customer and product values into a message without guessing the field names.

The ten workflows

1. Order confirmation. Trigger on a new order, send a WhatsApp message to the customer and an email to the owner. Include the order number and the items from the variable catalog. This is the workflow to build first, because it removes the most common 'did you get my order' message.

2. Large order alert. Trigger on a new order with a filter on the order total, then send a push notification and an email to the owner. A store that mostly sells small items still needs to know immediately when a big one lands, and a filter keeps the alert meaningful instead of noisy.

3. Delivery status update. Trigger when an order status changes, then send a WhatsApp message with an image and a short note about what happens next. A customer who knows the parcel has left the shop is much less likely to message you asking whether it has.

4. New product announcement. Trigger on a product update or run it manually when you launch, then send a WhatsApp message and a chat message. Use the product name and price from the variable catalog so the announcement does not go out with the wrong details.

5. Weekly owner summary. Run on a schedule every Monday morning, look up the week's records and email the summary to the owner. It is a small habit that turns the dashboard into a weekly review instead of something you open only when there is a problem.

6. First purchase welcome. Trigger on a new customer or a first order, tag the customer and send a welcome message. The tag is the useful part: it lets you find first-time buyers later for a follow-up, a coupon or a check-in without exporting anything.

7. Review request after delivery. Trigger when an order is marked delivered, then send a WhatsApp or email message asking for a review. Keep it short and send it once. A request that arrives a day after delivery feels like service; one that arrives a week later feels like marketing.

8. Stale paid order task. Run on a schedule, look up orders that are paid but not fulfilled, and create a task for the team. This is the workflow that catches the order someone forgot to pack, and it is worth more than most dashboards because it acts instead of reporting.

9. Blog publish cross-post. Trigger when a blog post is published, then publish to LinkedIn and send a Telegram message. Content that only lives on the store gets read once. A cross-post workflow makes every article do a second job without anyone remembering to share it.

10. Partner webhook intake. Use an incoming webhook as the trigger, make an HTTP call to your supplier or logistics partner, and create a task or note with the result. This is how a store connects a system that Salesive does not integrate with directly, without waiting for an app.

How do you build one without breaking it?

Start with the trigger and the filter, then add one action. Run it manually and read the result before you add the next step. Most broken workflows are not broken because the logic is hard; they are broken because someone built ten steps at once and could not tell which one failed.

Use the variable catalog rather than typing field names from memory. It is the difference between a message that says 'Hello {{customer.name}}' and one that says 'Hello {{customer.nmae}}' to a thousand people. Test with a real order, not a made-up one, so the values are the same shape as production.

Should you start from a template?

Yes, if there is one that fits. The templates marketplace has official and community templates, and starting from a working example is faster than starting from an empty canvas. Read the template before you enable it, though. A template built for a restaurant may have steps that make no sense for a digital store.

Ola can build, test and debug a workflow as well. That is useful when you know the outcome you want but not the exact sequence of actions. Describe the rule, let her assemble it, then read what she built before you turn it on.

How do test runs count?

Test runs count against a usage meter. That is fair, because a test run does the same work as a live run, but it changes how you should test. Decide what you are checking before you press run. One deliberate test with a real order is worth ten runs against an empty payload.

What is not native?

Abandoned cart recovery is not a native Salesive workflow. That job belongs to the Recart app. The builder can do a lot, but it is honest to say where the boundary is rather than promising a recovery flow that the platform does not run itself.

The same applies to channels and actions outside the list. If a workflow needs a service that is not in the action list, the answer is usually an incoming webhook plus an HTTP call, or an app.

The best workflow is the one that removes a message you were tired of answering.

Frequently asked questions

Do I need to write code to build a workflow?

No. You choose a trigger, add actions and set filters in the builder. The variable catalog gives you the order, customer and product values without writing expressions. HTTP calls and webhooks are there if you want them, but they are not required.

Can Ola build a workflow for me?

Yes. Ola can build, test and debug a workflow. Describe the rule you want, then read what she assembled before you enable it. Test runs count against a usage meter, so test with a clear question in mind.

Do test runs cost anything?

Test runs count against a usage meter. A test does the same work as a live run, so it is counted the same way. Test deliberately rather than repeatedly.

Can a workflow run on a schedule?

Yes. The schedule trigger uses a cron, so a workflow can run every morning, every Monday or at any interval you set. That is how the weekly summary and the stale order task work.

Does Salesive recover abandoned carts natively?

No. Abandoned cart recovery is handled by the Recart app, not by a native workflow. The builder covers order updates, messages, content, tasks and webhooks, but cart recovery is a separate product.

Start with one workflow, not ten. Order confirmation is the obvious first one, because it removes a question you answer every day. Add the large order alert, then the delivery update, and let the rest wait until the first three are running cleanly. If you want help building them, read what Ola can actually do in your dashboard and how Ola replies to WhatsApp, Instagram and Telegram DMs. For the platform, see features and pricing, or browse the Salesive blog.