Short answerMake's custom webhook is an instant trigger with a unique URL and a 5 MB payload limit. n8n's Webhook node has separate test and production URLs, basic, header or JWT authentication, and a 16 MB payload limit.
Make: custom webhook
- Instant trigger that gives a unique URL per scenario.
- Accepts JSON, form data, multipart and query strings; 5 MB payload limit.
- Optional API key header, IP restrictions and a data structure for validation.
- Default reply is 200 "Accepted"; a Webhook Response module can return a custom reply.
n8n: Webhook node
- Separate Test and Production URLs; production registers when you publish the workflow.
- Methods: DELETE, GET, HEAD, PATCH, POST, PUT.
- Authentication: Basic, Header, JWT or none.
- Response modes include immediately, when the last node finishes, and via a Respond to Webhook node.
- Payload limit 16 MB, changeable on self-hosted installs.
Always require authentication so strangers cannot trigger your workflow. See Actions migration and Zapier.
Not sure it is simple enough to do yourself?
Tell us what your GPT does, whether it uses Actions and how many files it has. We will say what will break and what a rebuild involves. The audit is free.
Request a free auditRelated guides
Sources
Pages describing other companies' products reflect their public documentation on the date shown and can go out of date.