Why n8n for automation?
n8n is a self-hostable, fair-code workflow engine with hundreds of integrations and a permissive licence for internal use. For an MSP or IT team it means one tool that can call the PSA ticketing API, the RMM API, Microsoft Graph, Slack and a webhook from a monitoring alert — without writing a full app for each integration. Self-hosting keeps data inside your perimeter and avoids per-execution SaaS pricing.
Workflow automation basics
An n8n workflow is a graph of nodes: a trigger (webhook, schedule, poll, manual), processing nodes (transform, filter, branch), and action nodes (HTTP, app integrations). Each node receives JSON items and outputs JSON items, so data flows predictably. Use the Set node to shape data between steps, the If/Switch nodes to branch, and the Merge node to combine branches. Version workflows in Git via the n8n CLI or the source control feature.
- Trigger → transform → action is the basic shape
- Use Set nodes to shape data between steps
- Branch with If/Switch; combine with Merge
- Version workflows in Git
Integration orchestration
The highest-value workflows orchestrate across systems that do not natively talk to each other. A monitoring alert becomes a ticket with the right category and priority; a closed ticket triggers a CSAT survey and a CRM update; an HR new-hire creates the identity and opens the onboarding ticket. n8n's HTTP node handles any REST API; built-in nodes cover Microsoft Graph, Slack, Google, Jira, Asana and more.
| Trigger | Actions | Value |
|---|---|---|
| Monitoring alert | Create ticket + notify NOC channel | Faster, consistent incident response |
| HR new-hire | Provision identity + open onboarding ticket | Removes manual copy-paste |
| Ticket closed | Send CSAT + update CRM | Closes the feedback loop |
| RMM agent offline 24h | Escalate to NOC + open ticket | Catches silent failures |
MSP automation workflows
For MSPs, the workflows that pay back fastest remove copy-paste between the PSA, RMM and documentation tools. Auto-create tickets from alerts with standardised categories and priorities. Sync asset data from the RMM into the documentation tool (IT Glue/Hudu) so documentation stays current. Trigger onboarding/offboarding checklists from the PSA contract change webhook.
- Monitoring alert → auto-ticket with context
- RMM asset sync → documentation tool
- PSA contract change → onboarding/offboarding checklist
- Backup failure alert → escalate + open ticket
API integrations
Use the HTTP Request node for any REST API not covered by a built-in node. Store credentials in n8n's credential vault (encrypted), never inline in nodes. Handle pagination with the node's pagination settings, and handle rate limits with retries and backoff. For GraphQL APIs, send the query as the request body and parse the response.
// HTTP Request node configuration
Method: POST
URL: https://graph.microsoft.com/v1.0/users
Authentication: Header Auth (Bearer token from credential)
Headers: { "Content-Type": "application/json" }
Body: { "accountEnabled": true, "displayName": "={{ $json.name }}" }
Pagination: none | Retry: 3 with exponential backoffWebhook automation
Webhook triggers let external systems start a workflow in real time. Expose a webhook URL in n8n, register it with the source (GitHub, Stripe, a monitoring tool), and the workflow runs on each event. Always validate the webhook signature where the source supports it, and respond quickly — offload long work to a sub-workflow so the webhook returns within the source's timeout.
- Validate webhook signatures where supported
- Respond fast — offload long work to a sub-workflow
- Use the webhook test URL for development, production URL for live
- Store the production webhook URL in the source's secret store
Business process automation
Beyond IT ops, n8n automates business processes — approval routing, document generation, report distribution, CRM sync. The discipline is the same: map the manual process, identify the systems and their APIs, build the workflow, and add an error-trigger so failures alert a human. Start with one painful, repetitive process, prove the value, then expand.
Self-hosting and reliability
Run n8n in Docker behind a reverse proxy with Postgres as the execution store (SQLite is fine for small setups but Postgres scales). Use queue mode with a separate worker process for high-volume workflows so the editor stays responsive. Back up the n8n database — your workflows are intellectual property. Add an error-trigger workflow so a failed run alerts the NOC rather than failing silently.
- Use Postgres in queue mode for production n8n
- Store credentials in the vault, never in nodes
- Add error-trigger workflows so failures alert a human
- Back up the n8n database — workflows are code
Lessons learned
- Start with one painful, repetitive process — prove value, then expand
- Use Postgres + queue mode for production reliability
- Validate webhook signatures and respond fast
- Back up the n8n database — workflows are intellectual property
Written by
Jamshed Alam
Global MSP & IT Infrastructure Consultant with 20 years across Exchange, Microsoft 365, Azure, security and automation. Available for project and contract work worldwide.