Business Automation Examples That Save Time Every Week

How it works

1. 1Job Completed Webhook
2. 2New Review Webhook
3. 3Wait 1 Day (1 days)
4. 4AI Draft Review Response (AI chain)
5. 5SMS Review Request
6. 6Send Draft to Owner (send email)
7. 7Email Review Request (send email)
8. 8Log Review + Draft (append)
9. 9Log Request Sent (append)

How it works

1. 1Monthly on the 1st, 10am (schedule)
2. 2Read Customer List
3. 3Filter Inactive 60+ Days (code)
4. 4Anyone to Win Back? (if)
5. 5AI Personalized Offer (AI chain)
6. 6Nobody Lapsed: Skip (no-op)
7. 7Email: We Miss You (send email)
8. 8SMS: Offer Nudge
9. 9Log Campaign Send (append)

How it works

1. 1Owner fills the "Find Prospects" form (business type, area, how many).
2. 2Google Places Text Search returns matching businesses.
3. 3"Shape Results" maps name, address, rating and place_id.
4. 4Filter keeps weak-presence targets (rating under 4.3).
5. 5Prospects are appended to the Prospects sheet.
6. 6Owner gets an email that fresh prospects are ready.

How it works

1. 1Meta sends each new comment to the comment-keyword webhook.
2. 2"Map Comment" pulls out commenter name, comment text and post ID.
3. 3Filter keeps only comments containing the keyword (GUIDE, any case).
4. 4A private reply DM with the link goes to the commenter.
5. 5The comment gets a like and a short public reply.
6. 6Every fulfilment is logged to a sheet.

How it works

1. 1Owner fills "Launch a Promo" (segment, offer headline, details, code, expiry).
2. 2Customers are read from the sheet.
3. 3Switch routes by segment: All pass through, VIPs and Lapsed hit their own filter.
4. 4VIP filter keeps totalSpend of RM1000+; Lapsed filter keeps lastVisit older than 60 days.
5. 5Merge brings the chosen segment back together.
6. 6AI writes the promo email from the offer brief, one clear CTA.
7. 7Each customer gets the promo email; the campaign is logged.

How it works

1. 1Runs daily at 9am
2. 2Reads the customer list
3. 3A visual filter keeps only people whose birthday (MM-dd) is today
4. 4Sends the birthday email + SMS with the gift code, logs it

How it works

1. 1Someone registers on the hosted form
2. 2Saved to the attendee list + instant confirmation with calendar link
3. 3Day-before reminder email
4. 4After the event: replay link + the offer made during the session

How it works

1. 1Runs every day at 8am.
2. 2Pulls yesterday's spend and conversions from Meta Ads Insights.
3. 3"Map Spend Fields" shapes the numbers.
4. 4IF conversions are zero AND spend is RM50 or more: WhatsApp the owner, then email the details.
5. 5Otherwise a quiet "Ads healthy" path.
6. 6Either way, the day's spend is logged to a sheet.

How it works

1. 1Friday 4pm schedule fires once a week.
2. 2Reads every row from the Reviews Log sheet (all platforms in one tab).
3. 3Maps raw columns to clean fields (platform, rating, date, text).
4. 4Filters to reviews left in the last 7 days.
5. 5Counts and averages ratings split by platform.
6. 6Limits to one item so a single report is produced.
7. 7AI writes the summary as labeled lines (AVERAGE_SCORE, BEST_QUOTE, WORST_ISSUE, ONE_ACTION) using gpt-4o-mini.
8. 8Emails the owner the full report.
9. 9Appends the report to the Report History tab for a running record.

How it works

1. 1Owner fills the ad brief form (product, audience, offer, platform)
2. 2AI step 1: writes 5 genuinely different hooks (pain, dream, proof, curiosity, offer-led)
3. 3AI step 2: expands each hook into a complete ad
4. 4Variants saved to the swipe sheet + emailed for review

How it works

1. 1Monday 9am schedule fires weekly.
2. 2Fetches the search-terms report from the Google Ads API (placeholder customer ID).
3. 3Shapes the raw rows into one clean term | clicks | cost | conversions block.
4. 4AI reviews the terms and flags irrelevant ones as labeled lines (NEGATIVES, WASTED_SPEND, KEEP_AN_EYE_ON, SUMMARY).
5. 5gpt-4o-mini powers the review step.
6. 6Extracts the negative list and waste estimate into clean fields.
7. 7Emails the owner the wasted-spend terms with the paste-ready list.
8. 8Appends the suggestions to the Negative Keyword Log sheet.

How it works

1. 1Monday 7am schedule fires weekly.
2. 2Reads the Keywords tab (keyword + targetUrl per row).
3. 3Runs a live SERP check per keyword via the SerpAPI endpoint (placeholder key).
4. 4Extracts the position of the client's URL from the organic results, stamped with today's date.
5. 5Appends every keyword's position to the Rank History tab, the long-term trend line.
6. 6Checks whether the position is 11 or worse (off page 1).
7. 7If slipped: emails the owner naming the keyword and the new position.
8. 8If still on page 1: ends quietly with no noise.

How it works

1. 1Wednesday 9am schedule fires weekly.
2. 2Searches the Meta Ad Library for the competitor's page (placeholder page ID + token).
3. 3Shapes the newest 25 ads into one clean text block (creative body, start date, platforms).
4. 4AI answers "what are they testing?" as five labeled lines (ANGLES, OFFERS, HOOKS, TREND, ACTION).
5. 5gpt-4o-mini powers the analysis step.
6. 6Extracts the labeled lines into clean fields for the email and the log.
7. 7Emails the owner the competitor ad intel note.
8. 8Appends the snapshot to the Ad Intel Log so you can see their strategy shift over months.

How it works

1. 1Monthly schedule fires on the 1st at 9am.
2. 2Reads the full Subscribers sheet (email, name, lastOpened).
3. 3Maps the raw columns to clean fields.
4. 4Filters to subscribers whose lastOpened is more than 120 days ago.
5. 5Sends each inactive subscriber the re-permission email with a one-click stay link.
6. 6Appends every contacted subscriber to the Sunset List tab.
7. 7Counts the batch so one summary line exists.
8. 8Emails the owner how many are sunsetting this month.

How it works

1. 1Google Alerts RSS feed is polled every hour
2. 2Each new mention triggers the flow
3. 3AI assesses sentiment + drafts a suggested reply or action
4. 4Digest emailed to the owner; every mention logged

How it works

1. 1Daily 7am schedule checks the calendar every morning.
2. 2Reads the Campaign Calendar sheet (holidayName, sendDate, offer, audience).
3. 3Filters to rows whose sendDate equals today. Most days nothing matches and it ends quietly.
4. 4AI writes the holiday email from the offer brief as labeled lines (SUBJECT + BODY), festive but offer-led.
5. 5gpt-4o-mini powers the writing step.
6. 6Extracts the subject and body into clean fields, carrying the audience along.
7. 7Sends the campaign to the audience list address.
8. 8Appends the send to the Send Log tab with date and holiday name.

How it works

1. 1"Scrape a Directory" form collects the URL and an extraction brief.
2. 2Maps the form answers to clean fields (directoryUrl, extractBrief).
3. 3Fetches the directory page HTML.
4. 4AI extracts the business listings from the page text as name | phone | detail lines, guided by your brief.
5. 5gpt-4o-mini powers the extraction step.
6. 6Shapes the result into sheet-ready fields (source, listings, date). Tune the split per directory here.
7. 7Appends the rows to the Prospects sheet.
8. 8Emails the owner a done summary with the listing count.

How it works

1. 1Monday 8:30am schedule fires weekly.
2. 2Pulls a GA4 runReport by sessionCampaignName: sessions + conversions, last 7 days.
3. 3Shapes the API rows into one clean campaign | sessions | conversions block.
4. 4AI judges which campaigns earned their keep, as labeled lines (WINNERS, LOSERS, REALLOCATION_TIP, SUMMARY).
5. 5gpt-4o-mini powers the judging step.
6. 6Extracts the verdict lines into clean fields for the email and the log.
7. 7Emails the owner the digest.
8. 8Appends the digest to the Campaign Digest Log for a season-over-season record.

How it works

1. 1Webhook visitor-identified receives the identification event from the visitor tool.
2. 2Maps the payload to clean fields (companyName, domain, pagesViewed).
3. 3Filters to engaged visits only: 3 or more pages viewed.
4. 4AI writes a one-line account brief (who they are plus their likely interest) from the company name, domain and pages viewed.
5. 5gpt-4o-mini powers the brief step.
6. 6Extracts the brief line into a clean field, carrying the company details along.
7. 7WhatsApps the owner: company name plus the one-line brief, in seconds.
8. 8Appends the visit to the Visit Log sheet so sales can follow up with context.

How it works

1. 1Webhook partner-referral receives the referral (partner form or UTM landing page).
2. 2Maps the payload to clean fields (partnerName, partnerEmail, leadName, leadEmail).
3. 3Stamps a unique reference ID and received-at time onto the referral.
4. 4Responds to the submitting form instantly so the partner sees success.
5. 5Appends the full referral to the Referral Ledger sheet, the single source of truth for payouts.
6. 6Emails the partner: logged, reference ID included, you're credited when this closes.
7. 7Emails the owner a new-referral note with the lead's details for fast follow-up.

How it works

1. 1New Blog Post (RSS)
2. 2AI: LinkedIn Post (AI chain)
3. 3AI: Facebook Post (AI chain)
4. 4AI: Instagram Caption (AI chain)
5. 5Wait for All 3 (merge)
6. 6Package Posts (code)
7. 7Add to Posting Queue (append)
8. 8Notify: Posts Ready (send email)

How it works

1. 1Runs every Friday at 9am
2. 2Reads this week's raw inputs from the sheet (anyone on the team can add rows)
3. 3AI turns them into a friendly newsletter with subject line + intro + 3 sections + CTA
4. 4Draft emailed to the owner; approved drafts get pasted into Kit/Mailchimp

How it works

1. 1Fires Monday, Wednesday, Friday at 10am
2. 2Reads the post queue sheet
3. 3Keeps only rows marked "ready", takes just the next one (visual Limit node)
4. 4Publishes to GBP via the API, then logs it as posted

How it works

1. 1Owner submits the New Blog Post form (keyword, audience, angle)
2. 2AI writes an outline (H2s matched to search intent)
3. 3AI expands the outline into a full draft with examples
4. 4Draft is saved to the Blog Drafts sheet
5. 5Owner gets the draft by email for review

How it works

1. 1Fires every day at 9am and 3pm
2. 2Reads the Post Queue sheet (postText, platform, status)
3. 3Keeps only rows with status "ready"
4. 4Takes the next post in line
5. 5Publishes it through the scheduling API (Buffer or Postiz)
6. 6Logs the post as published

How it works

1. 1Happy Signal Webhook
2. 2Testimonial Form
3. 3Map Customer (edit fields)
4. 4Save Raw Testimonial (append)
5. 5Invite to Share a Testimonial (send email)
6. 6AI: Tidy Grammar Only (AI chain)
7. 7Send to Owner: Ready to Publish (send email)

How it works

1. 1Fires on the 25th of each month at 9am
2. 2Reads last month's results from the Post Log sheet
3. 3AI drafts next month's calendar: 12 ideas with hook, format and CTA, leaning on topics that already proved themselves
4. 4Ideas are appended to the Content Calendar sheet
5. 5Owner gets the full plan by email

How it works

1. 1Recorder / YouTube pipeline sends the transcript to the webhook
2. 2Title and transcript are mapped into clean fields
3. 3AI writes a blog article from the transcript
4. 4AI writes copy for 3 social clips (hook lines + captions)
5. 5Everything is saved to the Repurposed Content sheet
6. 6Owner gets the full package by email

How it works

1. 1Team fills the Project Wrapped form (client, problem, work done, result numbers, quote)
2. 2AI drafts the case study in a Problem → Approach → Result structure with the numbers up front
3. 3Draft is saved to the Case Studies sheet
4. 4Owner gets it by email for approval

How it works

1. 1Fires every Friday at 3pm
2. 2Reads the Enquiries sheet
3. 3Keeps only messages from the last 7 days
4. 4Combines the week into one block
5. 5AI clusters the top 5 questions and suggests 2 article titles
6. 6Extracts the ideas into clean fields
7. 7Emails the owner "what customers actually asked this week"
8. 8Maps the two article ideas into a calendar row
9. 9Appends the row to the Content Calendar sheet

How it works

1. 1Someone fills the Meta Refresh form (page URLs + brand voice notes)
2. 2The request is mapped into clean fields
3. 3AI writes a 60-character title and 155-character meta for every URL
4. 4The results are packaged with a page count and timestamp
5. 5The full list is saved to the SEO Metas sheet
6. 6The owner gets the CSV-style list by email, ready to paste into the CMS

How it works

1. 1The RSS trigger polls the industry feed every hour
2. 2Each new article is mapped into title, link and summary
3. 3AI judges whether customers would care about it, and drafts a caption
4. 4The verdict, reason and caption are extracted into clean fields
5. 5An IF node routes on the verdict
6. 6YES: the article joins the Curated Queue sheet
7. 7Then the owner gets the suggestion by email with the caption ready
8. 8NO: the article is skipped quietly

How it works

1. 1A page comment webhook posts the new comment in
2. 2Commenter, text, post link and platform are mapped into clean fields
3. 3AI drafts a helpful, human reply (max 40 words), or flags ESCALATE if hostile
4. 4The status and draft text are extracted into fields
5. 5An IF node routes on the status
6. 6ESCALATE: the owner gets a needs-a-human alert
7. 7REPLY: the owner gets the one-tap reply draft
8. 8Either way the comment and outcome are mapped into a log row
9. 9The row is appended to the Comment Log sheet

How it works

1. 1Fires every Monday at 10am
2. 2Reads the Post Log sheet (with its engagement column)
3. 3Keeps posts with 50+ engagement that ran more than 90 days ago
4. 4Limits to the single top candidate
5. 5AI rewrites the hook and freshens dated details, keeping the core idea
6. 6The refreshed post is packaged with status ready
7. 7It is appended to the Post Queue sheet
8. 8The owner gets a short note with the new hook

How it works

1. 1The recorder pipeline posts the transcript to the episode-transcript webhook
2. 2Title, transcript and guest are mapped into clean fields
3. 3AI writes the show notes: summary, timestamps, quotes and links
4. 4A second AI pass writes the YouTube description plus three title options
5. 5Both outputs are packaged with the episode title and timestamp
6. 6The package is saved to the Episodes sheet
7. 7The owner gets the full package by email, ready to paste

How it works

1. 1Fires every morning at 8am
2. 2Fetches the Google Trends RSS feed for Malaysia
3. 3The raw feed is mapped into one text field
4. 4AI checks every trend against the client's niche, strictly
5. 5The verdict, angle and post idea are extracted into fields
6. 6An IF node routes on the verdict
7. 7A match: the owner gets a ride-this-trend-today email with the post idea
8. 8No match: the run ends quietly with no noise in the inbox

How it works

1. 1The author submits the form (name, email, content, platform)
2. 2The submission is mapped into clean fields
3. 3It is logged on the Approval Queue sheet
4. 4The owner gets an approve-or-decline email and the workflow pauses until the click
5. 5An IF node routes on the decision
6. 6Approved: the content is shaped into a queue row with status ready
7. 7It is appended to the Post Queue sheet
8. 8The author gets an approved confirmation
9. 9Declined: the author gets a revisions-needed note instead

How it works

1. 1Someone pastes the content into the Localize Content form
2. 2The original text and target languages are mapped into clean fields
3. 3AI translates into natural Bahasa Melayu, keeping the marketing tone
4. 4A second AI pass translates into Chinese for a Malaysian audience
5. 5All three versions are packaged together
6. 6The set is saved to the Localized Content sheet
7. 7The owner gets all versions in one email, ready to post

How it works

1. 1The mention webhook posts the new brand mention in
2. 2Username, platform, media link and caption are mapped into clean fields
3. 3Mentions without media are filtered out (nothing to repost)
4. 4The mention is banked on the UGC Library sheet
5. 5AI drafts the repost caption and the thank-you DM
6. 6Both drafts are extracted into clean fields
7. 7The owner gets a new-customer-content email with both drafts ready

How it works

1. 1Fires on the 1st of every month at 10am
2. 2Reads the Published Posts sheet (url, title, dates)
3. 3Keeps posts not updated in the last 180 days
4. 4Limits the batch to the 3 oldest candidates
5. 5AI suggests what is stale, what to add, and a new title for each
6. 6Each suggestion is packaged into a clean block
7. 7The three blocks are combined into one refresh list
8. 8The owner gets this month's refresh list by email
9. 9A log row is mapped with the month and list
10. 10The row is appended to the Refresh Log sheet

How it works

1. 1Chat Widget
2. 2Load Knowledge (run once) (manual)
3. 3Support Agent (AI agent)
4. 4Fetch Website / FAQ Content (GET)
5. 5Needs a Human? (if)
6. 6Store Docs in Knowledge Base (vector store)
7. 7Email Transcript to Team (send email)
8. 8Answered by Bot (no-op)

How it works

1. 1WhatsApp Business fires the trigger on every incoming message
2. 2Sender + message text are extracted
3. 3AI classifies: faq / order / human
4. 4Route: instant AI answer · order-status reply · human handoff (customer gets an acknowledgment, team gets the alert)

How it works

1. 1Gmail Trigger (every 5 min)
2. 2AI Classify Email (AI chain)
3. 3Parse Category (code)
4. 4Route by Category (switch)
5. 5Label as Lead (gmail)
6. 6AI Draft Support Reply (AI chain)
7. 7Label as Invoice (gmail)
8. 8Archive Spam (gmail)
9. 9WhatsApp: Hot Lead Ping (send message)
10. 10Save Draft in Gmail

How it works

1. 1Website contact form posts to the webhook
2. 2Message is mapped to clean fields
3. 3AI tries to answer from the FAQ and must declare CONFIDENT or UNSURE
4. 4Confident → answer sent to the customer. Unsure → forwarded to the team.
5. 5Both paths logged

How it works

1. 1Job Done Webhook
2. 2NPS Answer Form
3. 3Wait 3 Days
4. 4Save the Response (append)
5. 5Send the One-Question Survey (send email)
6. 6Promoter / Passive / Detractor (switch)
7. 7Ask Promoter for a Review (send email)
8. 8Thank the Passive (send email)
9. 9WhatsApp Owner: Rescue Needed (send message)

How it works

1. 1Runs every hour
2. 2Reads open tickets
3. 3Visual filter keeps only tickets older than the 4h SLA
4. 4Manager emailed per breached ticket, breach logged
5. 5If a ticket is 24h+ old, the owner also gets a WhatsApp ping

How it works

1. 1Any channel forwards the message to the webhook
2. 2Sender, channel and text are mapped into clean fields
3. 3AI labels sentiment and urgency with a short reason
4. 4Negative messages ping the owner on WhatsApp, then email the full context
5. 5Every message is logged to the sheet

How it works

1. 1New Signup Webhook
2. 2Usage-Drop Webhook (swap: analytics)
3. 3Welcome Email (Day 0) (send email)
4. 4Normalize Account Signal (edit fields)
5. 5Wait 2 Days
6. 6AI Churn-Risk Summary (AI chain)
7. 7Activation Tips (Day 2) (send email)
8. 8Slack: Churn-Risk Alert
9. 9Wait 4 More Days (4 days)
10. 10Log Risk Event (append)
11. 11Case Study + Upgrade (Day 6) (send email)

How it works

1. 1New ticket arrives at the webhook
2. 2Subject, sender and description are mapped into clean fields
3. 3AI writes a 2-line summary, a P1-P3 priority and a suggested first reply
4. 4The priority is extracted into its own field
5. 5P1 tickets ping the on-call phone on WhatsApp
6. 6Every ticket lands in the ticket sheet with its summary

How it works

1. 1Customer fills in the refund / return form
2. 2The request is saved to the request sheet
3. 3The owner gets an approval email with the details and Approve / Decline buttons
4. 4Approved: the customer gets an approval email with next steps, and the decision is logged
5. 5Declined: the customer gets a friendly "let's talk first" email with a booking link, and the decision is logged

How it works

1. 1Email / form events forward the sender to the webhook
2. 2Sender email and message are mapped into clean fields
3. 3The VIP list is read from Google Sheets
4. 4Rows are kept only when the VIP email matches the sender
5. 5The owner gets a WhatsApp nudge to reply personally
6. 6The touch is logged to the VIP sheet

How it works

1. 1Runs every Monday at 8am.
2. 2Reads the Accounts sheet (client, lastContact, openIssues, invoicesOverdue).
3. 3Scores each account: 100 minus one point per silent day, 10 per open issue, 20 per overdue invoice.
4. 4Keeps only accounts scoring under 60.
5. 5AI writes a short save play for each at-risk account.
6. 6Emails the owner one heads-up per account with the score and the play.
7. 7Maps a tidy log row (client, score, play, date).
8. 8Appends every rescue to the Health Scores tab.

How it works

1. 1Helpdesk or inbox forwards a resolved ticket to the ticket-resolved webhook.
2. 2Maps the ticket into clean fields (ticketId, customer, email, subject).
3. 3Waits 2 hours so the survey doesn't land mid-conversation.
4. 4Emails the customer a one-click survey (Great / OK / Poor faces).
5. 5Logs the survey send to the CSAT Sent tab.
6. 6A separate form catches the customer's rating and comment.
7. 7Saves every response to the CSAT Responses tab.
8. 8Checks whether the rating is Poor.
9. 9Poor: WhatsApps the owner a rescue ping with the comment.
10. 10Great or OK: ends quietly, nothing to fix.

How it works

1. 1Runs every Friday at 2pm.
2. 2Reads the Resolved Tickets sheet.
3. 3Keeps only tickets resolved in the last 7 days.
4. 4Bundles the week's tickets into one list for the AI.
5. 5AI picks the recurring issues and drafts 1-2 step-by-step articles.
6. 6Maps the drafts into a tidy row (date, week, article text).
7. 7Appends the drafts to the KB Drafts tab.
8. 8Emails the support lead the drafts for a quick polish-and-publish.

How it works

1. 1Staff fill the Log a Promise form (customer, email, what was promised, by when).
2. 2Maps the answers into clean fields.
3. 3Saves the promise to the Promises tab.
4. 4Waits 1 day (see setup note to wait until the exact promised date).
5. 5Emails the staff member a due-today reminder with the exact wording promised.
6. 6Waits 4 more hours.
7. 7Emails the manager a still-open nudge (ignore if already handled).
8. 8Maps a tidy log row.
9. 9Appends the follow-up to the Promise Log tab.

How it works

1. 1Every channel (email rule, FB/IG/WhatsApp automation) forwards messages to the channel-message webhook with a channel field.
2. 2Maps each message into clean fields: channel, from, text, receivedAt.
3. 3Appends the message to the Unified Inbox sheet, one place for every conversation.
4. 4Checks whether the message contains a question mark.
5. 5Question: AI drafts a short suggested reply in the business's voice.
6. 6Emails the team the original message plus the ready-to-edit draft.
7. 7No question: ends quietly (already logged in the inbox sheet).

How it works

1. 1Runs on the 15th of every month at 10am.
2. 2Reads the Customers sheet (client, email, service, lastContact, status).
3. 3Keeps only active customers with no contact in the last 90 days.
4. 4AI writes a personal check-in email per customer, referencing their service.
5. 5Splits the AI output into a clean subject and body.
6. 6Sends the check-in email to the customer.
7. 7Maps a tidy log row (client, days silent, subject, date).
8. 8Appends every touch to the Check-In Log tab.

How it works

1. 1Weekly Check-In Form
2. 2Log Check-In (append)
3. 3AI Progress Summary (AI chain)
4. 4Digest to Coach (send email)
5. 5AI Encouragement Note (AI chain)
6. 6Encouragement to Client (send email)

How it works

1. 1Runs every day at 8:30am.
2. 2Reads the Contracts sheet (client, renewalDate, openIssues, monthlyValue, accountOwnerEmail).
3. 3Keeps only contracts renewing between 30 and 45 days from now.
4. 4AI writes a renewal risk brief per client: risk level, signals, fix-first list, talk track.
5. 5Emails the account owner the brief with a fix-these-first framing.
6. 6Maps a tidy review row (client, renewal date, risk, date reviewed).
7. 7Appends the review to the Renewal Reviews tab.

How it works

1. 1Runs every day at 9:30am.
2. 2Reads the Onboarding tracker (client, email, step, stepStartedAt).
3. 3Keeps only clients sitting on the same step for 5 or more days.
4. 4Emails the client a gentle unblock: "stuck on this step? 15-minute call?"
5. 5WhatsApps the owner a stuck-client note with the step and days stuck.
6. 6Maps a tidy rescue row (client, step, days stuck, date).
7. 7Appends the rescue to the Rescue Log tab.

How it works

1. 1Every Morning 9am (schedule)
2. 2Read Open Invoices (swap: Xero)
3. 3Compute Days Overdue (code)
4. 4Reminder Stage (switch)
5. 5Gentle Reminder (send email)
6. 6Second Reminder (send email)
7. 7Final Notice (send email)
8. 8Combine Reminders (merge)
9. 9Log Reminders Sent (append)
10. 10Daily AR Report to Owner (send email)

How it works

1. 1The payment gateway calls the webhook when a charge fails.
2. 2Map Failure tidies the payload into customer, email, amount, reason.
3. 3Email 1 asks them to update their card, zero shame.
4. 4Wait 3 days, then Email 2 with a gentle expiry warning.
5. 5Wait 4 more days, then WhatsApp the owner for a manual chase.
6. 6Every case lands in the Dunning Log sheet.

How it works

1. 1Payment gateway posts the payment event
2. 2Payment details mapped to clean fields
3. 3Thank-you receipt emailed to the customer
4. 4Row appended to the ledger, owner pinged on WhatsApp

How it works

1. 1Fires on the 1st of the month at 8am
2. 2Reads active retainer clients
3. 3Visual filter keeps only active = yes
4. 4A Set node builds the invoice fields (number, period, due date)
5. 5Invoice emailed, then logged

How it works

1. 1The quoting tool or website calls the webhook when a quote is accepted.
2. 2Map Quote tidies the payload into client, email, amount, quoteRef.
3. 3Build Invoice Fields creates the invoice number (INV-yyyyMM-ref) and a due date 14 days out.
4. 4Send Invoice Email delivers a clean HTML invoice.
5. 5The invoice is appended to the Invoices sheet.
6. 6WhatsApp tells the owner the quote is now invoiced.

How it works

1. 1Runs Friday 5pm
2. 2Reads the week's transactions
3. 3Summarize node totals amounts grouped by type (in/out)
4. 4AI writes the commentary
5. 5Snapshot emailed to the owner

How it works

1. 1Runs daily at 9am
2. 2Reads contracts/subscriptions
3. 3Visual filter: renewal date within the next 30 days
4. 4IF within 7 days → urgent path (client email + owner WhatsApp); otherwise → gentle heads-up
5. 5Both paths merge and get logged

How it works

1. 1Gmail trigger watches for receipt/invoice emails
2. 2Email subject + body are mapped to clean fields
3. 3AI extracts VENDOR / DATE / AMOUNT / CATEGORY as labeled lines
4. 4A Set node splits those lines into columns (visual, no code)
5. 5Row appended to the expenses sheet

How it works

1. 1Runs every Monday at 8am.
2. 2Reads the Invoices sheet and keeps only unpaid rows.
3. 3Bucket Age tags each invoice 0-30, 31-60, 61-90 or 90+ days overdue.
4. 4Sum By Bucket totals the amounts per bucket.
5. 5AI drafts collection priorities: who to call first and an opening line.
6. 6The owner gets the AR aging summary by email.

How it works

1. 1Runs every morning at 8:30.
2. 2Reads the Bills sheet (vendor, amount, dueDate, status).
3. 3Keeps only bills still marked unpaid.
4. 4Keeps only bills due within the next 72 hours.
5. 5Maps each bill into a clean reminder record with days left.
6. 6Emails the owner one reminder per bill.
7. 7Sends a short WhatsApp nudge as backup.
8. 8Logs every reminder to the Reminder Log tab.

How it works

1. 1A staff member submits the Expense Request form.
2. 2The request is saved to the Expense Requests sheet.
3. 3An IF splits by amount: RM500 and above goes to the owner, below auto-approves.
4. 4Big requests email the owner an Approve / Decline button and wait.
5. 5A second IF reads the owner's click.
6. 6Approved: the staff member gets a confirmation email.
7. 7Declined: the staff member gets a polite decline email.
8. 8Small amounts: the staff member gets an instant auto-approval email.
9. 9All three outcomes merge back into one stream.
10. 10The final decision is logged to the Decision Log tab.

How it works

1. 1Runs every evening at 6pm.
2. 2Reads the Bank Transactions sheet (date, reference, amount, type).
3. 3Keeps only credit entries, money coming in.
4. 4Reads the Open Invoices sheet (invoiceNo, client, amount).
5. 5Collapses everything into a single report run.
6. 6AI compares both lists and outputs MATCHED / UNMATCHED lines with reasons.
7. 7Emails the bookkeeper the full match report.
8. 8Logs the run to the Reconciliation Log tab.

How it works

1. 1Fires on the 1st of each month at 7am.
2. 2Reads the Transactions sheet (date, category, amount).
3. 3Keeps only last month's entries.
4. 4Totals the amounts by category.
5. 5Collapses the totals into a single report run.
6. 6AI writes the narrative: revenue, top 3 costs, margin trend, one cost to question.
7. 7Emails the owner the snapshot in plain English.
8. 8Logs the run to the P&L Snapshots tab.

How it works

1. 1Runs every morning at 9am.
2. 2Reads the Installments sheet (client, email, installmentNo, dueDate, amount, status).
3. 3Keeps only rows still marked pending.
4. 4Keeps only installments due today.
5. 5Maps each one into a clean reminder with the pay link.
6. 6Emails the client their payment reminder.
7. 7Sends a short WhatsApp nudge as backup.
8. 8Logs every reminder to the Sent Log tab.

How it works

1. 1Runs every evening at 7pm.
2. 2Reads the Uncategorized tab (date, description, amount).
3. 3Keeps only rows whose category is still blank.
4. 4Maps each transaction into clean fields for the AI.
5. 5AI picks one category from the fixed list and gives a confidence.
6. 6A Set step extracts the category and confidence from the labeled lines.
7. 7The categorized row is appended to the Categorized tab.

How it works

1. 1Runs every night at 8pm.
2. 2Reads the Transactions sheet (date, description, amount, memo).
3. 3Keeps only entries posted today.
4. 4Keeps only unusually large amounts, RM1,000 and above.
5. 5AI judges each one: NORMAL or REVIEW, with a reason.
6. 6An IF routes on the verdict.
7. 7REVIEW: the owner gets a WhatsApp with the transaction and the reason.
8. 8NORMAL: the item passes through quietly.
9. 9Both paths merge back into one stream.
10. 10Every check is logged to the Anomaly Checks tab.

How it works

1. 1Runs every Friday at 8am.
2. 2Reads the Retainer Usage sheet (client, hoursUsed, hoursBudget).
3. 3Works out the burn percentage per client.
4. 4Keeps only clients at 80% of budget or more.
5. 5Emails the account lead a heads-up per flagged client.
6. 6An IF checks who is already past 100%.
7. 7Over budget: the owner gets a WhatsApp immediately.
8. 8Still within budget: the item passes through quietly.
9. 9Both paths merge back into one stream.
10. 10Every flag is logged to the Burn Log tab.

How it works

1. 1Runs every morning at 7:30.
2. 2Reads the Tax Calendar sheet (obligation, dueDate, notes).
3. 3Keeps only obligations due within the next 14 days.
4. 4Maps each one into a clean reminder with a days-left count.
5. 5Emails the owner one reminder per obligation.
6. 6Emails the bookkeeper the same reminder.
7. 7Logs every reminder to the Reminder Log tab.

How it works

1. 1A staff member submits the Staff Claim form with a receipt link.
2. 2The claim is saved to the Claims sheet.
3. 3The manager gets an email with Approve / Decline buttons and the flow waits.
4. 4An IF reads the manager's click.
5. 5Approved: the staff member is told it is paid next cycle.
6. 6The approved amount is appended to the Payroll Additions tab.
7. 7Declined: the staff member gets a query note asking for more detail.
8. 8Both outcomes merge back into one stream.
9. 9The decision is logged to the Claims Log tab.

How it works

1. 1Runs every Monday at 9am
2. 2Reads the document register
3. 3Visual filter: expiring within 30 days
4. 4A Set node computes days remaining
5. 5Reminder emailed to the responsible person, then logged

How it works

1. 1Booking Created Webhook
2. 2Normalize Booking (edit fields)
3. 3Save Appointment (append)
4. 4Instant Confirmation Email (send email)
5. 5Wait → 24h Before (1 days)
6. 6WhatsApp: Day-Before Reminder (send message)
7. 7Wait → 2h Before (22 hours)
8. 8SMS: 2-Hour Reminder
9. 9Wait → After Appointment (4 hours)
10. 10Follow-Up / Rebook Email (send email)

How it works

1. 1Booking Form
2. 2Add Job to Calendar
3. 3Read Technician Roster
4. 4Assign Next Available Tech (code)
5. 5Log Job + Assignment (append)
6. 6WhatsApp: Booking Confirmed (send message)
7. 7Wait → Day Before (1 days)
8. 8WhatsApp: Day-Before Reminder (send message)
9. 9Wait → After Job (1 days)
10. 10Hand Off to Review Request (POST)

How it works

1. 1Deal Won Webhook (swap: CRM)
2. 2Normalize Deal (edit fields)
3. 3Welcome Email + Intake Form (send email)
4. 4Send Contract (swap: DocuSign) (POST)
5. 5Create Project Folder (drive)
6. 6Build Kickoff Checklist (code)
7. 7Save Task Checklist (append)
8. 8Notify Team (Slack)
9. 9Respond 200 OK

How it works

1. 1Runs every day at 7am
2. 2Pulls today's calendar events + open tasks in parallel
3. 3Both streams merge
4. 4AI writes the one-screen briefing
5. 5Delivered by WhatsApp

How it works

1. 1Anyone submits the request form (department, description, urgency)
2. 2Switch routes by department
3. 3A Set node stamps the right assignee per route
4. 4Routes merge → task logged → assignee notified → requester gets confirmation

How it works

1. 1Friday 3pm schedule fires.
2. 2Reads the Task Board sheet (project, client, clientEmail, task, status).
3. 3Keeps rows that have a project name.
4. 4AI drafts the weekly update: done this week, in progress, next week, blockers.
5. 5Emails the client and logs the send.

How it works

1. 1Runs daily at 5pm
2. 2Reads the rota sheet
3. 3Visual filter keeps only tomorrow's shifts
4. 4Each staff member gets a WhatsApp with their shift details
5. 5Every reminder is logged

How it works

1. 1Daily 5:30am schedule fires.
2. 2Pulls tomorrow's rain probability from the Open-Meteo forecast API.
3. 3Extracts the rain risk into a single number.
4. 4If rain probability is 70% or higher: reads tomorrow's outdoor jobs from the sheet, WhatsApps each customer a friendly reschedule offer, then WhatsApps the owner a summary.
5. 5If skies look clear, it quietly does nothing.

How it works

1. 1Booking webhook arrives with guest name, email, topic and intake answers.
2. 2Maps the payload into clean fields.
3. 3AI drafts 3 agenda items from their answers plus 2 things to research before the call.
4. 4Creates a 15-minute prep block in the owner's calendar.
5. 5Emails the owner the prep brief, then emails the guest a confirmation with the agenda.

How it works

1. 1Technician submits the Job Photos form (job ID, before/after photo links, notes).
2. 2Saves the submission to the Job Log sheet.
3. 3AI rewrites the tech's shorthand notes into a client-friendly summary of what was done.
4. 4Emails the client a before/after report with both photos embedded.
5. 5Logs the send.

How it works

1. 1Daily 10am schedule fires.
2. 2Reads the Purchase Orders sheet (po, supplier, supplierEmail, expectedDate, status).
3. 3Keeps POs that are still open and past their expected date.
4. 4Emails each supplier a courteous nudge with the PO number.
5. 5WhatsApps the owner a late-PO heads-up and logs each chase.

How it works

1. 1A team member submits the Report an Issue form (reporter, area, severity, description).
2. 2The incident is saved to the Incident Register sheet.
3. 3A Switch routes the report by severity: High, Medium or Low.
4. 4High: the owner gets an immediate WhatsApp alert.
5. 5High: the manager also gets a full email with the details.
6. 6Medium: the manager gets an email to action within the day.
7. 7Low: the report is parked for the weekly review, no interruption.
8. 8All three paths merge back into one stream.
9. 9The routing outcome is logged so every incident shows who was notified.

How it works

1. 1Runs every weekday at 8:45am.
2. 2Reads the team list (name, email) from Google Sheets.
3. 3Emails each person the standup prompt with a link to the reply form.
4. 4Logs who was prompted this morning.
5. 5A team member answers the My Standup form (yesterday, today, blockers).
6. 6The answers are saved to the Standup Log sheet.
7. 7An IF checks whether the Blockers field has anything in it.
8. 8If yes, the owner gets a WhatsApp ping with the blocker and who raised it.
9. 9If no, nothing happens, the entry just sits in the log.

How it works

1. 1Runs every Monday at 7am.
2. 2Reads the SOP Schedule sheet (checklist name, assignee email, frequency, items).
3. 3Keeps only the checklists marked weekly.
4. 4Turns each item list into a formatted tick-box list.
5. 5Emails each assignee their checklist for the week.
6. 6Logs every dispatch to the Dispatch Log sheet.
7. 7Counts how many checklists were sent.
8. 8WhatsApps the owner a one-line dispatch summary.

How it works

1. 1Runs daily at 6:30am.
2. 2Reads the Equipment Register (asset, last service, interval days, assignee).
3. 3Computes each asset's next due date from last service plus interval.
4. 4Keeps only the assets due within the next 7 days.
5. 5Emails each assignee a book-the-service reminder.
6. 6Creates a service slot in the calendar on the due date.
7. 7Logs each reminder to the Maintenance Log.
8. 8Counts how many assets are due this week.
9. 9Emails the owner a morning digest with that count.

How it works

1. 1Runs on the 1st of each month at 9am.
2. 2Reads the Service Log sheet (client, client email, work done last month).
3. 3Keeps only rows that have a client email.
4. 4AI drafts each client's report: what was delivered, why it mattered, next month's preview.
5. 5A shared OpenAI model powers the drafting step.
6. 6A Set step extracts the subject and body from the draft and re-attaches the client details.
7. 7Emails each client their report.
8. 8Logs every report sent to the Report Log sheet.
9. 9Counts the reports sent this run.
10. 10WhatsApps the owner a one-line confirmation.

How it works

1. 1A team member submits the Book a Resource form (name, email, resource, date, time slot).
2. 2A Set step builds the start and end times from the chosen date and slot.
3. 3The request is saved to the Booking Requests sheet.
4. 4The booking is created in the shared calendar with resource and requester in the title.
5. 5The requester gets a confirmation email with the details.
6. 6The owner gets a short heads-up email about the new booking.
7. 7The booking is logged to the Booking Log sheet.

How it works

1. 1The technician submits the Job Done form (job ID, technician, customer email, work done, materials, follow-up needed).
2. 2The completion is saved to the Completions sheet.
3. 3An IF checks whether follow-up work is needed.
4. 4If yes, the job is appended to the Follow-Up Queue sheet.
5. 5Ops gets an email so the follow-up is scheduled, not remembered.
6. 6If no, the flow passes straight through.
7. 7Both paths merge back together.
8. 8The customer gets a job-complete summary email.
9. 9The send is logged to the Completion Log.

How it works

1. 1Someone submits the New Vendor form (company, contact email, service, payment terms).
2. 2A Set step maps the answers into clean vendor fields.
3. 3The vendor is saved to the Vendor Register sheet.
4. 4The vendor gets a welcome email requesting SSM cert, bank letter and insurance.
5. 5Finance gets a setup-task email with the vendor's details and terms.
6. 6A chase-documents reminder is created in the calendar 7 days out.
7. 7The owner gets a WhatsApp note that a new vendor entered onboarding.
8. 8The onboarding is logged to the Onboarding Log sheet.

How it works

1. 1Runs daily at 4pm, late enough to catch the day's real status.
2. 2Reads the Task Board sheet (task, assignee, assignee email, status, due date).
3. 3Keeps only tasks that are not done and already past their due date.
4. 4Emails each assignee a polite overdue nudge.
5. 5An IF checks whether the task is more than 3 days overdue.
6. 6If yes, the manager gets an escalation email with the details.
7. 7If no, the flow passes through without escalating.
8. 8Both paths merge back together.
9. 9The run is logged to the Escalation Log sheet.

How it works

1. 1Candidate submits the application form
2. 2Application saved to the applicant tracker
3. 3AI scores 0-100 against the role criteria with reasons
4. 470+ → interview invite + shortlist log. Below 70 → manual review pile (no auto-rejection)

How it works

1. 1Staff member submits the leave form
2. 2Request logged
3. 3Manager receives an approval email. The workflow WAITS for their click
4. 4Approved → employee notified + leave on the team calendar. Declined → employee notified with a note to discuss.

How it works

1. 1HR system (or a form) posts the new hire
2. 2Details mapped to clean fields
3. 3Welcome email to the new hire → IT checklist to IT → induction on the calendar → staff register updated

How it works

1. 1Webhook receives the departure (name, last day, role).
2. 2Map Departure tidies the fields.
3. 3IT gets an itemized revocation checklist by email.
4. 4Finance gets the final-pay checklist.
5. 5An exit-interview slot goes on the calendar.
6. 6The departure is appended to the Offboarding Log sheet.

How it works

1. 1Webhook receives the shortlisted candidate (name, email, role).
2. 2Map Candidate tidies the fields.
3. 3Candidate is emailed the booking link to pick a slot.
4. 4A hold block is placed on the interviewer's calendar.
5. 5Hiring manager gets the CV link and interview brief.
6. 6The invite is logged to the Recruitment sheet.

How it works

1. 1Friday 4pm: read the staff list and email each person the timesheet link.
2. 2Staff submit the Weekly Timesheet form; every entry is saved.
3. 3If OT is 5 hours or more, the manager gets an approve/decline email.
4. 4Approved: added to Payroll Additions. Declined: staff get a friendly query.
5. 5Low-OT entries go straight to Payroll Additions.

How it works

1. 1Runs on the 20th of each month at 9am.
2. 2Reads this month's Payroll Additions sheet (claims, OT, changes).
3. 3Summarize totals the amounts per staff member.
4. 4AI writes a per-staff prep summary and lists anomalies to double-check.
5. 5The payroll person gets everything for this month's run in one email.
6. 6The run is logged as Prepared.

How it works

1. 1Runs every day at 8am.
2. 2Reads the Staff Register sheet (name, probationEnd, contractEnd, manager).
3. 3Keeps only staff whose probation ends within the next 14 days.
4. 4Maps the reminder fields and counts the days left.
5. 5Emails the manager: decision due, confirm or extend.
6. 6Sends the owner a short heads-up.
7. 7Logs the reminder in the Reminder Log tab.

How it works

1. 1A webhook fires when a new hire starts (from your HR form or ATS).
2. 2Maps the hire's name, email, manager and start date.
3. 3Waits 30 days.
4. 4Emails the 30-day check-in survey link.
5. 5Waits another 30 days.
6. 6Emails the 60-day check-in survey link.
7. 7Waits a final 30 days.
8. 8Emails the 90-day check-in survey link.
9. 9Emails the manager a prompt to book the 90-day review.
10. 10Logs all milestones to the Milestones Log tab.

How it works

1. 1On the 1st at 10am, reads the staff list.
2. 2Emails every staff member the anonymous pulse link.
3. 3The Team Pulse form collects score and comments (no name asked).
4. 4Answers are tidied and stamped with the month.
5. 5Each response is appended to the Pulse Responses tab.
6. 6On the 7th at 10am, reads all responses.
7. 7Keeps only this month's responses.
8. 8Builds one line per response.
9. 9Combines them into a single block.
10. 10AI writes the morale summary with a labeled-line format.
11. 11The owner gets the summary by email.

How it works

1. 1Runs every Monday at 8:30am.
2. 2Reads the Certs Register sheet (staff, staffEmail, cert, expiryDate).
3. 3Keeps only certs expiring within the next 60 days.
4. 4Maps the renewal fields and counts days left.
5. 5Emails the staff member a renewal reminder with the deadline.
6. 6Emails the manager the expiring item so nothing slips.
7. 7Appends each reminder to the Renewal Log tab.

How it works

1. 1Fires at 9am on the 1st of January, April, July and October.
2. 2Reads the Staff Register (name, email, manager, role).
3. 3Stamps each row with the quarter label (e.g. Q3 2026).
4. 4Emails every staff member their self-review form link.
5. 5Emails each manager a note on what to prepare for the review.
6. 6Creates a placeholder review meeting in the calendar two weeks out.
7. 7Appends a Cycle Started row per staff member to the Review Log.

How it works

1. 1A webhook fires when an application's stage changes (from your ATS or tracking sheet).
2. 2Maps the candidate's name, email, role and new stage.
3. 3A Switch routes by stage: Screening, Interview, Offer or Rejected.
4. 4Screening: a warm "you're in the running" acknowledgment.
5. 5Interview: an invite email asking them to pick a slot.
6. 6Offer: the good-news heads-up that the offer letter is coming.
7. 7Rejected: a kind, encouraging, door-open note.
8. 8All four paths merge back into one stream.
9. 9Every update is appended to the Applications Log.

How it works

1. 1Runs every day at 9am.
2. 2Reads the Pipeline sheet (candidate, stage, stageEnteredAt, owner).
3. 3Keeps only candidates stuck in a stage for more than 3 days.
4. 4Maps the nudge fields and counts the days stuck.
5. 5Emails the responsible owner a nudge per stuck candidate.
6. 6Appends each nudge to the Nudge Log.
7. 7Counts stuck candidates per stage.
8. 8Emails a per-stage bottleneck line to the business owner.

How it works

1. 1HR submits the Generate Offer form (candidate, email, role, salary, start date).
2. 2AI drafts a full MY-style offer letter with placeholders for statutory details.
3. 3The owner receives the draft as an approve/decline email and decides inline.
4. 4An IF node checks the owner's decision.
5. 5Approved: the candidate gets the offer letter by email.
6. 6Declined: HR gets a revise-and-resubmit note instead.
7. 7Both paths merge back into one stream.
8. 8The outcome is appended to the Offer Log.

How it works

1. 1HR submits the Request References form (candidate + two referees).
2. 2The request fields are mapped and stamped with the request date.
3. 3Referee 1 gets the structured questions form link.
4. 4Referee 2 gets the same.
5. 5The request is logged as Requested in the Reference Log.
6. 6The workflow waits 3 days.
7. 7HR gets a chase-status note listing both referees.
8. 8The chase is logged so the trail is complete.

How it works

1. 1Runs every day at 10:30am, after everyone should be in.
2. 2Reads the Attendance Log sheet (staff, date, clockIn).
3. 3Keeps only clock-ins after 9:15 (time compared as a number, 915).
4. 4Maps the late-entry fields with the cutoff for context.
5. 5Appends each late entry to the Late Log tab.
6. 6Emails the manager one alert per late staff member.
7. 7Counts today's lates per staff member.
8. 8Appends the per-staff counts to the Late Counts tab for trend tracking.

How it works

1. 1Runs every Monday at 7:15am, before the week starts.
2. 2Reads the Approved Leave sheet (staff, from, to).
3. 3Keeps only leave that overlaps the coming 7 days.
4. 4Builds one plain line per absence (who, from, to).
5. 5Combines all lines into a single block.
6. 6AI writes the digest: who's out when, plus coverage gaps to watch.
7. 7The whole team gets the digest by email.
8. 8The digest is appended to the Digest Log for reference.

How it works

1. 1Runs every day at 8:15am.
2. 2Reads the Staff Register (name, birthday, joinDate).
3. 3Keeps only staff whose birthday (month-day) is today.
4. 4Maps the celebration fields with today's date.
5. 5Emails the team: it's their colleague's birthday today.
6. 6WhatsApps the owner a nudge to wish them personally.
7. 7Appends the celebration to the Celebration Log.

How it works

1. 1A staff member submits the Suggestion Box form any time.
2. 2The entry is tidied: name becomes Anonymous when left blank, and the month is stamped.
3. 3Each suggestion is appended to the Suggestions tab.
4. 4On the 28th at 9am, the digest run reads all suggestions.
5. 5Keeps only this month's entries.
6. 6Builds one line per suggestion (area + text, no names).
7. 7Combines them into a single block.
8. 8AI writes the digest: themes plus top 3 actionable ideas, respectful and attribution-free.
9. 9The owner gets the digest by email.

How it works

1. 1Cart Abandoned Webhook
2. 2Order Events Webhook
3. 3Wait 1 Hour (1 hours)
4. 4Route by Order Status (switch)
5. 5Read Recent Orders
6. 6WhatsApp: Order Confirmed (send message)
7. 7WhatsApp: Order Shipped (send message)
8. 8WhatsApp: Delivered + Review Ask (send message)
9. 9Did They Order Anyway? (code)
10. 10Log Order Event (append)
11. 11Still Abandoned? (if)
12. 12WhatsApp: Recovery Nudge 1 (send message)
13. 13Already Ordered: Skip (no-op)
14. 14Wait 23 Hours
15. 15Email: Recovery + Discount (send email)

How it works

1. 1Store fires a webhook when a COD order comes in
2. 2Order details are mapped into clean fields
3. 3Buyer gets a WhatsApp asking them to reply YES to confirm
4. 4After 6 hours, ops gets an email to check unconfirmed orders
5. 5Order is logged to the tracking sheet

How it works

1. 1Store fires a webhook when inventory goes above zero
2. 2Restocked product details are mapped into clean fields
3. 3The waitlist sheet is read
4. 4Only waiters for that exact SKU are kept
5. 5Each waiter gets an email with the product link, plus a WhatsApp option
6. 6Every notification is logged

How it works

1. 1Store fires a webhook when an order is marked delivered
2. 2Order and customer details are mapped
3. 3Wait 3 days so the product has been tried
4. 4First review ask goes out, with a photo-review incentive
5. 5Wait 4 more days
6. 6If the customer email is on file, a gentle second ask goes out
7. 7The request is logged

How it works

1. 1Runs every morning at 9am
2. 2Reads recent orders from the sheet (customer, email, product, order date, usage days)
3. 3Calculates each order's reorder-due date (order date + usage days)
4. 4Keeps only customers whose due date is right about now (last 2 days)
5. 5Sends a friendly one-click reorder email
6. 6Logs every reminder sent

How it works

1. 1The store fires a webhook the moment a checkout payment fails.
2. 2Map Attempt tidies the payload into name, email, cart total, order ref and a retry link.
3. 3Wait 30 Minutes gives the shopper room to retry on their own first.
4. 4Email 1 reminds them their order is saved, with a one-click retry link and an FPX option.
5. 5Wait 1 Day lets the first nudge land.
6. 6Email 2 offers a 5% comeback code to close the sale.
7. 7Every attempt is logged to the Recovery Log sheet so the owner can see recovered revenue.

How it works

1. 1Runs daily at 7am
2. 2Reads the inventory sheet
3. 3Visual filter: stock level ≤ reorder point
4. 4A Set node builds the reorder quantity
5. 5PO draft emailed per item + logged

How it works

1. 1The store fires a webhook when an order is placed.
2. 2Map Order pulls out the bought SKU, product name, customer name and email.
3. 3Read Product Pairings loads the owner's pairing table (boughtSku → pairSku, pairName, pitch).
4. 4Filter Matching Pairing keeps only rows where boughtSku matches what was just ordered.
5. 5Wait 5 Days lets the first purchase arrive and settle in.
6. 6Email: Perfect Match sends the paired product with the owner's own one-line pitch.
7. 7Log Cross-Sell Sent appends the touch to a sheet so nobody gets pitched twice.

How it works

1. 1The store fires a webhook on a customer's first order.
2. 2Map Customer pulls out name, email and the product they bought.
3. 3Email 1 (day 0) welcomes them with the brand story and care tips for their product.
4. 4Wait 4 Days.
5. 5Email 2 shares practical ways to get the most out of the purchase.
6. 6Wait 5 Days.
7. 7Email 3 invites them into the loyalty circle with a referral reward.
8. 8Log Series Complete appends the customer to a sheet so the series never repeats.

How it works

1. 1A schedule fires on the 5th of every month at 10am.
2. 2Read Customers loads the customer sheet (customer, email, lastProduct, lastOrder).
3. 3Filter Lapsed 90d keeps only people whose last order is older than 90 days.
4. 4Prep Winback Fields extracts a first name and tidies the fields for the writer.
5. 5AI: Personalized Winback drafts a short note referencing their last purchase.
6. 6Email: Comeback Offer sends it with the COMEBACK10 code.
7. 7Log Winback appends each send to a sheet so next month's run can skip them.

How it works

1. 1The store fires a webhook whenever a product review is submitted.
2. 2Map Review tidies rating, product, customer, email and the review text.
3. 3IF Rating 3 or Below splits unhappy from happy.
4. 4Unhappy: WhatsApp Owner Alert pings the owner with the review and who to call.
5. 5Then Email Support Team briefs the inbox to reach out before it spreads.
6. 6Happy: Email Thank-You thanks them and asks for a photo or social share.
7. 7Log Review appends every review and the action taken to a sheet.

How it works

1. 1A schedule fires daily at 11am.
2. 2Read Open Shipments loads orders still in transit (order, customer, email, trackingStatus, trackingUrl, shippedAt).
3. 3Filter Delayed keeps shipments older than 5 days that are still marked in_transit.
4. 4Compute Days In Transit works out exactly how long each one has been on the road.
5. 5Email: Proactive Notice apologises to each customer and hands them the tracking link.
6. 6WhatsApp Ops Summary pings ops with each stuck shipment to chase the courier.
7. 7Log Notices appends every notice sent to a sheet so customers aren't re-notified daily.

How it works

1. 1A schedule fires daily at 9pm.
2. 2Read Orders loads the orders sheet (orderId, product, total, orderDate).
3. 3Filter Today's Orders keeps only orders placed since midnight.
4. 4Summarize By Product totals revenue and order count per product.
5. 5Build Report Line turns each product row into a readable one-liner.
6. 6Combine Report Lines merges the lines into a single report block.
7. 7AI: Daily Trading Note writes the WhatsApp-length summary with an anomaly check.
8. 8WhatsApp Owner delivers the note to the owner's phone.

How it works

1. 1The store fires a webhook when an order is placed for fulfilment.
2. 2Map Order pulls the order number, customer, shipping address and the items array.
3. 3Build Picklist Lines turns the items into one "qty x SKU - name (bin)" line per item.
4. 4Email: Warehouse Picklist sends the printable slip to the packing bench.
5. 5WhatsApp Warehouse Heads-Up pings the packer that a new slip is in the inbox.
6. 6Append Fulfilment Queue adds the order to the working queue sheet.
7. 7Log Order appends a permanent record for the day's count.

How it works

1. 1The store fires a webhook whenever a product price changes.
2. 2Map Change tidies the SKU, product name, old price, new price and product URL.
3. 3IF Price Dropped checks the new price is actually lower (increases are ignored).
4. 4Read Wishlist loads the wishlist sheet (sku, name, email).
5. 5Filter Wishlist SKU Match keeps only the people waiting on this product.
6. 6Email: Price-Drop Alert tells each of them, old price versus new.
7. 7No Price Drop parks price increases quietly.
8. 8Log Alert Run appends the outcome to a sheet either way.

How it works

1. 1The customer fills in the Return Request form (order no, email, item, reason, photos link).
2. 2Save RMA appends the request to the RMA Requests sheet.
3. 3Ops Approval emails the owner the details with Approve / Decline buttons and waits.
4. 4IF Approved branches on the owner's click.
5. 5Approved: Email Return Label Instructions tells the customer exactly how to send it back.
6. 6Declined: Email Clarification Ask requests photos or more detail, keeping the door open.
7. 7Log RMA Decision appends the outcome so the sheet shows every request end to end.

How it works

1. 1The owner fills in the Launch a Product form (product, link, key benefit, launch offer).
2. 2AI: Launch Copy writes the announcement email plus two platform-ready captions.
3. 3Extract Launch Copy splits the output into subject, body and the two captions.
4. 4Email: List Announcement sends the launch email to the list segment.
5. 5Append Captions to Post Queue drops both captions into the social queue sheet.
6. 6Email: Owner Recap shows the owner everything that just went out.

How it works

1. 1The store fires a webhook on every new order.
2. 2Map Order extracts amount, shipping and billing addresses, email domain and first-order flag.
3. 3IF High Risk flags orders of RM1,000+ from first-time buyers.
4. 4AI: Risk Note reviews the order and lists what looks off plus verification steps.
5. 5Email: Ops Hold-Fulfilment tells ops to hold shipping until the checks are done.
6. 6WhatsApp Owner gives the owner the one-line heads-up.
7. 7Normal orders pass through the Normal Order lane untouched.
8. 8Log Screen appends every screening result to a sheet.

How it works

1. 1The store fires a webhook whenever a product's stock level changes.
2. 2Map Change tidies the SKU, product name and new quantity.
3. 3Update Marketplace A pushes the new quantity to the first marketplace API.
4. 4Update Marketplace B pushes the same quantity to the second marketplace API.
5. 5Log Sync appends the sync result to a sheet for an audit trail.
6. 6IF Low Stock checks whether the new quantity has fallen to 5 or below.
7. 7WhatsApp Owner Low-Stock warns the owner it's time to reorder.
8. 8Healthy stock levels pass through the Stock Healthy lane quietly.

How it works

1. 1A schedule fires daily at 5am, before the ad platforms' morning refresh.
2. 2Read Product Master loads the full product sheet (sku, title, price, status, image, url).
3. 3Filter Active Products drops anything discontinued, hidden or out of season.
4. 4Shape Feed Row maps each product into catalog fields (id, title, price, availability, image_link, link).
5. 5Push to Meta Catalog sends the shaped rows to the catalog batch endpoint.
6. 6Log Feed Run appends each pushed row to a sheet for the audit trail.
7. 7Summarize Run counts how many products went out.
8. 8Email: Feed Summary tells the owner the feed is fresh and how big it was.

How it works

1. 1Every Monday 8am (schedule)
2. 2Fetch GA4 Traffic (swap creds) (POST)
3. 3Read Sales Numbers
4. 4Fetch Ad Spend (swap: Meta) (GET)
5. 5Wait for All 3 (merge)
6. 6Combine KPIs (code)
7. 7AI Weekly Summary (AI chain)
8. 8Email the Digest (send email)
9. 9WhatsApp the Digest (send message)

How it works

1. 1Runs every 5 minutes
2. 2HTTP node pings the site (set to continue even on failure)
3. 3IF checks: did we get a healthy 200?
4. 4Healthy → nothing happens. Down → WhatsApp + email alert + incident log

How it works

1. 1Error Trigger fires when a linked workflow fails
2. 2Maps the workflow name and error message
3. 3WhatsApp alert to the owner right away
4. 4Email with the full failure details
5. 5Row appended to the Error Log sheet

How it works

1. 1Runs daily at 8am
2. 2Reads this month's sales from the sheet
3. 3Sums the revenue so far
4. 4Compares it to where the month SHOULD be by today
5. 5WhatsApps the owner: behind pace or on pace
6. 6Logs the pacing number for trend history

How it works

1. 1Runs daily at 9am
2. 2Pulls sessions from the GA4 Data API (yesterday vs same day last week)
3. 3Works out the drop percentage
4. 4If the drop is 30% or more: email + WhatsApp the owner
5. 5Every check is logged either way

How it works

1. 1Schedule fires daily at 8:30am.
2. 2HTTP request fetches yesterday's spend and revenue from the ad platform.
3. 3"ROAS Math" computes ROAS = revenue divided by spend.
4. 4IF checks whether ROAS fell below 2x.
5. 5Below 2x: the owner gets an email flagging likely creative fatigue.
6. 6Healthy: the run passes through quietly.
7. 7Both paths merge back together.
8. 8The day's numbers are appended to the ROAS History sheet for trends.

How it works

1. 1Schedule fires daily at 8:30pm.
2. 2Sheets reads the full sales log.
3. 3Filter keeps only rows dated today.
4. 4Summarize totals the amounts and counts the sales.
5. 5"Format Snapshot" shapes the numbers into a message.
6. 6WhatsApp sends the owner tonight's one-line summary.
7. 7The snapshot is appended to a Snapshot Log tab for history.

How it works

1. 1Schedule fires every Monday at 7:45am.
2. 2HTTP calls the Search Console Search Analytics API for the last 7 days.
3. 3"Map GSC Rows" packs the rows into one field for the AI.
4. 4AI writes the movers report as labeled lines (WINNERS / SLIPPING / ACTION).
5. 5The shared OpenAI model powers the AI step.
6. 6Email delivers the report to the owner.
7. 7"Log Row" stamps the date onto the report text.
8. 8Sheets appends the report to a Report Log for history.

How it works

1. 1Schedule fires on the 1st of each month at 7:30am.
2. 2Sheets reads the monthly KPI history rows.
3. 3"Combine All Months" folds every row into one item for the AI.
4. 4AI writes the review: growth, declines, three priorities.
5. 5The shared OpenAI model powers the AI step.
6. 6Email delivers the monthly board report to the owner.
7. 7"Log Row" stamps the date onto the review text.
8. 8Sheets appends the review to a Review Log for the record.

How it works

1. 1Schedule fires every Monday at 8:15am.
2. 2Sheets reads last week's ad spend rows.
3. 3Summarize totals the spend.
4. 4In parallel, Sheets reads last week's new customer rows.
5. 5Summarize counts the new customers.
6. 6Merge brings both totals together.
7. 7Limit collapses the merge to one row.
8. 8"CAC Math" divides spend by customers.
9. 9The week's CAC is appended to CAC History.
10. 10IF checks whether CAC hit RM200; if so the owner gets an email, otherwise the run ends quietly.

How it works

1. 1Schedule fires every Sunday at 6pm.
2. 2Sheets reads the full reviews log.
3. 3Filter keeps only reviews from the last 30 days.
4. 4Summarize averages the rating field.
5. 5"Trend Row" rounds the score and stamps the week.
6. 6The rolling score is appended to Score History.
7. 7IF checks whether the average fell below 4.3.
8. 8Below 4.3: the owner gets a heads-up email.
9. 9Otherwise the run ends quietly.

How it works

1. 1Schedule fires every Monday at 8:45am.
2. 2Sheets reads the funnel events tab (one row per week of stage counts).
3. 3Limit keeps the latest week's row.
4. 4"Conversion Math" computes lead rate, quote rate and close rate.
5. 5AI names where the funnel leaks most and gives one fix.
6. 6The shared OpenAI model powers the AI step.
7. 7Email delivers the leak report to the owner.
8. 8"Log Row" stamps the week onto the rates.
9. 9Sheets appends the rates to Funnel History.

How it works

1. 1Schedule fires daily at 7:15am.
2. 2Sheets reads the email send log.
3. 3Filter keeps only yesterday's rows.
4. 4Summarize totals sent, bounces and opens.
5. 5"Rates" computes bounce rate and open rate percentages.
6. 6IF checks whether the bounce rate hit 3%.
7. 7Spike: the owner gets an email explaining likely list or domain issues.
8. 8Healthy: the run passes through quietly.
9. 9Both paths merge back together.
10. 10The day's rates are appended to a History tab for trends.

How it works

1. 1Schedule fires every Sunday at 3am.
2. 2Sheets reads the page list (one row per URL to watch).
3. 3HTTP requests each page, capturing the status code without failing the run.
4. 4IF checks whether the status is 400 or higher.
5. 5Broken: "Map Broken Row" records the URL, status and timestamp.
6. 6The row is appended to the Broken List sheet.
7. 7The webmaster gets an email naming the page and status.
8. 8Healthy pages pass through quietly.

How it works

1. 1Schedule fires every Wednesday at 4am.
2. 2HTTP calls the PageSpeed Insights API for the homepage on mobile.
3. 3"Extract Scores" pulls the performance score and LCP out of the response.
4. 4The week's scores are appended to Speed History.
5. 5IF checks whether performance fell below 70.
6. 6Slow: the owner gets an email explaining why speed matters and what to check.
7. 7Fast: the run ends quietly.

How it works

1. 1Schedule fires daily at 6am.
2. 2HTTP fetches the competitor's page.
3. 3"Content Signal" measures the page (content length) as the change signal.
4. 4Sheets reads the stored snapshots.
5. 5Limit keeps the most recent snapshot row.
6. 6IF compares today's signal to the stored one.
7. 7Changed: AI writes a short what-to-check note.
8. 8The shared OpenAI model powers the AI step.
9. 9Email sends the owner the change alert.
10. 10Unchanged: the run passes through quietly.
11. 11Both paths merge back together.
12. 12"Snapshot Row" stamps today's signal.
13. 13Sheets appends it to Snapshots for tomorrow's comparison.

How it works

1. 1Schedule fires on the 2nd of each month at 9am.
2. 2HTTP calls the Business Profile Performance API for last month's metrics.
3. 3"Map Metrics" packs the response and stamps the month label.
4. 4AI writes the local visibility report: what moved, and one GBP action.
5. 5The shared OpenAI model powers the AI step.
6. 6Email delivers the report to the owner.
7. 7"Log Row" stamps the date onto the report text.
8. 8Sheets appends the report to a Report Log for history.

How it works

1. 1Schedule fires every Monday at 9:15am.
2. 2Sheets reads the social stats rows (one row per platform per week).
3. 3"Combine Platforms" folds all rows into one item for the AI.
4. 4AI writes the growth note: per-platform change, best post type, one experiment.
5. 5The shared OpenAI model powers the AI step.
6. 6Email delivers the growth note to the owner.
7. 7"Log Row" stamps the date onto the note.
8. 8Sheets appends the note to a Report Log for history.

How it works

1. 1Schedule fires daily at 5:15am.
2. 2Sheets reads the domain register (domain, domainExpiry, sslExpiry per row).
3. 3Filter keeps rows whose domain expiry falls within the next 21 days.
4. 4"Map Alert" computes days left and shapes the alert fields.
5. 5Email gives the owner the expiry details and renewal steps.
6. 6WhatsApp follows with the urgent one-liner.
7. 7The alert is appended to a Renewal Alert Log.

How it works

1. 1Schedule fires every Sunday at 2am.
2. 2Sheets reads every row of the critical Customers tab.
3. 3"Stamp Backup Row" adds the backup date to each row, keeping all original fields.
4. 4The rows are appended to the separate Backups spreadsheet.
5. 5Summarize counts how many rows were backed up.
6. 6"Backup Summary" shapes the confirmation fields.
7. 7Email tells the owner the backup completed, with date and row count.