What a configuration could hand over
When company policy keeps data out of somebody else’s cloud, n8n can run inside your own infrastructure. The configurator calls a webhook on submission and the workflow can carry on into the CRM, into tasks and into an alert. What the workflow does is then yours to change.
Webhook node
On submission the configurator could call the production URL of a Webhook node, and the workflow would start with the configuration as JSON in the request body.
IF and Switch
IF or Switch nodes can split enquiries by product, country or price band and route each branch elsewhere.
Respond to Webhook
The Respond to Webhook node can return a custom reply to the configurator, such as the ID of the record the workflow created in the CRM.
HTTP Request
The HTTP Request node or ready-made app nodes can also write the enquiry into an internal system that n8n can reach on your network.
What we need to connect it
You decide whether n8n runs on your own infrastructure, as the unlicensed Community edition or Business or Enterprise with a licence key, or in n8n Cloud.
We secure the webhook with one of the methods n8n offers: Basic auth, Header auth or JWT, optionally with an IP allowlist.
For debugging we use the webhook’s test URL; the production URL accepts requests only once the workflow is published.
The JSON structure and field names are agreed in advance.
Worth deciding up front
- When you self-host, the webhook’s availability is in your hands: if the server is down, the configuration is not delivered, so we agree on retries on the configurator’s side.
- The default maximum webhook payload is 16 MB, and a self-hosted instance can change it with the N8N_PAYLOAD_SIZE_MAX variable.
- With the production URL, n8n does not show incoming data in the workflow editor, so debugging is best done through the executions history.
Questions about this connection
Can n8n run on a server next to our ERP?
That depends on your IT; n8n installs through Docker, for example, and can run inside a private network. The configurator still has to reach the webhook from the internet, so a public address or reverse proxy is designed with your administrator.
What if we want to change the workflow later?
The workflow lives in your instance and you edit it yourselves. As long as the webhook URL and data structure stay the same, the configurator needs no change.
Other integrations
Put n8n to work in your sales.
Tell us what you sell and how an enquiry is handled today. On the demo you will see the configurator, and we will go through which data could flow from it into your system.