Business process automation
Stop moving the same information by hand.
I map repetitive business processes and build the workflows between the systems, data and people involved — so routine work moves automatically while important decisions stay controlled.
Where to start
Look for repetition, not technology.
Good automation candidates are rarely hidden. They are the tasks people describe with “every time…” and “first I have to…”. Not every repetitive task is worth automating, but these signals are usually where the useful opportunities are.
Signals worth looking at
- The same information is copied again and again
- Someone watches an inbox for one type of message
- Documents are read by hand and typed into another system
- One system needs information that lives in another
- Follow-up depends on someone remembering the next step
- A spreadsheet exists because two systems do not talk
- People keep checking whether something already exists
- The rules are predictable, but the work is still manual
The best starting point is usually a repetitive process people already understand — not a tool looking for a use case.
What a workflow connects
One process, several systems.
A business process rarely lives in one tool. A workflow picks up the trigger, moves the data between the systems involved and hands the right steps to the right people. What can be connected depends on what each system and file makes available.
Communication
- Forms
- Shared inboxes
- Notifications
- Detect incoming requests
- Extract useful information
- Route messages
- Prepare follow-up
- Trigger the next step
Business systems
- CRM
- Marketing platforms
- Internal tools
- Databases
- Find records
- Create or update data
- Link related records
- Synchronise information
- Trigger actions
Documents and data
- PDFs
- CVs
- Spreadsheets
- Structured files
- Read incoming documents
- Extract structured information
- Validate fields
- Transform data
- Transfer the source file
External services
- APIs
- AI models
- Webhooks
- Third-party platforms
- Exchange data
- Add processing steps
- Classify information
- Connect systems without a native integration
- Continue workflows across tools
In production
A recruitment process that used to start in the inbox.
At Logi-technic, candidate proposals from staffing agencies arrive by email. A recruiter had to connect the email, the CV and later replies, assess the candidate, check records, prepare replies and register the candidate and application in Salesforce.
The workflow now processes the email and supported CV or document attachments, structures the relevant candidate information and uses technical role profiles to support the assessment. The appropriate follow-up is prepared, and when the agency replies, the reply stays connected to the original conversation. Existing records are checked before candidate and application data is created or supplemented in Salesforce/Connexys where appropriate, and the CV is transferred to the relevant records.
AI supports the assessment; predefined workflow logic controls how its output is used.
One business process, crossing
- Documents
- AI-assisted processing
- Workflow logic
- Conversation context
- Salesforce/Connexys
From candidate email to Salesforce, step by step
- 01 · ReceiveA staffing agency sends a candidate proposal by email.
- 02 · ExtractEmail and supported CV information are structured.
- 03 · AssessAI supports the assessment against technical role profiles.
- 04 · PrepareThe appropriate follow-up is prepared, with the conversation kept.
- 05 · ValidateThe agency’s reply and existing Salesforce records are checked.
- 06 · RegisterCandidate, application and CV go into Salesforce/Connexys where appropriate.
Another pattern
Sometimes the automation is the handover between teams.
At Optimile and Mobiflow, incoming Marketing demand needed to become actionable Sales work. A website request creates a contact and lead in HubSpot, ownership is assigned through round-robin and a follow-up task is created, so Sales starts with a clear next action instead of a record sitting in the CRM.
Business process automation does not always mean a large technical workflow. Sometimes a few well-designed handovers remove the manual gap between teams.
From website request to Sales action
- 01 · WebsiteWebsite request
- 02 · HubSpotContact & lead created
- 03 · HubSpotRound-robin Sales assignment
- 04 · HubSpotFollow-up task created
- 05 · SalesSales action
Process design
Automating a bad process only makes the bad process faster.
Before anything is built, the process is mapped and, where possible, simplified. The workflow then follows the process instead of freezing its current workarounds.
01Map
Understand how the process works today.
- Trigger
- Inputs
- Systems
- Decisions
- Exceptions
- Outputs
- Owners
02Simplify
Remove what should not be automated in the first place.
- Unnecessary steps
- Duplicate data entry
- Unclear ownership
- Rules that can be made explicit
03Build
Connect the systems and implement the workflow.
04Test
Test more than the normal path.
- Normal path
- Missing data
- Existing records
- Failures
- Unexpected inputs
05Hand over
Make sure the team knows how the workflow behaves.
- What happens automatically
- What remains manual
- How failures are handled
- Where to change the workflow later
Control
Automate execution. Keep decisions where they belong.
Different steps in a process need different levels of control. A typical split looks like this, though every project draws the lines in its own place.
Deterministic automation
- Field mapping
- Record lookup
- Routing rules
- Status updates
- API calls
AI-assisted steps
- Extracting information
- Classification
- Summarisation
- Preparing responses
- Supporting assessments
Human decisions
- Approvals
- Exceptions
- Commercially important judgement
- Sensitive decisions
The workflow should make clear which decisions are rules, which are AI-assisted and which remain human.
Technology
Use the tools that fit the workflow.
I work with the systems a business already uses rather than forcing every process into a new platform. Depending on the workflow, that can mean n8n for orchestration, HubSpot or Salesforce as the CRM, and the APIs, files and services around them.
Depending on the workflow
- n8n
- HubSpot
- Salesforce
- Email platforms
- Spreadsheets
- REST APIs
- Webhooks
- AI services
- Custom integrations
The architecture should be as simple as the process allows and as robust as the process requires.
Reliability
The failure path is part of the workflow.
Production automation needs more than a working normal path. Which safeguards a workflow gets depends on how important and how complex the process is; not every workflow needs all of them, and no workflow can promise that nothing ever goes wrong.
Safeguards to consider
- Validation
- Retries
- Error outputs
- Logging
- Duplicate and existing-record checks
- Fallback paths
- Alerts
- Manual recovery
- Idempotent steps where possible
A workflow is not finished when the normal path works. You also need to know what happens when it does not.
Questions about process automation
Business process automation, answered briefly
- What is business process automation?
- Using software and integrations to carry out the repetitive steps of a business process automatically, while keeping the necessary rules, checks and human decisions in place.
- What business processes can be automated?
- Common examples are email processing, CRM administration, lead routing, document processing, data synchronisation, follow-up tasks, reporting inputs and repetitive handovers between systems. Whether a process is suitable depends on how predictable it is and which systems are involved.
- How do I know if a process is worth automating?
- Good candidates are repetitive, rule-based, frequent enough to matter and currently need people to move information between systems. The number of exceptions, the complexity and the business impact matter too.
- Do I need to replace my existing software?
- Usually not. I generally connect the existing systems first. Sometimes a process exposes a limitation that makes a software change sensible, but replacement should not be the default assumption.
- What tools do you use for business process automation?
- n8n, HubSpot, Salesforce, APIs, webhooks, email and document processing, and AI services where they are useful.
- Can you automate processes between systems that do not have a native integration?
- Often, if the systems provide an API, webhooks or another reliable way to exchange data. Sometimes a custom integration is needed.
- Can AI be part of business process automation?
- Yes. AI is useful for less predictable tasks such as extraction, classification and summarisation. Fixed business rules are usually better kept as deterministic steps in the workflow. See AI workflows.
- What happens if an automation fails?
- Depending on how important the process is, a production workflow can include validation, retries, logging, error paths and manual recovery. Not every failure can be recovered automatically, so the workflow should make failures visible.
- Is business process automation only for large companies?
- No. The relevant question is whether the repetitive manual work is significant enough to justify automating it.
- Do you provide business process automation in Belgium?
- VNCK works from Willebroek, Belgium and builds business process automation for companies that need to connect CRM, email, documents, APIs and operational tools. Projects can be delivered remotely, with on-site collaboration where useful.
Automation project
Start with the task everyone is tired of doing.
Show me the process as it works today. We can map the repetitive steps, decide what should stay human and build the workflow around the systems you already use.