Free Workflow Automation Templates: 25 Workflows to Steal in 2026

Most small businesses do not have an automation problem -- they have a starting-point problem. Every founder and ops lead has a vague list of "things we should automate" that never makes it onto a sprint, partly because the blank-canvas of a no-code builder is intimidating, partly because nobody has time to design a workflow from scratch.

This post solves that. Below are 25 workflow templates -- five each across Sales, Customer Success, Billing, Marketing, and Ops -- that cover roughly 80% of what a small business needs to automate. Each one is presented as a copy-paste recipe: the trigger, the conditions to skip on, the actions to fire in order, and an estimate of time saved per week. Steal the ones that match your business, ignore the rest, and ship them in any order.

You do not need a developer. You do not need an integration platform sitting between your tools. You need an afternoon and the willingness to build the first one.

The fastest way to fail at automation is to try to deploy all 25 templates at once. The fastest way to succeed is to deploy one, learn from it, and move to the next.

1. Pick the one that affects revenue or owner time first. For most teams that is the sales lead routing or the dunning sequence -- both pay for themselves in the first month. Save the "nice to have" templates for later.

2. Build it in 30 minutes, not three days. These templates are intentionally simple. The first version should fire end-to-end before lunch. Iterate after you see real data.

3. Test with a real record before going live. Run the workflow against one contact, one invoice, or one ticket. Confirm the email lands, the field updates correctly, and the timing makes sense.

4. Watch the logs for a week. Every automation platform shows execution history. Skim the first 50 runs to catch the edge cases your initial conditions missed.

5. Move to the next template. A reasonable cadence is one new workflow per week. By the end of a quarter, you have 10-12 of these running, and you have learned enough to design your own.

Now the templates.

Trigger: Contact created in the CRM with `source = web_form`.

Conditions: Skip if the contact already exists as an active customer or open deal owner. Skip if the email looks invalid (bounces, role-based addresses like info@, plus tags you exclude).

Actions (in order): 1. Look up territory/round-robin owner from a saved rule. 2. Assign the contact to that sales rep. 3. Send a templated welcome email within 60 seconds (speed-to-lead is the single biggest conversion lever). 4. Create a follow-up task for the rep due in 24 hours. 5. Add the contact to a "Warm Leads" segment in the marketing app.

Estimated time saved: 2-4 hours per week for a team handling 30+ inbound leads, plus a 15-30% lift in qualified leads from the same traffic. Manual routing loses leads in the gap between "form submitted" and "someone got around to it."

Trigger: Deal stage changes to `Closed Won` in the CRM.

Conditions: Skip if the deal is flagged as a renewal or upgrade (those use a separate workflow). Require a primary contact email and an assigned customer success owner.

Actions (in order): 1. Move the contact's status from `prospect` to `customer`. 2. Notify the assigned CS owner in the team messenger with the deal record link. 3. Send a "welcome to the team" email to the customer with the CS owner introduced by name. 4. Create three onboarding tasks for the CS owner: kickoff call, week-one check-in, 30-day review. 5. Auto-book a 30-minute kickoff meeting through the bookings app, sending the customer three available time slots.

Estimated time saved: 30-45 minutes per closed deal. The bigger payoff: customers who get a same-day handoff from sales to CS retain at materially higher rates than ones who wait three days for a kickoff email.

Trigger: A quote is sent (status changes to `sent`) on a deal in the CRM or sales app.

Conditions: Skip if the prospect has already replied to the quote thread. Skip if the deal stage is back to `negotiation` (means the rep is already actively engaged).

Actions (in order): 1. Wait 48 hours. 2. Check if there is any inbound activity on the deal (email reply, viewed receipt, click on the quote link). 3. If no activity, send a polite follow-up email referencing the quote: "Wanted to make sure this didn't get buried. Happy to walk through any of the line items or adjust scope." 4. Create a task for the rep to call the prospect the next morning. 5. If still no response after another 5 days, move the deal to a `stalled` stage for re-engagement.

Estimated time saved: 1-2 hours per week, plus a meaningful close-rate lift. Most quotes that go cold do so because the rep gets pulled into the next deal and forgets to follow up by day three.

Trigger: Daily scheduled job that scans contacts in the CRM with `lastActivity` older than 30 days and `status = lead`.

Conditions: Skip contacts marked as `do not contact`, contacts already in another active sequence, and contacts who unsubscribed.

Actions (in order): 1. Add the contact to a "Cold Lead Re-Engagement" segment. 2. Send a soft re-engagement email -- no pitch, just a useful resource (recent blog post, customer story, or product update). 3. Wait 7 days. If the contact opened the email or clicked a link, move them back to `warm lead` and notify the assigned rep. 4. If still no engagement after 14 days, send a second email asking if they want to stay on the list. 5. If no engagement after another 14 days, move them to a `dormant` segment and stop the sequence.

Estimated time saved: 2-3 hours per week of manual list-cleaning, plus the recovery of leads that would otherwise stay buried in the CRM forever. Most teams find 5-10% of cold leads come back warm with a single touch.

Trigger: Daily scheduled job that scans deals where `stageEnteredAt` is older than 14 days and stage is one of `discovery`, `proposal`, or `negotiation`.

Conditions: Skip deals flagged as `long sales cycle` (enterprise deals with explicit timelines). Skip deals where the rep has logged a recent activity within 7 days.

Actions (in order): 1. Notify the deal owner in the team messenger with the deal record, days stalled, and last activity date. 2. Send the same notification via email if the rep has not responded in messenger within 24 hours. 3. Create a task for the rep due tomorrow: "Re-engage [Deal Name] -- 14 days in [Stage]." 4. After 7 more days of no movement, escalate the alert to the sales manager.

Estimated time saved: 1-2 hours per week of manual pipeline review. The bigger payoff: deals that would have quietly died get one more honest push, and the reps who forget to follow up get an objective reminder instead of a manager nag.

Trigger: Contact status changes to `customer` (or a deal moves to `Closed Won`).

Conditions: Customer has a primary contact email. Skip if they are flagged as `enterprise white-glove` (those go to a different sequence with a real human at every step).

Actions (in order): 1. Day 1: Welcome email with login info, the assigned CS owner's name, and what to expect over the next 30 days. 2. Day 3: Walk-through email covering their first three actions in the product or service. 3. Day 7: Check-in email asking what is going well and what is not, with a one-click reply option. 4. Day 14: "Are you stuck?" email with three common quick wins customers hit by week 2. 5. Day 30: Review email summarizing what they have used and inviting feedback. Notify the CS owner internally so they can run the 30-day check-in.

Estimated time saved: 1-2 hours per new customer, plus a measurable lift in retention. The first 30 days of a customer relationship determine 70-80% of their lifetime value -- automation makes that experience consistent regardless of when they signed.

Trigger: A customer responds to a satisfaction survey (CSAT) with a score below 7.

Conditions: Skip duplicate scores from the same customer within 72 hours (one alert per customer per low-score event). Skip if a CS owner already has an open task for the customer.

Actions (in order): 1. Notify the assigned CS owner in the team messenger with the score, the customer name, and any open-text feedback. 2. Create a high-priority task for the CS owner: "Reach out to [Customer] -- CSAT [score]." Due in 24 hours. 3. Tag the customer record with `at-risk` and add them to a watchlist segment. 4. Schedule a follow-up survey 14 days later to measure recovery. 5. If the same customer scores below 7 twice in 30 days, escalate to the head of CS.

Estimated time saved: 30 minutes per low-CSAT response. Bigger payoff: at-risk customers who get a personal outreach within 24 hours of a complaint churn at roughly half the rate of customers who get a generic thank-you and nothing else.

Trigger: Subscription `renewalDate` is exactly 60 days away.

Conditions: Subscription is on auto-renewal (skip month-to-month or already canceled). Customer has been onboarded for at least 90 days (skip new customers in their first quarter).

Actions (in order): 1. Calculate an engagement score: usage frequency, support ticket volume, satisfaction scores, and feature adoption. Weight per your model. 2. If score is `healthy`, add to a standard renewal sequence and no human action needed. 3. If score is `at-risk`, notify the CS owner with a one-page summary of the customer's recent activity and any open issues. 4. Create a task for the CS owner: "Renewal save call with [Customer]" due within 14 days. 5. Send the customer a value-summary email (what they have used, key wins) with a calendar link to book a check-in if they want one.

Estimated time saved: 2-3 hours per week of manual at-risk review. Bigger payoff: 5-15% improvement in net retention, depending on your starting baseline.

Trigger: A support ticket has `status = open` and `firstResponseAt` is null after 24 hours (or after the SLA configured for that customer's plan tier).

Conditions: Skip tickets marked as `pending customer reply`. Skip tickets created by team members (internal). Skip tickets in queues that are explicitly off-hours (e.g., enterprise after-hours queue).

Actions (in order): 1. Notify the assigned agent in the messenger with the ticket link and minutes overdue. 2. After 1 more hour, if still no response, notify the support team lead. 3. After another 2 hours, escalate to the head of support and tag the ticket as `breached SLA`. 4. Send the customer an automated apology email acknowledging the delay and committing to a response within 4 hours. 5. Log the breach for weekly reporting so the team can identify patterns.

Estimated time saved: 1-2 hours per week. Bigger payoff: SLA breaches drop dramatically once agents know an objective timer is watching, and the customers who do get caught in a breach hear from you proactively instead of finding out by waiting in silence.

Trigger: A customer responds to an NPS survey with a score of 0-6 (detractor).

Conditions: Skip duplicate detractor responses within 60 days. Skip if the customer has churned (post-cancellation feedback uses a different sequence).

Actions (in order): 1. Notify the assigned CS owner in the messenger with the score, any open-text comment, and the customer's last 30 days of activity. 2. Create a high-priority task for the CS owner: "Detractor follow-up with [Customer]" due in 48 hours. 3. Send the customer a personal email from the CS owner: "Saw your NPS response and want to make this right -- when can we talk?" 4. Wait 14 days, then send a second survey asking specifically about the issue they raised. 5. If the second survey score improves to 7+, mark the recovery in the customer record. If not, flag for a churn-risk review.

Estimated time saved: 30-45 minutes per detractor. Bigger payoff: detractors who get a personal call within 48 hours convert to passives or promoters at rates 3-5x higher than detractors who get nothing.

Trigger: Invoice `dueDate` was 7 days ago and `status` is still `unpaid`.

Conditions: Invoice is not flagged as disputed. Customer is not on an approved payment plan. Amount is above a minimum threshold (skip $5 invoices).

Actions (in order): 1. Send polite Reminder 1 with a one-click pay link. 2. Wait 7 days. If still unpaid, send firmer Reminder 2 and add a 1.5% late fee per your stated terms. 3. Wait 7 days. If still unpaid, send Reminder 3, flag the customer record as `at-risk`, and notify the account owner. 4. Wait 7 more days. If still unpaid, pause new orders or service for the account and escalate to the owner for a personal call. 5. Log the full dunning history on the invoice and customer record for accounting.

Estimated time saved: 2-3 hours per week if you currently chase invoices manually, plus a 20-40% improvement in days-sales-outstanding (DSO). Cash flow is the number one reason small businesses fail; dunning is the cheapest insurance against it.

Trigger: A successful payment is recorded in the billing app (invoice paid, subscription charge succeeds, or one-off charge clears).

Conditions: Skip refunds and chargebacks. Skip duplicate webhooks. Skip if the customer has opted out of marketing emails (still send the receipt, just not the cross-sell).

Actions (in order): 1. Send a clean receipt email with the invoice PDF attached and a link to the customer portal. 2. Wait 24 hours. 3. Look up the customer's current product mix and identify the most relevant cross-sell or upsell. 4. Send a soft cross-sell email -- not pushy, framed as "customers like you also tend to use [X]" with a clear opt-out. 5. Log the cross-sell touch on the customer record so the next sequence does not repeat too soon.

Estimated time saved: 30-60 minutes per week. Bigger payoff: most teams find 1-3% of receipt-driven cross-sell emails convert -- which adds up fast at any meaningful payment volume.

Trigger: A payment fails (card declined, expired, or insufficient funds) on a subscription or invoice.

Conditions: Skip if this is the first hour after the failure (give the processor's automatic retry a chance). Skip if the failure reason is `disputed` (chargebacks use a separate flow).

Actions (in order): 1. Wait 1 hour, then attempt the charge again. 2. If still failing, send a friendly email to the customer: "Your payment didn't go through -- can you update your card?" with a one-click link to the billing portal. 3. Wait 3 days. Retry the charge again. 4. Send Reminder 2 with a slightly more urgent tone if still failing. 5. After 7 days of failed retries, pause the service and notify both the customer and the account owner. Continue retrying weekly for up to 30 days before final cancellation.

Estimated time saved: 2-3 hours per week. Bigger payoff: most failed payments are resolved within 7 days when there is an automated dunning loop, versus 30-60 days of manual back-and-forth without one. Recovered revenue from involuntary churn is one of the highest-ROI automations in the entire stack.

Trigger: Subscription `status` changes to `canceled` (immediate or scheduled).

Conditions: Skip cancellations triggered by failed payment dunning (those get a separate flow). Skip duplicate cancellations within 24 hours.

Actions (in order): 1. Send an immediate exit survey: one screen, three questions, no required fields. Ask the reason, what would have changed their mind, and whether they would recommend you. 2. If the cancellation reason is `too expensive` or `not enough value`, send a retention offer 24 hours later -- a discount, a downgraded plan, or an extension. Tag the customer for a save-call attempt. 3. If the reason is `going to a competitor`, route the survey response to the head of product so the team can review patterns. 4. Send a polite "sorry to see you go -- door is open" email 7 days after cancellation with no pitch and a clear path back. 5. After 60 days, send a single "are you ready to try us again" win-back email with any new features shipped since they left.

Estimated time saved: 1-2 hours per cancellation. Bigger payoff: 5-15% of canceled customers come back when there is a retention offer at the right moment, and the survey data drives product priorities for the next quarter.

Trigger: A refund is issued in the billing app (full or partial).

Conditions: Skip refunds tied to fraud cases or billing errors that are already explained over a personal call.

Actions (in order): 1. Send a clear refund-confirmation email with the amount, the original transaction, and the expected timing on the customer's bank statement. 2. Wait 24 hours, then send a follow-up survey: "What could we have done differently?" 3. Notify the assigned CS or support owner that the customer received a refund, with the original ticket or invoice attached. 4. If the refund reason is a quality issue, create a task for the team lead to review the underlying root cause. 5. Tag the customer record with `refund_issued` and the date so future sequences can be aware.

Estimated time saved: 20-30 minutes per refund. Bigger payoff: customers who receive a clean, fast refund and a thoughtful follow-up survey often become more loyal than customers who never had an issue. The refund is not the problem -- silence after a refund is.

Trigger: A new newsletter subscriber is added (web form, lead magnet, or import).

Conditions: Skip role-based emails (info@, support@). Skip if the email is already an active customer with a different sequence already running.

Actions (in order): 1. Send a welcome email immediately with a brief intro to your brand and one piece of high-value content (your best post, a free template, or a primer guide). 2. Wait 7 days. 3. Send a Day-7 educational email -- a single useful idea, no pitch. The goal is to train the subscriber to expect value, not promotion. 4. Tag the subscriber with `nurture_active` so they do not get pulled into other sequences before they are warm. 5. After Day 21, if the subscriber has opened both emails, move them to a deeper nurture segment. If not, keep them on the regular newsletter cadence.

Estimated time saved: 30-60 minutes per week. Bigger payoff: subscribers who get a clear two-email welcome unsubscribe at materially lower rates and convert to leads at higher rates than subscribers who land in the general newsletter cold.

Trigger: Contact downloads a gated whitepaper, ebook, or report.

Conditions: Skip if the contact is already an active customer or open deal owner. Skip if they have already received this specific nurture sequence in the last 90 days.

Actions (in order): 1. Day 0: Deliver the asset with a thank-you email and a brief intro to a related second resource. 2. Day 3: Send a case study email featuring a customer who solved the problem the whitepaper addresses. 3. Day 7: Send a "how to apply this" email with three actionable steps the reader can take this week. 4. Day 14: Send a soft pitch email introducing the product or service that ties to the whitepaper topic. Include a demo link or free trial. 5. Day 21: Final email: ask if they want to talk to a human, with a calendar booking link. Tag the contact based on engagement -- engaged contacts move to a sales-ready segment, unengaged contacts to a long-term nurture list.

Estimated time saved: 1-2 hours per week. Bigger payoff: a structured 5-email nurture converts gated-asset downloads to qualified leads at 2-4x the rate of single-touch follow-up.

Trigger: A registration is recorded for a scheduled webinar.

Conditions: Skip duplicate registrations from the same email. Skip if the webinar has been canceled or rescheduled (those use a separate notification flow).

Actions (in order): 1. Send an immediate confirmation email with the calendar invite, the join link, and one piece of pre-reading. 2. 24 hours before the webinar: send a reminder email with the join link and a one-line teaser. 3. 1 hour before: send a final "starting soon" email. 4. After the webinar ends: send a thank-you email to attendees with the recording, slides, and a relevant next step (demo, free trial, or follow-up resource). 5. 24 hours after: send a separate email to no-shows with the recording and an apology for missing them, with an option to book a 1:1 instead.

Estimated time saved: 1-2 hours per webinar. Bigger payoff: webinar attendance rates lift 15-30% with a proper reminder cadence, and the post-attend follow-up converts attendees to opportunities at meaningfully higher rates than a single thank-you note.

Trigger: A contact has opened 5 or more marketing emails within the last 14 days.

Conditions: Skip contacts who are already in an active sales sequence. Skip if they are an existing customer with an assigned CS owner (different signal entirely).

Actions (in order): 1. Tag the contact as `engaged` in the marketing app. 2. Move them from the general nurture list to a sales-ready segment. 3. Notify the assigned sales rep (or the round-robin owner if none assigned) in the team messenger: "[Contact] is heating up -- 5+ opens in 14 days. Consider a personal outreach." 4. Create a task for the rep due in 48 hours: "Send a personal note to [Contact]." 5. Pause automated marketing emails to the contact for 14 days while the human outreach plays out.

Estimated time saved: 30-60 minutes per week. Bigger payoff: the engaged-but-untouched lead is one of the most expensive missed opportunities in any marketing system. A small messenger nudge to the right rep at the right moment converts these into opportunities at notable rates.

Trigger: A customer submits a referral through your referral form or shares a referral link that converts to a new account.

Conditions: Skip duplicate referrals (same referrer + same referred contact within 30 days). Skip if the referrer is no longer an active customer.

Actions (in order): 1. Send a thank-you email to the referrer with a confirmation of the reward (credit, discount, or whatever you offer) and an estimated timeline. 2. Send a welcome email to the referred contact noting who referred them and offering a small first-time discount. 3. Apply the reward to the referrer's account (account credit, coupon code, or queued payout). 4. Notify the assigned CS owner so they can mention the referral on the next check-in call. 5. After 30 days, if the referred contact is still an active customer, send the referrer a final "your referral stuck -- thanks again" email and update their lifetime referral count.

Estimated time saved: 30 minutes per referral. Bigger payoff: a referral program with same-day acknowledgment generates 3-5x more repeat referrals from the same customers than one with manual processing and slow rewards.

Trigger: A new employee record is created in the HR app or a hiring pipeline stage moves to `Hired`.

Conditions: Start date is set. Manager and team are assigned. Role-based access profile is selected.

Actions (in order): 1. Provision accounts across all the apps the new hire needs based on their role profile -- CRM, helpdesk, field service, messenger, mail, plus role-specific apps. On a unified platform this is a single role assignment; on a stitched-together stack it is 8-15 separate provisioning calls. 2. Send a Day-1 welcome email with login info, the first-week schedule, and a link to the team handbook. 3. Day 3: Send a check-in email from the manager. 4. Day 7: Send a "how is your first week going" email with a one-click feedback link. 5. Day 30: Schedule a check-in meeting with the manager via the bookings app and create training tasks in the project management app for required learning modules.

Estimated time saved: 4-6 hours per new hire. Bigger payoff: employee turnover in the first 90 days costs 50-75% of the role's salary in lost productivity. The single biggest preventable cause of early churn is a chaotic first week -- automation makes the first week consistent regardless of who is on the hiring side.

Trigger: An employee submits a time-off request in the HR app.

Conditions: Skip if the employee has insufficient PTO balance (route to a different exception flow). Skip if the dates conflict with a blackout period (open the request for explicit override approval).

Actions (in order): 1. Notify the manager in the team messenger with the request details and a one-click approve/deny. 2. If approved, create a calendar block on the employee's work calendar and add to the team's shared time-off calendar. 3. Send the employee a confirmation email with the approved dates and the team coverage plan field for them to fill in. 4. Update the employee's status in the messenger and any other team status surfaces during the time-off window. 5. Notify the team channel one business day before the time-off starts as a coverage reminder.

Estimated time saved: 20-30 minutes per request. Bigger payoff: the time-off request that sits in the manager's inbox for three days, or the team that gets surprised by a coworker's absence, are both fixed by the same workflow.

Trigger: An employee submits an expense in the expense or accounting app.

Conditions: Skip duplicate submissions (same amount, vendor, date within 24 hours). Skip if the expense is below an auto-approval threshold (small expenses can route directly to accounting).

Actions (in order): 1. Run a basic policy check: amount under per-category limit, receipt attached, date within submission window. 2. Route to the manager in the team messenger with one-click approve, deny, or request-info actions. 3. On approval, auto-categorize using the GL code mapping for the vendor or category, and post to the accounting app. 4. Notify the employee with the status (approved, denied with reason, or pending more info). 5. If approved and reimbursable, queue the payment in the next payroll or reimbursement run.

Estimated time saved: 1-2 hours per week for a 10-person team. Bigger payoff: expenses move from "submit and wait two weeks" to "submit and resolved by end of day," which is a quietly significant employee experience win.

Trigger: Daily scheduled job that scans documents (licenses, certifications, contracts, insurance policies) with `expiresAt` exactly 30 days away.

Conditions: Skip documents flagged as `archived` or `replaced`. Skip if a renewal task has already been created.

Actions (in order): 1. Send an email reminder to the document owner: "Your [license/cert/policy] expires on [date] -- 30 days left." Include a link to the renewal process and any required prerequisites. 2. Create a task for the owner due 14 days before expiration: "Renew [Document]." 3. Notify the team lead or compliance owner in the messenger so they have visibility. 4. At 14 days: send a more urgent reminder. At 7 days: escalate to the team lead. 5. At 0 days (expiration): flag the document as `expired`, alert the compliance owner, and pause any workflows that depend on the document being current (work orders, customer assignments, etc.).

Estimated time saved: 1-2 hours per month, plus enormous downside protection. Expired licenses or certs cause real operational risk -- this workflow makes that risk effectively impossible to ignore.

Trigger: Scheduled job that runs every Monday at 7:00 AM in your business timezone (cron `0 7 * * 1`).

Conditions: Data sources are healthy (each app has reported in the last 24 hours). Recipients list is current.

Actions (in order): 1. Pull this week's KPIs from across your stack -- new leads, deals closed, revenue, MRR, support tickets opened/resolved, NPS, invoice DSO, plus any custom metrics. 2. Have an AI assistant generate a 200-word executive summary highlighting wins, warnings, and items needing attention. 3. Email the digest to the leadership team with the AI summary at the top and the raw numbers below. 4. Post a condensed version (top three numbers + the summary) to the leadership channel in the team messenger. 5. Archive the digest to a shared drive folder so the team has a running history.

Estimated time saved: 2-3 hours per week. Bigger payoff: most small business owners know they should review their numbers every Monday and skip it because pulling the data takes longer than reviewing it. An automated digest in your inbox at 7 AM creates a habit that manual dashboard-checking never will.

Every template above maps cleanly to the Deelo Automation app. The platform ships with 60+ first-party templates including all 25 of these, pre-wired to the relevant apps in the Deelo ecosystem -- CRM, invoicing, helpdesk, field service, HR, marketing, messenger, and the rest.

The build pattern is the same for every template:

1. Pick the trigger from the trigger library (Contact Created, Invoice Overdue, Subscription Renewing, Ticket Created, etc.). 2. Add condition nodes as needed -- skip rules, segment filters, or branch points. 3. Chain action nodes -- send email, create task, update field, notify channel, schedule meeting, run AI summary. 4. Wire in waits or scheduled steps for delayed actions (Day 3 follow-up, 7-day reminder, 30-day check-in). 5. Test with one record before flipping to live, then watch the execution logs for the first week.

Because Deelo is one platform with one data layer, the automations work across apps without integration plumbing. There is no Zapier-style middleware sitting between the trigger and the action, no separate billing for the automation layer, and no broken integrations when one of the underlying APIs changes upstream. Every workflow uses the same builder, the same data, and the same logs.

Deelo plans start at $19/seat/month for Starter (which includes the automation engine and most apps used in this guide), $39 for Business, and $69 for Enterprise. The free tier supports light usage if you want to validate before paying.