Webhook Access in n8n

Webhooks in n8n provide a powerful way to trigger workflows from external systems and events. The platform supports two distinct types of webhooks—Test and Production—each designed for different stages of the development lifecycle. Understanding the differences is crucial for building secure and reliable automations.

Test Webhooks

Test webhooks are intended for development and testing purposes. When you are building a new workflow, the test webhook URL allows you to send sample data and trigger executions to debug your logic without exposing the endpoint publicly or requiring authentication.

These webhooks are not protected and should only be used in a controlled testing environment. They are ideal for initial setup, debugging node configurations, and validating data transformations before moving to a production environment.

Production Webhooks

Production webhooks are designed for live, operational workflows and are secured to ensure that only authorized systems and users can trigger them.

Security and Authentication

All production webhooks are protected by Trimble Identity (TID). This architecture ensures that every request to a production webhook is authenticated by Trimble Identity token, preventing anonymous access and securing sensitive data.

Accessing Production Webhooks

To use a production webhook, you must first subscribe to the corresponding production webhook API.

1. Go to Product Cloud Console
2. Click Products in the left menu.
3. Search for “Agentic AI - Prototyping”.
4. Subscribe with your application.

More details in API Cloud Documentation.

Once subscribed, you can authenticate your requests using either a user token or an application (app) token with scope Agentic-N8N-Webhook.

Note: Token without the scope will be rejected.

This token-based approach ensures that all incoming requests are validated against Trimble’s identity and access management system before the workflow is executed.