The NocoBase workflow plugin turns record events and schedules into automations: triggers, conditions, approval nodes, API calls, emails. Wiring up a multi-step flow through the UI takes care — one wrong branch and deals vanish into the void. Your vibe-code agent can read the workflow configuration, build the flow step by step, and test it against real data. Here are ten automations worth handing over.

1. Expense Approval Chain

Requests, approvals, and notifications are the bread and butter of the workflow plugin. The agent can build an event-triggered flow that fires when an expense record is created, routes it to the requester’s manager for approval, and emails the outcome. Ask: “Build a workflow that triggers when an Expense is created, sends it to the employee’s manager for approval, and emails the requester approved or rejected with the manager’s comment.” It will set up the approval node, map the fields into the email template, and create a test expense so you can watch the whole chain fire.

2. Ticket SLA Escalation

Support tickets that sit quietly become angry customers. A scheduled workflow can scan open tickets, measure how long they have been untouched, and escalate the stale ones. Try: “Create a scheduled workflow that runs every hour, finds tickets with status Open untouched for more than 24 hours, sets their priority to High, and emails the support lead with the list.” The agent will define “untouched” precisely — updated-at timestamp versus new comments — so the rule matches how your team actually works.

3. Webhook Intake from External Forms

Contact forms on your website, payment notifications, partner systems — all of them can push into NocoBase through a webhook trigger. The agent can create the endpoint, map the incoming JSON to collection fields, and add validation. Say: “Add a webhook workflow that receives form submissions from our website and creates a Lead with name, email, and message, rejecting any payload missing an email.” It will show you the exact URL and payload format to hand to whoever runs the other system, and log failures so nothing silently drops.

4. Weekly Report Email

Managers like a Monday digest: new customers, revenue, open tickets. A scheduled workflow can run an aggregation query and email the result on a cron schedule. Ask: “Every Monday at 8am, email me a report with the count of orders created last week, their total value, and the five oldest open deals by stage.” The agent writes the query, builds the email template, and can run it on demand first so you check the numbers before the schedule goes live. Honest note: complex layouts take iteration — start with a clean text table.

5. Round-Robin Lead Assignment

When a new lead arrives, someone has to pick it up. Round-robin assignment spreads the load fairly without a daily argument. The workflow computes whose turn it is and stamps the lead. Try: “When a Lead is created with no owner, assign it round-robin across the sales team role and send the owner a notification.” The agent will track assignment state somewhere sensible — a counter field or a small config collection — and handles the edge case of people on leave by reading from the active members only.

6. Low-Stock Alerts

Inventory runs out when nobody is watching the number. A scheduled workflow compares stock levels against a reorder threshold and raises the alarm before you hit zero. Say: “Each night, find products where stock quantity is below reorder threshold, create a Restock task assigned to the warehouse role, and email a summary.” The agent adds the threshold field if missing, decides whether partial stock across locations counts, and can include supplier details on the task so ordering is one step.

7. Conditional Two-Stage Approval

Small expenses need one approver; big ones need two. Branch nodes make the workflow decide based on record values. Ask: “Route expense approvals so amounts under 500 need only the manager, amounts 500 and above go to the manager then finance, and anything over 5000 also notifies the CEO but still only needs the two approvals.” The agent will lay out the branches, set the thresholds, and test one expense in each range so you can see the paths work. This is the kind of flow that is miserable to debug in a visual editor and quick to verify in chat.

8. Sync Records to an External System

NocoBase is often the front office, but accounting or shipping lives elsewhere. The HTTP request action pushes records to external APIs when things change. Try: “When an order is marked Paid, send its id, customer email, and total to our accounting API at this endpoint with our API key, and retry once if it fails.” The agent stores credentials in environment variables rather than the workflow definition, logs the external system’s response onto the record, and tells you honestly if the target API’s docs are unclear.

9. On-Create Follow-Up Tasks

New customer signed? There is a checklist: welcome email, onboarding call, data enrichment. One workflow can fan a single event out into several actions. Say: “When a Customer is created, create three tasks — welcome call in 2 days, send onboarding email now, verify billing details in 5 days — and assign them to the customer’s owner.” The agent sets due dates relative to the trigger, handles the case where the owner field is empty by falling back to a default user, and you can adjust the checklist by editing one workflow instead of three.

10. Auto-Number Records with Smart IDs

Humans type INV-0042 and INV-42. Computers should not. A create-triggered workflow assigns sequential, formatted identifiers so records stay sortable and greppable. Ask: “When a Quote is created, assign a quote number like Q-2026-0001 that increments per year and never reuses a number, even if records are deleted.” The agent implements the counter so gaps from deletions do not cause collisions, pads the digits, and backfills existing quotes on request. It sounds trivial until the day you search for an invoice and find four formats of it.

Workflows reward starting small: one trigger, one action, tested, then grown. Your agent can draft the whole flow, explain each node it added, and rerun tests until the behavior matches your words. When you are ready to try them on a live server, see NocoBase on OpenSysLab.