15 Workflow Automations That Save Solopreneurs 5 Hours a Week

Builder · Level 2 of 3

Some links below are affiliate links. If you sign up through them, Automate My Life may earn a commission at no extra cost to you, which helps keep the site free. Only tools worth using get a recommendation here.

A workflow automation is a saved rule that watches for something to happen, then does the next steps for you without you touching them. Set up the right 15 and a solo operator can hand off five or more hours of repetitive work a week: lead capture, invoicing chase-ups, content reposting, client onboarding, and the small admin that quietly eats a day. Below are 15 concrete recipes, grouped by the job each one does, with the trigger and the action spelled out so you can copy them in an afternoon. You build them in a no-code automation platform: Zapier, Make, or n8n. You do not need to write code, and you do not need all 15. Start with the two that hurt most.

What you need before you build anything

Every recipe here runs on a no-code automation tool that sits between your apps and moves data between them on a trigger. The three most common are Zapier, Make, and n8n. Zapier is the most beginner-friendly and has the widest app library. Make uses a visual canvas and tends to cost less per task at volume. n8n is open source and can be self-hosted if you want to run automations on your own server. All three are built around the same idea: a trigger (the event that starts the workflow) and one or more actions (what happens next). Pricing and free-tier limits change often, so check each tool’s own pricing page before you commit; the recipes below work on any of the three.

One habit to set now: name every automation clearly (for example, “Form lead to CRM and Slack”) and turn it on for one real record before you trust it with everything. The point is to remove work, not to create a silent failure you find out about three weeks later.

Lead capture and sales automations

These move a new lead from “filled out a form” to “in your system and contacted” without you copying anything by hand.

#	Automation	Trigger → Action
1	Form lead into your CRM	New form response (Google Forms, Typeform) → create or update a contact in your CRM
2	Instant new-lead alert	New CRM contact → post a message to a Slack or Telegram channel
3	Auto welcome reply	New form response → send a templated email from Gmail or your mailer
4	Book-a-call follow-through	New Calendly or Cal.com booking → add to calendar, create a CRM deal, send prep notes

Recipe 1 is the one most solo operators should build first, because lead data entered by hand is lead data that eventually gets dropped. Here it is fully worked.

Worked example: turn a form submission into a contact, an alert, and a welcome email

1. Create a new workflow (a “Zap” in Zapier, a “Scenario” in Make). Set the trigger to your form tool, event New Form Response, and pick the specific form.
2. Add action one: your CRM’s Create or Update Contact. Map the form’s email field to the contact email so re-submissions update the same record instead of making duplicates.
3. Add action two: Send Channel Message in Slack, pointed at your #leads channel, so a new lead pings you in real time.
4. Add action three: Send Email in Gmail with a short templated reply so the lead hears back within seconds.
5. Test with one real submission, confirm all three actions fired, then turn the workflow on.

Copy this field map and adapt the names to your own apps:

Trigger: Google Forms — New Form Response

Action 1 — CRM: Create or Update Contact
  email        = {{form.email}}
  first_name   = {{form.name}}
  lead_source  = "website form"

Action 2 — Slack: Send Channel Message (#leads)
  text = "New lead: {{form.name}} ({{form.email}}) — {{form.message}}"

Action 3 — Gmail: Send Email
  to      = {{form.email}}
  subject = "Thanks for reaching out"
  body    = "Hi {{form.name}}, thanks for your message. I'll reply personally within one business day."

That single workflow replaces four manual steps every time a lead arrives. The same trigger-action pattern carries the rest of the list, so once you have built one, the others go faster.

Invoicing and money automations

Getting paid is mostly a chase problem. These recipes do the chasing and the record-keeping so you do not have to remember either.

#	Automation	Trigger → Action
5	Auto-invoice on closed deal	CRM deal marked Won → create and send an invoice in your billing tool
6	Overdue invoice reminder	Invoice past due date (scheduled check) → send a polite reminder email
7	Log every payment	New payment received → append a row to a Google Sheet and post to your accounting tool

Recipe 6 uses a scheduled trigger instead of an event: the automation runs every morning, looks for invoices past their due date, and emails a reminder. It is the closest thing to a polite assistant who never forgets and never feels awkward sending the third nudge.

Content repurposing automations

Publishing once and reposting everywhere by hand is the kind of recurring work that automation was made for. These keep your channels fed from a single source.

#	Automation	Trigger → Action
8	New post to social queue	New blog post in your RSS feed → draft a post to your social scheduler
9	Video to newsletter draft	New video published → create a draft email with the title, link, and notes
10	Saved idea to content board	New starred note or saved link → add a card to your content planning board

Keep a human in the loop for these. Have the automation create a draft rather than publish directly, so you approve the wording before it goes out. You get the time back without giving up the final say.

Client and admin operations automations

The onboarding and file-shuffling work that comes with every new client is highly repeatable, which means it is highly automatable.

#	Automation	Trigger → Action
11	New client onboarding kit	New deal Won → create a project folder, copy a task template, send a welcome packet
12	Email attachment filing	New email with attachment → save the file to the right cloud folder by sender or subject
13	Meeting notes to tasks	New meeting transcript or note → extract action items and create tasks in your tracker

Recipe 11 is the highest-value one in this group for a service business. A single trigger can stand up the whole onboarding sequence, so the client gets a consistent start every time and you skip the checklist you would otherwise run by hand.

Personal and life automations

The same trigger-action thinking works outside the business. Two recipes that pay off quietly every week:

#	Automation	Trigger → Action
14	Receipts to a tax folder	New email labeled “receipt” → save the PDF to a dated cloud folder and log the amount
15	Weekly review digest	Every Friday (scheduled) → pull the week’s completed tasks and calendar into one summary email

If you want to take this thinking into your home next, the same trigger-action map runs your house too. The starting set is in 20 Home Assistant automations worth setting up first, and a full morning sequence is broken down in how to build a morning routine that runs your house for you.

Which tool should you use: Zapier, Make, or n8n?

Pick based on where you are, not on which is “best.” If you are building your first automation and want the widest set of pre-built app connections, start with Zapier. If you are comfortable with a visual builder and want more control over branching and lower cost as your task volume grows, Make is a strong fit. If you want to self-host, keep your data on your own server, or run a high volume without per-task pricing, n8n is the open-source option. The 15 recipes above are written to be tool-agnostic, so you can move them between platforms later if your needs change. Confirm current plan limits on each tool’s pricing page before you choose, since the free tiers shift.

How to start without breaking anything

• Build one, not fifteen. Pick the recipe tied to the work you most resent doing, and ship that this week.
• Test on one real record. Run a live trigger once and check every action fired before you switch it on for good.
• Keep a human in the loop where judgment matters. Drafts over auto-sends for anything client-facing.
• Watch for duplicates. Map on a unique field like email so re-runs update records instead of multiplying them.
• Name and date your workflows. Future you needs to know what each one does when something changes.

Five hours a week is not one heroic automation; it is a handful of small ones that each remove a recurring chore. Start with the lead-capture recipe, get it running on a real submission, then add the next one when the first has earned your trust. The list is here whenever you are ready to build the next one.

Build the next layer: Automate quarterly tax reminders and set-asides, turn a task dump into a weekly plan with ChatGPT, or browse more step-by-step automation guides.