Skip to main content

n8n Integration

Open-source workflow automation with self-hosting option.

n8n Integration

n8n is an open-source workflow automation platform that you can self-host or use via n8n.io cloud. It provides a visual workflow builder with full control over data transformation, conditional logic, and error handling — making it an excellent choice for organisations that need advanced automation or prefer to keep data on-premises.

CrownSync integrates with n8n through two mechanisms: outbound webhooks (CrownSync pushes events to n8n) and the REST API (n8n calls CrownSync to create or update incidents).

Using CrownSync Webhooks as Triggers

CrownSync can push events to n8n whenever incidents are created, updated, or closed:

  1. Create a Webhook node in n8n. In your n8n workflow, add a Webhook node as the trigger. Set the HTTP method to POST. n8n will generate a unique webhook URL.
  2. Copy the n8n webhook URL into CrownSync. Navigate to Admin → Integrations → Webhooks in CrownSync and add a new outbound webhook. Paste the n8n URL as the destination and select which events to forward (e.g. incident created, incident updated, drill completed).
  3. Activate and test. Activate the n8n workflow, then trigger an event in CrownSync (e.g. create a test incident). The Webhook node should receive the payload and pass it to the next node in your workflow.

Using CrownSync API as Actions

n8n can call the CrownSync REST API to create incidents, update records, or fetch data:

  1. Add an HTTP Request node. In your n8n workflow, add an HTTP Request node after your trigger.
  2. Configure the request. Set the URL to https://pb.crownsync.uk/api/v1/incidents, the method to POST, and add an Authorization header with the value Bearer YOUR_API_KEY. Generate your API key from Admin → Integrations → API Keys.
  3. Build the request body.Use n8n's expression editor to map incoming data from previous nodes into the JSON body. Refer to the API Reference for the full schema of available fields.

Example Workflows

Here are some workflows you can build with n8n and CrownSync:

  • Sentinel alert → Create CrownSync incident → Notify Teams → Create Jira ticket. A Microsoft Sentinel webhook triggers n8n, which creates an incident in CrownSync, posts a notification to a Microsoft Teams channel, and creates a Jira ticket for tracking — all in a single automated workflow.
  • CrownSync incident closed → Generate summary → Email stakeholders. When CrownSync sends an incident-closed webhook, n8n extracts the timeline and lessons learned, formats a summary using a template node, and sends it to a distribution list via the email node.
  • Scheduled compliance check → Fetch playbook status → Report. A Cron node triggers daily, n8n calls the CrownSync API to check which playbooks have been reviewed recently, and generates a compliance status report.

Advantages of n8n

  • Self-hosting.Run n8n on your own infrastructure to keep all data within your network perimeter — particularly important for organisations with strict data residency requirements.
  • Full control over data transformation. Use JavaScript or Python function nodes to manipulate data between steps, apply conditional logic, and handle complex branching scenarios.
  • No per-task pricing. Unlike SaaS automation platforms, self-hosted n8n has no per-execution costs, making it cost-effective for high-volume workflows.
  • Extensive node library. n8n includes hundreds of built-in integrations for databases, messaging platforms, cloud services, and more.

Credential Management

n8n has a built-in credential management system that securely stores API keys and tokens. Create a credential of type Header Auth with the name Authorization and the value Bearer YOUR_API_KEY, then reference it across multiple HTTP Request nodes. This avoids duplicating API keys in individual nodes and makes key rotation simpler.

Next Steps

  • Review the REST API Reference for all available endpoints and request fields
  • Configure outbound webhooks in CrownSync to trigger your n8n workflows
  • Consider Zapier if you prefer a no-code approach without self-hosting

Integration instructions last verified: April 2026

Was this page helpful?