Salesforce automation
Connect Salesforce to the work happening around it.
I build integrations and workflows that read, create and update Salesforce records as part of wider business processes — connecting CRM data with email, documents, APIs and operational systems.
CRM integration
The CRM is often only one step in the workflow.
A business process rarely starts in Salesforce. It begins with an email, a form, a document, another application, an internal request or an API event, and Salesforce needs to receive, update or provide information somewhere in the middle.
So an integration starts with the process around the CRM, as part of the wider CRM automation and business process automation work I do.
What to understand first
- Where the process begins
- Which Salesforce records are involved
- How those records relate to each other
- Which data already exists
- What may be created
- What may be updated
- What happens when information is incomplete
- Which steps need fixed rules or a person
Start with the business process and data relationships, then decide where Salesforce belongs in the workflow.
What I work on
The work around Salesforce records.
Most of the effort in a Salesforce integration sits in four areas: the records themselves, the connections to other systems, the email and documents that feed the process, and the rules that keep it under control.
Records and relationships
- Contacts
- Candidates
- Applications
- Positions
- Custom objects
- Find existing records
- Create records
- Update records
- Link related records
- Preserve existing information
APIs and integrations
- Salesforce API
- n8n
- REST APIs
- Webhooks
- Internal systems
- Read Salesforce data
- Write Salesforce data
- Trigger external workflows
- Synchronise systems
- Transform data between systems
Email and documents
- Outlook
- Gmail
- CVs
- PDFs
- Attachments
- Process incoming messages
- Extract structured information
- Connect documents to CRM records
- Prepare follow-up
- Keep the conversation context with the workflow
Workflow control
- Existing-record checks
- Statuses
- Validation
- Routing
- Error handling
- Avoid unnecessary record creation
- Validate required information
- Apply workflow rules
- Route different scenarios
- Handle failures explicitly
In production
From candidate email to Salesforce.
Logi-technic receives candidate proposals from staffing agencies by email. The workflow I built around their Salesforce environment with Connexys recruitment functionality reads each proposal, processes the supported CV or document attachments and structures the candidate’s experience, education and other relevant information.
Detailed technical role profiles are the input for the assessment. AI proposes a core profile and supports the assessment; predefined workflow logic controls how that output is used and which follow-up is prepared.
Around Salesforce/Connexys, the workflow
- Keeps the conversation context and processes the staffing agency’s reply
- Checks existing Salesforce data before writing
- Creates or supplements the Candidate where appropriate
- Creates or reuses the relevant Job Application
- Links candidate and application to the relevant Position
- Transfers the CV into Salesforce and links it to the records
Candidate proposal to Salesforce, step by step
- 01 · ReceiveA staffing agency sends a candidate proposal by email.
- 02 · ExtractThe workflow structures candidate and CV information.
- 03 · AssessAI supports the assessment against detailed technical role profiles.
- 04 · PrepareThe agency follow-up is prepared, with the conversation context kept.
- 05 · ValidateWhen the agency replies, the conversation and existing Salesforce records are checked.
- 06 · RegisterCandidate, application and CV are created or updated in Salesforce/Connexys where appropriate.
Data integrity
Check what already exists before creating something new.
CRM automation that creates a new record for every incoming message quickly fills Salesforce with duplicates and half-complete records. Before writing, a workflow should look at what is already there.
At Logi-technic, the workflow checks Salesforce before deciding whether to create or update: an existing candidate can be supplemented and an existing job application reused. These checks reduce unnecessary duplicates; they cannot rule them out in every situation.
Checks that can apply
- Does the person already exist?
- Does a related application already exist?
- Which record should be updated?
- Should existing information be preserved?
- Should new information supplement an existing record?
- Which relationships need to be created?
Good CRM automation treats existing data as context, not as something to overwrite by default.
Custom objects
Integrations have to understand the CRM you actually built.
Many Salesforce environments contain far more than standard Contacts, Accounts and Opportunities. The process depends on how that particular organisation has modelled its data, so an integration has to work with the actual data model rather than a generic one.
At Logi-technic, Salesforce with Connexys recruitment functionality works with concepts such as Candidate, Job Application and Position. The workflow writes to those records and their relationships instead of treating everyone as a generic contact or opportunity.
What a process can depend on
- Custom objects
- Custom fields
- Record types
- Lookup relationships
- Workflow statuses
- Picklists
- Document relationships
Documents
A CRM record is often only useful when the document travels with it.
Many processes revolve around documents: CVs, proposals, PDFs, forms and supporting files. Storing the extracted data without the source document leaves the record incomplete; storing the document without the data leaves people reading it again.
In the Logi-technic workflow, a CV arrives with an email, its relevant information is extracted, and the file is transferred into Salesforce and linked to the candidate and application it belongs to. Which file formats can be processed depends on the documents and the tools in the workflow.
What the integration has to do
- Receive the document
- Extract the relevant information
- Associate it with the correct record
- Store it using Salesforce’s document model
Workflow orchestration
Use Salesforce for CRM data. Use the workflow layer to connect the rest.
Salesforce is often one system inside a broader workflow. When the process also touches other tools, n8n can orchestrate it: receiving the trigger, calling the other services and deciding what to write, while Salesforce remains the system responsible for the CRM records.
That does not replace Salesforce’s own automation. Logic that lives entirely inside the CRM is usually best kept there.
Where a workflow layer helps
- Documents
- AI services
- Spreadsheets
- Other APIs
- Internal tools
Architecture
Native automation, n8n or a custom integration?
These are starting points, not fixed rules. The process decides.
- Native Salesforce automation
- Best when the process is mainly inside Salesforce, the records and actions stay within the CRM and native Salesforce functionality covers the requirements.
- Salesforce + n8n
- Best when email, documents or external systems are involved, custom API orchestration is required, data has to move through several services or external AI or processing is part of the workflow.
- Custom integration
- Best when specialised application behaviour is required, the integration is business-critical, standard connectors do not expose the necessary functionality or a dedicated application integration fits better.
Keep CRM logic close to Salesforce where it belongs, and use external orchestration for the parts that genuinely cross systems.
Questions about Salesforce
Salesforce, answered briefly
- What can a Salesforce automation consultant help with?
- API integrations, CRM workflows, creating and updating records, working with custom objects, data flows between systems, documents and attachments, and connecting Salesforce to the other systems a process uses.
- Do you work with Salesforce in Belgium?
- VNCK works from Willebroek, Belgium and builds Salesforce integrations and CRM automation as part of wider business processes.
- Can Salesforce connect to n8n?
- Yes. n8n can read and write Salesforce data and coordinate processes that involve other systems. Not every Salesforce operation is covered by a ready-made node; some need direct API calls.
- Can you create and update Salesforce records automatically?
- Yes, when the workflow has the required permissions and validated data. A workflow can find, create, update and relate records. The checks should happen before anything is written.
- Can you automate Salesforce custom objects?
- Yes, where those objects are accessible through the Salesforce API with the right permissions. The workflow has to understand the custom fields and relationships. At Logi-technic, it works with Candidate, Job Application and Position records in Salesforce/Connexys.
- Can Salesforce workflows process email attachments?
- Salesforce does not have to do every step itself. An external workflow can receive the email and documents, process them, then create or update Salesforce records and attach the relevant file. The Logi-technic workflow does this with candidate CVs.
- Can AI be connected to Salesforce?
- Yes, as part of a controlled workflow. AI can extract structured information, classify requests, summarise content, support assessments or prepare responses. Important decisions should stay with defined business rules and the people responsible for them.
- How do you avoid duplicate Salesforce records?
- By searching for existing records first, using stable identifiers where they exist, checking relationships, defining clear create and update rules and preserving existing data where appropriate. These controls reduce unnecessary duplicate creation; they cannot always prevent it.
- Can you migrate data into Salesforce?
- I build data flows that create and update Salesforce records. A full Salesforce migration is a separate scope that depends on the source data, the data model, the relationships, the volume and the migration requirements.
- Should I use Salesforce Flow or n8n?
- Use Salesforce’s native automation when the process mainly stays inside Salesforce. Use n8n when the workflow has to coordinate Salesforce with email, documents, APIs, AI or other external systems. Sometimes the right architecture uses both.
Salesforce workflow
Connect the CRM to the process around it.
If Salesforce still depends on people moving information between email, documents and other systems, we can map that process and automate the right handovers.