Get Transcription

Overview

This node is a webhook trigger designed to start an n8n workflow when it receives an HTTP request at a dynamically generated URL. It creates a unique webhook path using a random UUID, allowing external services to send data to the workflow securely and uniquely. The node listens for either GET or POST HTTP methods based on user configuration.

Common scenarios include:

• Receiving transcription data or other event notifications from external APIs or services.
• Triggering workflows upon incoming webhooks without exposing predictable URLs.
• Integrating with systems that push data via HTTP requests.

For example, you might use this node to receive real-time transcription results from a call transcription service that sends data via POST requests to your workflow.

Properties

Output

The node outputs the data received in the HTTP request body as JSON under the json field. This means any payload sent to the webhook URL will be accessible in subsequent workflow nodes through the standard JSON data structure.

No binary data output is produced by this node.

Dependencies

• Requires no external API keys or credentials.
• Depends on n8n's internal webhook handling infrastructure.
• Uses a UUID generation library internally to create unique webhook paths.

Troubleshooting

• Webhook URL not found or 404 errors: Ensure the workflow is active and the node has successfully created its dynamic webhook path.
• No data received: Verify that the external service is sending data using the configured HTTP method (GET or POST).
• Multiple triggers: Since the webhook path is randomly generated and stored statically, restarting or duplicating the node may change the webhook URL. Confirm the current webhook URL before sending requests.
• Permission issues: Make sure the n8n instance is accessible externally if expecting requests from outside networks.

Links and References

• n8n Webhook Trigger Documentation
• UUID npm package (used internally for generating webhook paths)