Each one replaced a person doing the same thing every day. The oldest has been running since 2023, and none of them needed rebuilding.
Order details arrived from the field system, and somebody retyped them into Fishbowl line by line — every order, every day. Typos created inventory problems that surfaced weeks later, and the person doing it was too senior to be doing it.
A webhook catches the order data, generates the reference number, and converts the payload into Fishbowl’s CSV import structure — a format with very specific requirements and no forgiving parser. Scheduled delivery dates calculate automatically, including the month-end edge cases that break naive date logic. Records that fail validation are flagged for review rather than imported broken.
Attachments arrived by email and someone downloaded each one, worked out which supplier sent it, renamed it, found the right client folder, uploaded it, then re-entered the details into a tracking system. Roughly nine hours a week, and invoices still went missing.
A scenario that watches Outlook, identifies the supplier, converts attachments where needed, files them into the correct OneDrive folder and creates the matching Airtable record. Each supplier format runs on its own branch, so a new document type can’t break the rest. Anything missing a required field is held for review instead of filed wrongly.
Seven to eight hours a week writing posts and publishing them by hand across several platforms. Posting was inconsistent because it depended on someone having a free afternoon.
Content ideas sit in a Notion board. ChatGPT drafts platform-specific versions and everything waits. Nothing publishes until it’s marked approved — then it goes out on schedule, across every channel. The scenario runs every fifteen minutes with error handling on each branch, so a failed API call on one platform doesn’t stop the others.
Reservations arrived through one system, payments ran through another, guest communication through a third, and channel availability through a fourth. Staff moved details between all of them by hand, and a missed step meant a guest arriving to a room that wasn’t ready.
An automation that parses each incoming reservation and routes it where it needs to go: guest details into Constant Contact, payment through Helcim, availability into Beds24. Access codes are issued only once payment clears, and a failed payment pauses access automatically instead of requiring someone to notice.
Send me one paragraph describing it. I’ll tell you what it would take to automate — or tell you honestly that it isn’t worth it.