What are some good practices to troubhleshooting nodes?

Questions
1

I am new at n8n and trying Notion node but sometimes it works and others don’t. What are some good practices to troubleshooting nodes instead to go with HTTP node directly?

It would help if there was a node for:

My use case:

Any resources to support this?

Are you willing to work on this?

2

Please post this under the Question category. This is not the correct place

3

I’d check the Notion node input/output first before switching to HTTP. Quick win: open a failed execution, click the Notion node, and compare what went in on a working run vs. a failed run.

I just released a 9-part n8n workflow testing series in the n8n Global Community. For this, look at Part 7: Using Execution Logs to Find Out Why a Workflow Failed. It shows how to stop guessing and trace the issue node by node.

4

Hi @Alfredo_IM :waving_hand:,
I moved this to the Questions category so it gets better visibility for troubleshooting.

You’ll likely get more targeted help here :+1:

5

Hi @AlfredoIM, for the flaky Notion node, pin the input on a working run (right-click → Pin Data) then re-run the failing case against it — most “sometimes works” Notion issues are property names changing case or a database ID pointing to a renamed page. Also set N8N_LOG_LEVEL=debug in your env so the log shows the actual Notion API payload, way faster than swapping to HTTP

edit: double check the node output matches what you expect