Automation
Business Automation Built Around Real Workflows.
Automation is only useful when it follows how the business actually works. We map the steps people repeat by hand, then connect the websites, apps, marketplaces, messaging, payments and data behind them so the work moves on its own.
What we automate
Ten places automation usually pays off
Lead automation
Capture, validate, store, notify and follow up, with the source of every lead recorded.
See the flowWhatsApp automation
Enquiries, confirmations, reminders and alerts on the official WhatsApp Business Platform.
See the flowE-commerce automation
Product, stock, pricing and customer workflows across your store and sales channels.
Order automation
Orders moving from the sales channel into fulfilment, supplier tasks and internal records.
See the flowPayment workflows
Verified gateway callbacks updating orders, receipts, invoices and finance records once.
See the flowSocial media workflows
Content queues, approval steps, scheduled publishing and engagement reporting.
See the flowReporting automation
Scheduled summaries and dashboards built from your own operational data.
Internal business workflows
Approvals, task routing, notifications and handovers between the people who do the work.
API-driven automation
Systems talking to each other through official APIs, with retries, logging and idempotency.
AI-assisted workflows
Assistants that draft, classify, summarise or route, with a person kept in the loop.
See the flowEvery integration is built against the platform's official API, with credentials held server-side.
Proof, not a mock-up
A workflow running on this website
The quote builder on this site runs the flow below: validated, stored, acknowledged and notified, with the source of the lead recorded. It is the same shape of workflow we build for clients.
- Trigger
- Process
- Decision
- Action
- Output
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.
Messaging
WhatsApp Business Automation
Messaging workflows built on the official WhatsApp Business Platform: enquiries answered quickly, confirmations sent automatically, and a clean handoff to a person when the conversation needs one.
Built on the official WhatsApp Business Platform. Message templates, customer opt-in and messaging windows are governed by WhatsApp's own rules and need approval before launch. We do not build unofficial or unapproved WhatsApp automation.
- Website lead → WhatsApp notification → qualification → staff alert → human handoff
- Order received → customer confirmation → internal notification
- Booking → confirmation → reminder
- Payment → confirmation → receipt or status update
- Support enquiry → automated answers to common questions → human escalation
- Click-to-WhatsApp entry points from the website, with the conversation recorded as a lead
WhatsApp enquiry to human handoff
- 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.
Social
Meta & Social Automation
Content and reporting workflows for Instagram and Facebook built on the official Meta APIs, with an approval step before anything reaches an audience.
Features depend on Meta account type, API permissions and platform approval. We are not a Meta partner and claim no partner status.
- Instagram publishing workflows through the official API
- Scheduled posting from a content queue
- Content approval before publishing
- Social reporting and engagement dashboards
- Lead workflows from social campaigns into the lead database
- Messaging integration where the account's permissions allow it
Content approval to social reporting
- 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.
Marketplaces
Marketplace & Amazon Seller Integrations
Marketplace data pulled through official seller APIs into operational dashboards: orders, listings, inventory and finance in one place instead of several exports.
Access depends on the seller account and the API permissions it has been granted. We are not an Amazon partner and hold no Amazon certification.
- Amazon SP-API integration
- Order data and order workflows
- Listing and catalogue data
- Inventory and restock signals
- Finance, fee and settlement data
- Seller dashboards built on that data
- Multi-account architecture
- Notifications for the events that matter
- Operational and daily summary reporting
Marketplace order to 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.
Payments
Payment & Checkout Integrations
Checkout and payment workflows wired to the gateway's official API, with signature-verified webhooks so a payment updates your systems exactly once.
Available features depend on your payment provider, your account and the region you operate in. We are not affiliated with, or endorsed by, any payment provider.
- Payment gateway setup and checkout integration
- Payment links for invoices and one-off charges
- Subscription and recurring payment flows
- Webhook confirmation with signature verification
- Invoice and receipt workflows
- Payment status dashboards
- Reconciliation workflows against settlement data
- Refund status integration
Payment to confirmed record
- 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.
Maps & location
Google Business & Location Integrations
Location features for businesses with physical premises: finding the nearest store, getting there, and keeping location data consistent across your site.
Map and location features depend on Google API access, billing and quota on your own Google account. We are not a Google partner.
- Google Maps integration
- Store and location finder
- Address capture, validation and autocomplete workflows
- Directions and travel links
- Location search and filtering
- Google Business Profile-related integrations where API access allows
- Business and location data workflows
Assistants
Custom Bots & Business Assistants
Assistants built around one job and connected to the systems that hold the answer, rather than a generic chat window bolted onto a page.
Customer support bot
Answers common questions from your approved content and escalates the rest.
Sales qualification bot
Asks the questions your sales team would ask, then creates the lead.
Internal staff assistant
Gives staff answers from internal documentation and process notes.
Product enquiry bot
Answers questions about products, stock and specifications.
E-commerce assistant
Helps a customer find, compare and track what they bought.
Reporting bot
Delivers scheduled or on-demand summaries from your own data.
Workflow assistant
Moves a task through approvals and notifies whoever is next.
Knowledge assistant
Searches your documents and answers with the source attached.
Where a bot can connect
Website
Embedded in the site, like the assistant on this page.
WhatsApp
Through the official WhatsApp Business Platform.
APIs
Reading and writing through the systems you already run.
Databases
Answering from your operational data, with access scoped server-side.
Business workflows
Triggering the same automated steps a person would.
Channel availability depends on each platform's permissions and approval process.
Integrations
Connect the Tools Your Business Uses.
We integrate through official APIs. Where a platform requires approval, that is part of the project plan rather than an afterthought.
Marketplaces
- Amazon SP-API
- Seller dashboards
- Order and listing data
Messaging
- WhatsApp Business Platform
- Email notifications
- Internal alerts
Social
- Instagram publishing
- Facebook pages
- Engagement reporting
Payments
- Gateway checkout
- Payment links
- Webhooks and reconciliation
Maps & location
- Google Maps
- Store locator
- Address workflows
- Transactional email
- Delivery and bounce handling
- Marketing consent
Databases
- MySQL / MariaDB
- Operational schemas
- Reporting views
Analytics
- GA4
- Conversion tracking
- Consent-aware tracking
AI
- Assistants
- Classification
- Summarisation
Custom APIs
- REST integrations
- Webhooks
- Scheduled syncs
How we build integrations
Credentials stay on the server
Server-side secrets
API keys, tokens, database credentials and webhook secrets live in server environment variables. They are never shipped to the browser or committed to the repository.
Signature validation
Incoming webhooks are verified against the sender's signature or shared secret before anything is trusted.
Rate limiting
Public endpoints are rate limited per client to absorb abuse and accidental retries.
Input validation
Every payload is validated server-side against a schema, regardless of what the client sent.
Idempotency
Repeated callbacks and double submissions are de-duplicated so an order or payment is recorded once.
Logging
Integration failures are logged with enough context to diagnose them, and without recording secrets.
Which part of your work is still manual?
Tell us the steps your team repeats by hand. We will map the workflow and tell you what can be automated with the platforms you already use.