Pinned Data Remains Empty When Debugging a Webhook Using Both GET and POST

It sounds like you’re experiencing an issue where the pinned data isn’t showing properly in the editor when the webhook node is configured to accept multiple HTTP methods (GET and POST). Based on the documentation:

• Data Pinning Limitations:
  Data pinning is only available for nodes that have a single main output. The webhook node, when set up with both GET and POST, has separate outputs for each method. This can lead to unexpected behavior when attempting to pin data.

• Development-Only Feature:
  Remember that data pinning is intended for development use only, so its behavior in non-standard setups can sometimes be less predictable.

Suggestions to Try:

1. Switch to a Single HTTP Method:
   If possible, configure the webhook to use only one HTTP method (either GET or POST) during development. This should ensure the node has a single main output and allow pinning to work as expected.

2. Use Unpinned Data for Debugging:
   If you need to work with both methods, note that unpinning shows the data correctly. You could consider using the unpinned data for your debugging sessions.

3. Upgrade n8n:
   Check if a later n8n version addresses this issue. Sometimes behavior around features like data pinning can be refined in newer releases.

It doesn’t necessarily indicate a bug—instead, it’s a limitation resulting from how outputs are handled when multiple HTTP methods are enabled in a node. This documentation detail is important to keep in mind when deciding on a setup during development.