Workflow automation: the ops definition, then sales

A workflow is a path with an owner

Workflow automation means a repeatable path: something happens (a form, a status change, a clock), software does steps that used to live in someone's head or in a SOP, and a system of record ends in a known state. The point is not 'bots.' The point is that the tenth time a deal is marked Closed Won, provisioning does not depend on who was in Slack that afternoon. IT, finance, support, and sales all have these paths. The tools differ. The shape does not. Open-source builders such as n8n sit in this aisle. LinkedIn sequencers do not.

Good workflow design names the trigger, the happy path, the failure path, and the human exception. If you cannot name the exception ('legal has to look at this,' 'the customer asked for a custom DPA'), you will automate a lie and then staff a person to clean it up. Write the exception first.

What it is not

It is not RPA as a personality. Screen-scraping a vendor's UI because they have no API is a last resort, brittle, and often against that vendor's terms. It is not an AI agent that 'handles email' with no audit trail. It is not a LinkedIn sequencer, even though sequencers contain a workflow (invite, then message). Collapsing every sequence into 'workflow automation' is how you get an n8n graph pretending to be Expandi, or a sequencer pretending to be your CRM.

It is also not a replacement for a process you have not agreed on. Automating a messy handoff between marketing and sales just makes the mess faster. Sit the two teams down. Then draw the graph.

Sales examples that are actually workflows

A lead-gen form in Campaign Manager creates a CRM contact, assigns an owner by territory, and posts a Slack line with the form answers. A LinkedIn reply that a sequencer marked as interested creates a task with the thread link, not a second automated pitch. A closed-won deal creates the customer workspace, the invoice, and a kickoff event. A no-show on the calendar waits one day, then asks the rep to send a human note, not a four-step guilt sequence.

Notice what those examples share: the system of record is the CRM or the calendar, and LinkedIn is an input or an output, not the workflow engine. n8n, Zapier, Make, Workato, and native CRM automation (HubSpot workflows, Salesforce Flow) all compete for this glue. Pick based on who will maintain the graph, where the data must live, and whether you need on-prem.

How to introduce automation without boiling the company

Pick one path that already happens ten times a week and hurts when it fails. Measure the failure (missed follow-up, duplicate contact, forgotten provision). Automate that path. Leave the adjacent paths manual for a month. If nobody can explain the graph in standup, it is too clever. If the graph cannot be paused, it is too dangerous. Workflow automation that cannot be turned off is just a new outage type.