Workflow Automation Templates: 15 Ready-to-Use Workflows

TL;DR:

Each template defines the trigger, conditions, actions, and exception handling so you can adapt it to your specific tools

Templates are organized by department: finance (3), HR (3), sales (3), marketing (3), IT and operations (3)

Start with the template closest to your highest-friction process and customize for your tools and rules

Every template works with no-code platforms like Zapier, Make, Power Automate, or n8n

These 15 templates describe the logic of common automated workflows: what triggers them, what conditions route them, what actions they perform, and how they handle exceptions. Each is platform-agnostic: adapt the logic to whichever tool you use. For platform selection, see our no-code workflow automation guide. For implementation methodology, see our step-by-step playbook.

Finance Templates

1. Invoice Approval Routing

Trigger: Invoice received (email attachment or upload). Conditions: If amount under $1,000, auto-approve. If $1,000-$10,000, route to department head. If over $10,000, route to department head then VP. Actions: Extract invoice data, match against PO, route to approver with context, send reminder at 24 hours, escalate at 48 hours. Exception: Unmatched invoices route to AP team for manual review.

2. Expense Report Processing

Trigger: Expense report submitted. Conditions: Validate each line item against policy (per-diem limits, approved categories, receipt requirements). Actions: Flag violations with specific explanations, route compliant reports to manager, queue approved reports for reimbursement batch. Exception: Reports with missing receipts return to submitter with a specific list of what’s needed.

3. Payment Reminder Sequence

Trigger: Invoice due date passes with payment status unpaid. Actions: Day 1: send first reminder email. Day 7: send second reminder with invoice attached. Day 14: send final notice with escalation warning. Day 21: notify account manager for personal follow-up. Exception: Invoices from customers with active disputes skip the reminder sequence and route to the dispute resolution workflow.

HR Templates

4. Employee Onboarding Sequence

Trigger: New hire start date is 14 days away. Actions: Day -14: IT provisioning request. Day -7: manager checklist sent. Day -3: welcome email to new hire with logistics. Day 0: orientation calendar invites created. Day 30/60/90: manager check-in reminders. Exception: If IT provisioning isn’t confirmed by day -3, escalate to IT manager.

5. PTO Request and Approval

Trigger: Employee submits leave request. Conditions: Check accrued balance (reject if insufficient). Check team coverage minimums. Check blackout periods. Actions: Route to manager with coverage impact summary. If approved, update HRIS, block calendar, notify team. Exception: Requests during blackout periods route to manager with override option and business justification requirement.

6. Offboarding Checklist

Trigger: Departure date entered in HRIS. Actions: Immediately: IT deprovisioning ticket with last-day deadline. Day -7: exit interview scheduling prompt to manager. Day -3: equipment return checklist to departing employee. Last day: final payroll trigger, benefits termination, access revocation confirmation. Exception: If access revocation isn’t confirmed by end of last day, alert security team.

Sales Templates

7. Lead Scoring and Routing

Trigger: New lead enters CRM (form submission, event registration, content download). Actions: Score based on firmographic data (company size, industry) and behavioral signals (pages visited, content consumed). Route above-threshold leads to assigned rep based on territory. Route below-threshold leads to nurture sequence. Exception: Leads from existing customers route to the account manager, bypassing the scoring model.

8. Deal Stage Notifications

Trigger: Opportunity stage changes in CRM. Conditions: If moved to “Proposal,” notify legal for contract preparation. If moved to “Negotiation,” notify finance for pricing approval. If moved to “Closed Won,” trigger customer onboarding workflow. Exception: If moved to “Closed Lost,” trigger loss analysis survey to the sales rep and notify sales manager.

9. Follow-Up Reminder Sequence

Trigger: Sales call or meeting logged in CRM. Actions: Day 1: send meeting summary email to prospect (drafted by template, personalized with meeting notes). Day 3: follow-up with relevant case study or resource. Day 7: check if prospect has engaged (opened emails, visited pricing page). If engaged, alert rep for personal outreach. If not, add to drip sequence. Exception: If prospect replies to any email, remove from the automated sequence and alert the rep.

Marketing Templates

10. Content Approval Pipeline

Trigger: Content draft submitted for review. Actions: Route to subject matter expert for accuracy review (SLA: 48 hours). Upon SME approval, route to editor for final review (SLA: 24 hours). Upon editorial approval, schedule for publication on target date. Exception: If any reviewer misses their SLA, send reminder. If 72 hours pass, escalate to their manager.

Trigger: New blog post published (RSS feed or CMS webhook). Actions: Generate platform-specific social posts (LinkedIn format, X format). Schedule across a distribution calendar (day 0, day 3, day 7, day 14). Track engagement data back to a reporting dashboard. Exception: Posts about sensitive topics (layoffs, legal, crises) skip auto-publishing and route to communications for manual review.

12. Webinar Follow-Up Sequence

Trigger: Webinar ends (event platform webhook). Conditions: Segment attendees vs. registrants who didn’t attend. Actions: Attendees: send recording plus key takeaways email, then a related resource 3 days later, then a meeting scheduling link 7 days later. No-shows: send “sorry we missed you” with recording link, then a follow-up resource 5 days later. Exception: Attendees who asked questions during the webinar get flagged for personal follow-up from the presenter.

IT and Operations Templates

13. Help Desk Ticket Triage

Trigger: Support request submitted (email, form, or portal). Actions: Categorize by content analysis. Assign priority based on impact and urgency. Route common requests (password resets, software installations) to automated resolution. Route complex issues to appropriate tier with user context (equipment, recent changes, past tickets). Exception: Tickets from VIP users (executives, board members) bypass standard triage and route directly to senior support.

14. Vendor Onboarding

Trigger: New vendor approved. Actions: Send documentation request (W-9, insurance certificates, banking details). Track document submission against deadlines. Route compliance documents for review. Create vendor record in ERP upon approval. Set annual recertification reminders. Exception: Vendors who haven’t submitted required documents within 14 days receive escalating reminders. At 30 days, the vendor approval is suspended pending documentation.

15. Incident Response Escalation

Trigger: Monitoring alert (system down, security event, performance degradation). Actions: Create incident ticket with severity classification. Notify on-call engineer. Start SLA clock. If no acknowledgment in 15 minutes, escalate to next responder. If not resolved within SLA, escalate to team lead with full timeline. Post-resolution: trigger root cause analysis template. Exception: Critical severity incidents (production down, data breach) bypass the 15-minute wait and immediately page the on-call engineer plus the team lead simultaneously.

How to Use These Templates

Pick the template closest to your highest-friction process. Customize the triggers, conditions, thresholds, and routing rules for your specific tools and business rules. Build incrementally: implement the trigger and first two actions, test, then add the remaining steps. Let the automation run for two weeks before expanding.

For real-world examples with measurable outcomes, see our 20 workflow automation use cases. For platform selection, see our workflow automation tools comparison. For the complete implementation methodology, see our step-by-step playbook.

Frequently Asked Questions

Can I use these templates with any platform?

Yes. The templates describe the logic (triggers, conditions, actions, exceptions), not the platform-specific configuration. Adapt the logic to Zapier, Make, Power Automate, n8n, or any other workflow automation tool. Most platforms also offer their own template libraries that you can combine with these logical blueprints.

Which template should I start with?

Whichever addresses your highest-friction process. For most organizations, that’s Template 1 (invoice approval) or Template 4 (employee onboarding). For sales teams, Template 7 (lead routing). For IT teams, Template 13 (ticket triage).

How much customization do these templates need?

The logical structure (trigger-condition-action-exception) translates directly. You’ll need to customize: specific threshold values (dollar amounts, time limits), routing rules (who approves what), connected applications (your specific CRM, accounting tool, HR system), and notification channels (email, Slack, Teams). Expect 30 to 60 minutes of customization per template.