Automation and forms integration · Updated November 15, 2026

n8n integration

We build n8n workflows that move form, booking and payment data from your website into your CRM and other systems, and we can self-host n8n on Canadian servers. n8n fits when volumes are high, logic branches, or personal data has to stay in Canada.

Rated 5.0 out of 5,72 Google reviews

n8n at a glance

Connects
Hundreds of app nodes, a Webhook trigger, an HTTP Request node and code steps.
WordPress
The WordPress node writes posts, pages and users; form data arrives by webhook.
Webflow
A Webflow Trigger node for site events, and a Webflow node for CMS items.
Astro or Next.js with Sanity
A server route posts to an n8n Webhook node; n8n can write back to Sanity's API.
Custom software
Webhooks both ways, n8n's REST API, and n8n as a hidden back-end process.
Complexity
Medium. Self-hosting adds servers, backups, updates and monitoring.
Typical setup
2 to 4 days for workflows on n8n Cloud, 5 to 10 days with a self-hosted Canadian instance.

How we connect n8n

  • WordPress

    n8n's WordPress node creates and reads posts, pages and users, but it has no trigger and no form operations. Form data reaches n8n through a webhook: your form plugin or a small piece of code posts each entry to an n8n Webhook node. For anything else in WordPress, the HTTP Request node calls the REST API with an application password.

  • Webflow

    The Webflow Trigger node registers a webhook on your site, so a form submission starts the workflow without polling. The Webflow node then creates or updates CMS items. Webflow's form_submission payload sends field values as one data object, so we map each field by name and recheck it when someone renames a field in Designer.

  • Astro or Next.js with Sanity

    A server route validates the submission, stores it, then posts to an n8n Webhook node with a shared secret header. n8n can write results back to Sanity through its API, for example publishing an approved event listing. By default a self-hosted n8n accepts payloads up to 16 MiB, so large file uploads go to storage first and n8n gets the link.

  • Custom software

    Your app calls n8n's webhooks or its REST API, and n8n calls yours with the HTTP Request node. n8n's licence FAQ allows it to run behind the scenes in your product, as long as your users don't build or edit the workflows themselves. Letting customers build their own workflows needs an n8n commercial licence.

What organizations use n8n for

  • Keeping personal data in Canada

    We install the free Community Edition on a Canadian server, such as an AWS Canada region, with a PostgreSQL database and encrypted backups. Form submissions, contact records and execution logs then stay on infrastructure you can name in your privacy policy and your Law 25 assessment.

  • Branching intake workflows

    One form can route several ways: a donation enquiry to the development team, a media request to communications, an application to HR. n8n handles the branching, lookups and duplicate checks in one workflow, and an execution counts once however many steps it runs.

  • Scheduled syncs and reports

    A nightly workflow pulls new records from your booking or payment tool, reconciles them against the CRM and posts a summary to Slack. We split large jobs into batches and sub-workflows, so a single run doesn't run out of memory.

What to watch out for

  • Cloud hosting is in Germany

    As of November 15, 2026, n8n says data on its hosted plans is stored in the EU, on servers in Frankfurt, Germany. It offers no Canadian region. If personal data has to stay in Canada, self-host. If n8n Cloud is acceptable, record the transfer in your privacy policy and carry CASL consent fields with every contact.

  • Failures need an error workflow

    A failed execution only shows in the Executions list unless you set an error workflow. We build one starting with the Error Trigger node, which receives the workflow name, failing node, error message and execution link, and posts it to Slack or email. Risky nodes get Retry On Fail. A self-hosted instance also needs uptime monitoring.

  • Executions, memory and licence

    As of November 15, 2026, n8n Cloud Starter costs €20 a month billed yearly for 2,500 executions, with 640 MiB of memory. Pro costs €50 a month for 10,000. The self-hosted Business licence costs €667 a month billed yearly for 40,000. Community Edition is free, but the licence covers only your own business use.

Sources

Checked against n8n's docs on November 15, 2026.

  1. n8n pricing plans, executions, Frankfurt hosting
  2. Choose how to use n8n cloud vs self-hosted, editions
  3. License FAQ what the Sustainable Use License allows
  4. Sustainable Use License
  5. Handle errors gracefully error workflows and Error Trigger data
  6. Work with nodes Retry On Fail and On Error settings
  7. Enable queue mode
  8. Understand concurrency Cloud limits, queue mode on Enterprise
  9. Manage your data on n8n Cloud memory limits per plan
  10. WordPress node
  11. Webflow Trigger node

Questions about n8n

When should we use n8n instead of Zapier?

Choose n8n when volumes are high, workflows branch or loop, or data has to stay in Canada. n8n charges per execution, not per step, so long workflows cost less. Zapier is easier for non-technical staff to edit and has more ready-made connectors.

Can you host n8n for us under the free licence?

Yes, within limits. n8n's licence FAQ allows building automations for clients on an instance, and charging for setup and maintenance, as long as clients can't create or edit the workflows. Enterprise features such as SSO and Git version control need a paid licence.

What is queue mode, and do we need it?

Queue mode splits n8n into a main instance that receives webhooks and triggers, plus workers that run executions, with Redis passing jobs between them. It's included in self-hosted n8n and lets you add workers as volume grows. On n8n Cloud it's only available on Enterprise. Most website workflows don't need it at first.

How do we find out when a workflow fails?

Every production workflow gets an error workflow that posts the failure, failing node and execution link to a Slack channel or shared inbox. We save failed executions so someone can inspect the data and retry. A self-hosted server also gets uptime checks, so an outage is caught too.

Does your data need to stay in Canada?

Tell us what your workflows touch and where that data is allowed to live. We'll recommend n8n Cloud or a self-hosted Canadian instance and estimate both.

Book a call