Library / Code, Git & Developer Tools
Code, Git & Developer Tools
Test n8n Webhooks Without Changing the Webhook URL
When you run it, it creates a temporary request bin, mocks a webhook request and reads it back so you can test short-lived webhooks.
What it does
## How to Test a Short-Lived Webhook in n8n WITHOUT Changing WEBHOOK_URL Typically in n8n, in order to test a webhook, you first need to go through the process of changing the [WEBHOOK_URL]({{ $env.WEBHOOK_URL }} environment variable to an address that is accessible to the service you want to test. Time permitting, that can be done with [ngrok]({{ $env.WEBHOOK_URL }} ([example]({{ $env.WEBHOOK_URL }} or by self-hosting with one of [n8n's recommended deployment options]({{ $env.WEBHOOK_URL }} But if you're new to n8n and in a rush to test a webhook's functionality, you can use [PostBin]({{ $env.WEBHOOK_URL }} as demonstrated in this workflow to test a proof of concept fast and avoid any unnecessary time on n8n setup and configuration.
The steps
- When clicking ‘Test workflow’
- Merge
- Create Bin
- GET Bin
- Format url for webhook
- GET most recent request
- MOCK request
- Create Bin1
- GET Bin1
- Format url for webhook1
- SET BambooHR subdomain
- Split out fields
- Combine fields to monitor
- Format payload for BambooHR webhook
92 steps in total.
Similar automations
Code, Git & Developer ToolsTest n8n Webhooks with PostBin Without Changing WEBHOOK_URL34 stepsRAG & Knowledge BasesBambooHR Company Policies and Benefits Chatbot with OpenAI48 stepsRAG & Knowledge BasesBambooHR Company Policies and Benefits Chatbot48 stepsRAG & Knowledge BasesAnswer HR Policy Questions with BambooHR, OpenAI and Supabase39 steps