Recipes
When you’re not sure what to hand off, start here. Each guide walks the whole path: picking tools and skills → writing the behavior instructions → scheduled runs and approvals.
These setups are real work running in real businesses, rewritten so you can build them yourself. They’re not the only right answer; they’re a verified starting point. Add or drop tools, change the run time, change how you get notified.
If you’d rather not build it yourself, or the setup is more hands-on than you want, our team can build and operate it for you. See managed service .
What’s here
Partners place orders through a link like a chat; an AI employee confirms them and logs them into your ERP/CRM as sales orders. Nobody retypes anything.
Partner Order Intake → ERPAn AI employee prepares per-vendor quote requests and the side-by-side comparison; a person picks the vendor. The order mail and ERP record go out only when they match what was approved.
Purchasing Buyer: Quotes → Order → ERPDrive a real browser to read a booking channel with no dedicated integration, and add only the new bookings to Google Calendar.
Booking Intake → CalendarCatch missing items and inconsistencies by the same standard every time, with a review report written for you. You only do the final check.
Repetitive Document ReviewGet one page of what matters each morning, and hear about competitor prices only when they actually move.
Morning Briefing & Change WatchPicking one
| If this is your day | Start here |
|---|---|
| Orders and requests arrive as free text and you retype them | Partner Order Intake → ERP |
| You collect part quotes from each vendor by mail, retype them into a spreadsheet to compare, then write the order and key it into the ERP | Purchasing Buyer: Quotes → Order → ERP |
| You log into an admin screen several times a day to check it | Booking Intake → Calendar |
| You review the same document fields over and over | Repetitive Document Review |
| You sweep several sources each morning looking for what changed | Morning Briefing & Change Watch |
Shared patterns
There are five recipes, but only a handful of building blocks. Mix the ones that fit your work.
| Pattern | When to use it | Appears in |
|---|---|---|
| Compare against last seen | Never process the same thing twice; only report what moved | Booking intake · Morning briefing |
| Hand off the screen to sign in | Reach a service with no integration, without sharing a password | Booking intake |
| Split into two employees | The public-facing surface must never hold connection details | Order intake |
| Fix the verdict standard | Results must not vary by person or by day | Document review |
| A person chooses; run only if it matches what was approved | A judgment call such as selecting a vendor, where a change after approval must stop the action | Purchasing buyer |
Before you start
Each recipe’s cost notes, safety settings, and internals live in the # Advanced section at the bottom. Following the main body is enough to get it working; go to Advanced when you want to swap tools or trim cost.
Next steps
- Giving employees tools: what each tool in these recipes does, and good combinations
- Connections: attach the tools you already use by connecting your account
- Creating skills: turn a procedure that worked into something reusable
- Installing skills & templates: take ready-made skills and templates as-is