Workflow Recipes And Examples
Workflow Recipes and Examples
This article is a cookbook. Each recipe is a complete, runnable workflow you can adapt to your app — copy the structure, swap in your tables and fields, and you're done. Use it as inspiration and as a starting point.
Recipe 1 — New customer onboarding email
What it does: Sends a welcome email and creates a follow-up task whenever a new customer is added.
| Trigger | Record Created on Customers |
|---|---|
| Step 1 | Send Email — to Customer Email, subject "Welcome to {{company_name}}!", body from the "Welcome" email template. |
| Step 2 | Create Connected Record — add a Task connected to the customer with name "Schedule onboarding call" and due date = today + 2 days. |
Recipe 2 — Daily overdue invoice reminder
What it does: Every morning, finds overdue invoices and emails the customer + Slack alerts the AR team.
| Trigger | Schedule, Daily at 8:00 AM |
|---|---|
| Trigger Filter | Status = "Sent" AND Due Date is before today AND Paid = "No" |
| Step 1 | Send Email — to Customer Email with reminder template. |
| Step 2 | Slack: Send Channel Message — post to #ar-team with the invoice number and customer name. |
| Step 3 | Update Record — set Last Reminder Sent to current date/time. |
Recipe 3 — Route a lead based on deal size
What it does: When a lead is created, assigns it to a different sales team based on the estimated deal value.
| Trigger | Record Created on Leads |
|---|---|
| Step 1 | Branches:
|
| Step 2 | Send Email — welcome message to the lead. |
Recipe 4 — Charge a customer when an order is approved
What it does: Charges Stripe and updates the order with the charge ID.
| Trigger | Record Updated on Orders |
|---|---|
| Trigger Filter | Status = "Approved" AND Stripe Charge ID is blank |
| Step 1 | Stripe — Create Charge for the order's total, on the customer's saved card. |
| Step 2 | Update Record — set Stripe Charge ID from the integration response, set Status = "Paid". |
| Step 3 | Send Email — receipt to the customer. |
Recipe 5 — Generate and email a PDF receipt
What it does: When an order is paid, generate a receipt PDF and email it.
| Trigger | Record Updated on Orders, where Status = "Paid" |
|---|---|
| Step 1 | Create PDF Form — fill the "Order Receipt" template with the order's data, save to the order's Receipt PDF field. |
| Step 2 | Send Email — to Customer Email with the receipt PDF attached. |
Recipe 6 — AI-triage incoming support tickets
What it does: Uses an AI Prompt to classify a ticket and route it.
| Trigger | Record Created on Support Tickets |
|---|---|
| Step 1 | AI Prompt — "Triage Ticket": takes the ticket body, returns category (Billing/Bug/Feature) and priority (Low/Med/High). |
| Step 2 | Update Record — set Category and Priority from the AI response. |
| Step 3 | Branches:
|
Recipe 7 — Calculate a derived total with Custom Code
What it does: Computes subtotal/tax/total when an order is created or edited.
| Trigger | Record Created or Edited on Orders |
|---|---|
| Step 1 | Run Custom Code:
|
| Step 2 | Update Record — set Subtotal from Action Response Value, set Total from Action Response Value. |
Recipe 8 — Weekly CSV export to operations
What it does: Every Monday, exports last week's orders to CSV and emails them to the operations team.
| Trigger | Schedule, Weekly on Monday at 6:00 AM |
|---|---|
| Step 1 | Export to CSV — Orders, filter by Created in the last 7 days, sorted by Created descending. |
| Step 2 | Send Email — to ops@example.com, subject "Last week's orders," CSV attached. |
Recipe 9 — Stamp "Last Login" when a user signs in
What it does: Each user login updates the user's record.
| Trigger | User Event — User Logged In |
|---|---|
| Step 1 | Update Record — on the User record, set Last Login = current date/time, increment Login Count by 1. |
Recipe 10 — One-click "Mark as Shipped" button
What it does: A button on each order updates the status, notifies the customer, and posts to Slack.
| Trigger | Manual, on Orders |
|---|---|
| Step 1 | Show Message — "Marking as shipped…" |
| Step 2 | Update Record — set Status = "Shipped", Shipped At = current date/time, Shipped By = logged-in user. |
| Step 3 | Send Text — to the customer's phone with tracking info. |
| Step 4 | Slack: Send Channel Message — post to #fulfillment. |
| Page setup | Add a "Mark as Shipped" action button on the Orders table that triggers this workflow (with confirmation). |
Adapting these recipes
None of these recipes are sacred — they're starting points. Once you have a workflow set up:
- Add Conditions to gate steps on specific field values.
- Add Show Message steps so end users see what's happening.
- Always Dry Run before activating.
- Save versions with comments so you can roll back if needed.
- Group related workflows into folders (e.g. all the "Order" workflows in one folder).
We'd love to hear your feedback.