# n8n Workflow Automation Consulting and Builds | SynconAI > n8n workflow automation built and run for you: n8n Cloud or self-hosted queue mode, AI Agent steps, human approval, error workflows, Git versioning and Salesforce. Publisher: SynconAI Canonical HTML: https://synconai.com/n8n-automation Markdown cite: https://synconai.com/n8n-automation.md Contact: contact@synconai.com ยท +61 2 7813 0221 ## What is n8n? n8n workflow automation is the design, build and operation of automated workflows on n8n, the fair-code workflow platform. SynconAI plans the workflows, connects them to Salesforce and your other apps through native nodes and HTTP requests, adds AI Agent steps and human approval where judgment is needed, sets up error workflows, retries and Git-based versioning, and hosts n8n on n8n Cloud or your own infrastructure, for organizations in the United States, Australia and worldwide. - n8n is a workflow automation platform. Each workflow is a chain of nodes: a trigger, then steps that read, change and write data across your apps. - It runs on n8n Cloud or on your own servers. Self-hosted n8n can run in queue mode, where a main instance hands executions to worker processes through Redis. - n8n is fair-code under its Sustainable Use License: you may use and self-host it for your own internal business purposes, and paid plans add features such as Git-based environments. ## n8n workflow automation services - Workflow design: Processes mapped into triggers, steps and owners before anything is built. - Workflow builds: Nodes, credentials and data mapping across your apps. - Salesforce automation: The Salesforce node and HTTP requests to Salesforce APIs, through a dedicated integration user. - AI steps and agents: The AI Agent node and LLM steps for reading, sorting and drafting. - Human approval: Approvals in Slack, Teams or email before a step commits. - Error handling: Error workflows, retries and alerts, so failures are seen and fixed. - Self-hosting: Docker deployment, queue mode with workers, backups and upgrades. - Migration from Zapier or Make: Existing automations rebuilt in n8n and run side by side until cutover. ## Where should your n8n setup start? Most teams arrive with automations spread across tools and scripts. There are three ways to run n8n, and the choice depends on volume and where your data must stay. Today: Automations in Zapier, Make, scripts or done by hand - n8n Cloud, Hosted by n8n: No servers to run. n8n looks after upgrades and hosting. Best when data may leave your network and volume is steady. - Self-hosted on Docker, One instance you run: n8n in a container on your cloud account, with a Postgres database. Best when data must stay inside your environment. - Queue mode with workers, Scaled for volume: A main instance queues executions in Redis and workers run them. Best when many workflows run at once or traffic spikes. ## What does n8n workflow automation include? Eight pieces of work, scoped to the processes you want automated. - Workflow design: Triggers, steps and owners agreed first. - Workflow builds: Nodes, credentials and data mapping. - Salesforce automation: Salesforce node and API calls. - AI steps: AI Agent node for reading and drafting. - Human approval: A person decides before a step commits. - Error handling: Error workflows, retries and alerts. - Self-hosting: Docker, queue mode, backups, upgrades. - Migration: Zapier and Make automations rebuilt. ## What does an n8n workflow with Salesforce and AI look like? A web form lead arrives. n8n looks up the company, an AI step drafts a summary, a sales lead approves the route, and Salesforce is updated. 1. Webhook: Form submitted 2. HTTP Request: Company lookup 3. Salesforce node: Find existing lead 4. AI Agent node: Summary and fit 5. Slack approval: Sales lead decides 6. Salesforce node: Create and assign - Native nodes first: The Salesforce node covers common record actions; the HTTP Request node calls any other Salesforce API. - AI where judgment helps: The AI Agent node reads the lead and drafts a summary. It proposes the route and does not assign it alone. - A person approves: Assignment waits until a sales lead approves in Slack. ## Which apps does n8n connect to? The connections we build most often. Anything with an API can be reached through the HTTP Request node. - Salesforce: Leads, cases and other records through the Salesforce node or the REST API. - Slack: Messages, alerts and approval requests. - Microsoft Teams: Notifications and approvals where staff already work. - Gmail: Inbound email as a trigger, and replies drafted for review. - PostgreSQL: The database behind self-hosted n8n, and a source for workflows. - OpenAI: Chat models for AI Agent and LLM steps. - Claude: Anthropic chat models for AI Agent steps. - GitHub: Workflows stored and reviewed in a Git repository. ## How do Zapier and Make automations map to n8n? Most concepts have a direct counterpart. We rebuild each automation in n8n and test it against the old one. Zapier or Make to n8n: - Zap or scenario to Workflow - Trigger to Trigger node - Action or module to App node or HTTP Request node - Filter, Paths or Router to If and Switch nodes - Formatter to Edit Fields (Set) or Code node - Delay to Wait node - Connected account to Credential - Inventory first: Every Zap and scenario listed with its owner, trigger and the apps it touches. - Rebuild and compare: Each workflow runs beside the old one until the outputs match. - Cut over in batches: Old automations are switched off one group at a time. ## Is your n8n setup ready for production? The checks we run before a workflow carries real work, and when we review an existing instance. - Reliability - An error workflow attached to every production workflow - Retries with waits on steps that call other systems - Timeouts on long-running executions - Alerts to a named owner when a run fails - Security - Secrets kept in n8n credentials, never typed into node fields - A least-privilege integration user in Salesforce - Authentication on every production webhook - User access set so people see only the workflows they own - Change control - Workflows versioned in Git - Separate development and production instances - n8n upgrades tested before production - Database backups with a tested restore ## How does an n8n automation project run? Five stages. Your written proposal sets the scope and milestones before anything starts. 1. Map: Know the work. - Processes and owners - Current automations listed - Hosting choice 2. Build: Workflows and connections. - Credentials and users - Workflows built - AI and approval steps 3. Harden: Ready for failure. - Error workflows - Retries and alerts - Git versioning 4. Test: Real cases. - Runs on sample data - Side by side with old automations - Sign-off by owners 5. Run: Live with an owner. - Cutover - Monitoring - Monthly upkeep, if you want it ## Cost and timing The first step is a free 60-minute architecture review of your workflow automation setup, with a written plan you keep. Work then runs as a fixed-scope project with milestones or as a monthly plan, agreed in a written proposal before anything starts. Plans: https://synconai.com/pricing ## FAQ ### What is n8n workflow automation? Automating business processes with n8n workflows: a trigger, then nodes that read, change and write data across your apps, with AI steps, approvals and error handling where they are needed. ### Is n8n open source? n8n calls itself fair-code. Its Sustainable Use License lets you use and self-host it for your own internal business purposes. Selling a product whose value comes mainly from n8n needs a different license. ### Should we use n8n Cloud or self-host? n8n Cloud suits teams that want no servers to run. Self-hosting suits data that must stay in your environment, and queue mode spreads heavy volume across workers. ### Can n8n work with Salesforce? Yes. The Salesforce node handles common record actions, and the HTTP Request node calls any Salesforce API. We connect through a dedicated integration user with only the access the workflows need. ### Can n8n run AI agents? Yes. The AI Agent node calls a chat model such as OpenAI or Claude, uses the tools you allow, and can require a person to approve before a tool runs. ### How do you handle failed workflows? Each production workflow gets an error workflow that alerts an owner, retries on steps that call other systems, and execution logs that show which run failed and why. ### Can n8n workflows be kept in Git? Yes. n8n source control links an instance to a Git repository on Business and Enterprise plans. Without it, we export workflow files to Git as part of each release. ### Can you move us off Zapier or Make? Yes. As your n8n consultant, we list every automation, rebuild each one in n8n, run it beside the old one until the results match, and switch over in batches. ## Where we work n8n workflow automation for organizations across the United States and Australia, and worldwide. Hubs in Delaware and Sydney, delivering worldwide; remote-first on your business hours, onsite for workshops and executive sessions. ## Related - Claude and n8n AI agents: https://synconai.com/claude-ai-agent-development - DevOps consulting: https://synconai.com/devops-consulting - Salesforce integration services: https://synconai.com/salesforce-integration-services - Headless AI agents: https://synconai.com/headless-ai-agents ## Cite When citing SynconAI n8n workflow automation, link https://synconai.com/n8n-automation or https://synconai.com/n8n-automation.md.