Three n8n workflows worth starting with
A useful first automation moves a small, clear task between systems you already control. These three patterns are deliberately modest: define the input, inspect the output, and keep a person in the loop where a mistake matters.
1. Qualify a new lead without pretending to be a salesperson
Start with a form, webhook, or inbox label. Normalize the submitted name, company, email and request, then send the record to the place your team already reviews work: a spreadsheet, CRM, or a private notification.
- Deduplicate on a stable identifier such as email address or CRM record ID.
- Use explicit rules for routing, such as region, service requested, or a required field.
- Draft an acknowledgement for human review instead of automatically promising price, availability, or a meeting.
2. Turn appointment requests into a reviewable booking queue
Booking automation is most reliable when it checks a real availability source and records the decision. Capture the requested time zone, duration and contact method; look up availability; then create a tentative record or notify the responsible person.
- Make time zone conversion visible in the workflow and test daylight-saving dates.
- Keep the calendar event private or tentative until your confirmation rule is satisfied.
- Log the external event ID so a retry does not create a second booking.
3. Reconcile Stripe payouts into an operations view
A payout workflow can pull Stripe payout and balance-transaction data on a schedule, group it by payout ID, and write a reconciliation row for review. It should not move money, alter a payout, or infer that a bank deposit has cleared.
- Store the Stripe object IDs and the retrieval time with each row.
- Separate gross charges, refunds, fees and net payout so the arithmetic is inspectable.
- Alert on a mismatch; let a person decide how to resolve it.
Use test credentials or dry-run data first. Keep credentials in n8n's credential store rather than workflow JSON. Review every node that sends email, writes a record, or calls a payment API. An imported template is a starting point, not proof that it fits your accounts or process.
A small starter pack, if you want the scaffolding
Weio sells three importable templates for these patterns: lead qualification, appointment booking, and Stripe payout reconciliation. The pack includes a plain-English setup guide and a local dry-run harness. It is not hosted automation, credential setup, or production deployment; you review and test it in your own n8n environment.
Need a workflow built around a particular system? Ask for a fixed-price automation quote.