Automation lab
See how a workflow actually fits together
Each example below is drawn the way we build it: what starts it, what happens in between, where a decision is made, and what comes out the other end.
Simulated examples, real architecture
These diagrams are illustrations, not live systems running in your browser — nothing here sends a message, charges a card or touches a marketplace. One exception is marked: the website lead flow is the workflow this site runs when you submit the quote builder.
- Trigger
- Process
- Decision
- Action
- Output
Worked examples
Six workflows, end to end
Website lead to follow-up
A quote request is validated, stored, acknowledged to the customer and pushed to sales with attribution attached.
- Trigger
Estimate submitted
A visitor completes the quote builder or the contact form.
- Process
Validate and score
Input is validated server-side, spam checks run, and the submission is de-duplicated with an idempotency key.
- Decision
Marketing consent given?
Consent is recorded either way and drives whether the contact joins the marketing list.
Yes → subscribe · No → transactional only
- Action
Store the lead
Lead, quote, line items, attribution and consent are written to the database in one transaction.
- Action
Notify sales and the customer
The customer gets their estimate by email; sales gets an internal notification with the lead reference.
- Output
Lead ready in admin
The lead appears in the admin area with its estimate snapshot, email delivery status and source, ready for follow-up.
This is the flow running on this website. Submitting the quote builder triggers exactly these steps.
WhatsApp enquiry to human handoff
An enquiry arriving on WhatsApp is qualified with a few structured questions, then handed to a person with the context attached.
- Trigger
Message received
A customer messages the business number, or taps a click-to-WhatsApp link on the website.
- Process
Qualify
The assistant asks what the customer needs, the rough scope and their preferred contact time.
- Decision
Enough detail to route?
Complete enquiries route straight to the right person; thin ones get one more question.
Yes → route · No → ask again
- Action
Create the lead
The enquiry is written into the same lead database the website uses, tagged with WhatsApp as its source.
- Action
Alert the team
Staff are notified with the conversation summary so nobody restarts the conversation from scratch.
- Output
Human takes over
A person continues the chat in the shared inbox with the full history in front of them.
Runs on the official WhatsApp Business Platform. Templates, opt-in and session rules are set by WhatsApp and must be approved before launch.
Marketplace order to daily summary
An order pulled from the marketplace API moves through operations, supplier workflow, finance records and a daily summary.
- Trigger
Order notification
A new order arrives through the marketplace API notification, or is picked up by a scheduled sync.
- Process
Normalise the data
Order, item, buyer-region and fee data are normalised into the operations schema for one or more seller accounts.
- Decision
Stock available?
In-stock orders continue; short stock raises a supplier or restock task instead of failing silently.
Yes → fulfil · No → supplier task
- Action
Update the dashboard
The operations dashboard shows the order against products, suppliers and current inventory.
- Action
Record the finance entry
Settlement and fee data are attached to the order so margin is calculated from real figures.
- Output
Daily summary
Orders, exceptions and finance movements are summarised for the team on a schedule.
Modelled on the Seller Operations Platform architecture. Marketplace access depends on the seller account and the API permissions it is granted.
Content approval to social reporting
Prepared content goes through an approval step, gets scheduled, publishes through the official API, and reports back engagement.
- Trigger
Content prepared
A post, caption and asset are drafted in the content queue.
- Process
Check the asset
Media format, aspect ratio, caption length and required tags are checked before anything is queued.
- Decision
Approved to publish?
An approver signs the post off; rejected posts return to the queue with a comment.
Approved → schedule · Rejected → back to draft
- Action
Schedule the post
The post is queued for its publish time, with retries if the platform rejects the first attempt.
- Action
Publish through the API
The post is published through the official Meta endpoints for the connected account.
- Output
Engagement reporting
Published posts and their engagement data flow into a reporting dashboard.
Publishing uses the official Meta APIs. What is possible depends on the account type, granted permissions and Meta's app review.
Payment to confirmed record
A gateway webhook confirms the payment, updates the order, notifies the customer and writes the internal record once.
- Trigger
Customer pays
The customer completes checkout or pays through a payment link.
- Process
Verify the webhook
The gateway callback is checked against its signature before anything is trusted or written.
- Decision
Payment confirmed?
Confirmed payments continue; failed or pending ones are recorded and surfaced rather than dropped.
Paid → continue · Failed → flag
- Action
Update the order
The order status is updated once, with repeat callbacks ignored through an idempotency key.
- Action
Notify the customer
The customer receives confirmation with their receipt or invoice reference.
- Output
Internal record
The finance record and payment status dashboard are updated for reconciliation.
Works with the gateway's official webhooks. Signature verification and idempotency are part of the build, not an add-on.
Support request with AI assistance
An AI assistant answers from approved business content and escalates to a person when it is not confident or the request is sensitive.
- Trigger
Support request
A customer asks a question on the website, in chat or by email.
- Process
Search approved content
The question is matched against your documented answers, product data and policies.
- Decision
Confident, and allowed to answer?
Billing, account and complaint topics can be routed straight to a person regardless of confidence.
Yes → answer · No → escalate
- Action
Answer with sources
The customer gets an answer drawn from the approved content, with the source it came from.
- Action
Escalate with context
Anything uncertain or sensitive goes to a person with the conversation and the suggested answer attached.
- Output
Logged for review
Questions, answers and escalations are logged so gaps in the content can be fixed.
The assistant answers from your own approved content. Escalation rules, tone and the topics it must not answer are set by the business.
Want one of these mapped to your business?
Describe the process you run by hand and we will draw the workflow back to you, with the integrations it needs.