Make → n8n · Modules
Make webhooks, scheduling and the Code module in n8n
The start of a scenario and its custom code move almost one to one: custom webhooks become n8n Webhook nodes, webhook responses become Respond to Webhook, scheduled scenarios get a Schedule Trigger, and the Code module becomes an n8n Code node.
What becomes what
| Make | In n8n | Notes |
|---|---|---|
| Webhooks: Custom webhook | Webhook | Accepts the same methods. The URL changes: point every sender at the n8n URL. |
| Webhooks: Webhook response | Respond to Webhook | Same status, headers and body. |
| Scenario schedule | Schedule Trigger | Daily, weekly, monthly and interval schedules from Make API exports. Export Blueprint files leave the schedule out: set it in n8n. |
| Watch modules (instant or polling triggers) | The app's n8n trigger | Pick the matching n8n trigger and connect the account. |
| Code (JavaScript) | Code | input and the returned result work as in Make. |
| Code (Python) | Code (JavaScript) | Ported by the AI rewrite: n8n Cloud's Python can't import modules. |
Check after converting
- Error handlers (Resume, Ignore, Break, Rollback) are listed in the report: set the node's On Error option or an error workflow.
- Packages declared in a Make Code module are listed: on n8n Cloud the Code node can only load crypto and moment.
Other modules: Router and filters · Iterator and aggregators · Formulas (IML) · HTTP and JSON · Data stores, variables and tools