Can I use n8n under the Sustainable Use License (SUL) as the webhook endpoint for a WhatsApp integration, or does the webhook need to be implemented in my own application with n8n only acting as the backend?
@Oscar_Bonilla_Calder , that will depend on your use case.
More info here
We understand that using n8n as the back end to power a feature in your app is usually allowed, as long as n8n isn’t collecting and using your users’ own credentials to access third-party services on their behalf. One of their examples is an AI chatbot where users submit questions, but the workflow runs using the company’s own credentials—that is explicitly described as allowed.
Your WhatsApp example:
WhatsApp → n8n Webhook → workflow → your systems/APIs is generally in line with that example, assuming the workflow uses your WhatsApp Business credentials and other API credentials.
If your app collected each customer’s own WhatsApp/API credentials and stored or used them in n8n to access their accounts, that’s the kind of scenario the SUL FAQ calls out as not allowed.
So the webhook itself doesn’t need to be implemented in your own application just because of licensing. The more important question is whose credentials n8n is using, not whether the webhook endpoint is /webhook/... on n8n or on your own backend.
If your use case is a bit more unusual (multi-tenant, customer-supplied credentials, etc.), n8n also recommends contacting license@n8n.io for an authoritative interpretation of your specific scenario.
Which license do I need for my use case? | n8n Help Center
Hope this helps