Requirements:

1. BambooHR instance (free trial link)
2. BambooHR API key* (documentation)
3. Slack connection (n8n documentation)

• Note about API key: Set up in n8n as Generic Credential (Basic Auth) with the API key as the username and any string for the password.

Other use cases for BambooHR webhook

1. Fraud & Compliance Monitoring (Triggered by Pay Rate, Pay Type, Compensation Change Reason, Bonus Amount, Commission Amount)
2. Offboarding & Security Access Revocation (Triggered by Employment Status, Job Title, Department, Location)
3. Manager Change Alert for Team & Workflow Updates (Triggered by Reporting To, Job Title, Department)

STEP #1: Create a new Bin in PostBin

No authentication needed. Use API to create Bin and retrieve BinId to craft URL for subsequent usage.

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 environment variable to an address that is accessible to the service you want to test. Time permitting, that can be done with ngrok (example) or by self-hosting with one of n8n's recommended deployment options.

But if you're new to n8n and in a rush to test a webhook's functionality, you can use PostBin as demonstrated in this workflow to test a proof of concept fast and avoid any unnecessary time on n8n setup and configuration.

This may respond with a 404 If no requests have been sent to the Bin, an error is raised.

Uses API call to bypass broken PostBin create bin endpoint in n8n.

Retrieve the binId (can also be found in response of Create Bin node). Craft a url that uses https://www.postb.in/:binId structure

Per PostBin API Documentation: You can hit the https://www.postb.in/:binId endpoint to collect any kind of request data whether it is a GET, POST, PUT, PATCH, DELETE or whatever. This particular endpoint is not RESTful and is not part of this API. It isn't RESTful by definition. ie. it is meant to collect whatever you send to it.

Note about this section

Depending on your familiarity with BambooHR and your intention with the webhook, you could hard code the fields to monitor with your webhook or use AI to filter based on topic. I chose a middle ground for this example.

STEP #2

Use the PostBin URL in place of your normal webhook

BambooHR's /webhook API endpoint expects arguments passed in the body of the request. You can see what arguments are required in their documentation and examples. In the arguments we pass through, we have set our webhook to fire at the same frequency as BambooHR's rate limit: 1 time every 60 seconds.

What is this?

In the above two nodes, we performing two actions:

1. Checking BambooHR for a record of calls made by it to the webhook URL we registered (provided by PostBin).
2. Retrieving the most recent call made by BambooHR to the webhook URL from PostBin.

About the maker

Find Ludwig Gerdes on LinkedIn

What's happening here?

In this section, we do the following:

1. Extract employee information from webhook call (from PostBin)
2. Create a displayName from each employee's first and last name
3. Combine the names into a list and format the key
4. Ask OpenAI to compose a welcome message with the employee names
5. Post that welcome message to Slack

Test Webhooks in n8n Without Changing WEBHOOK_URL (PostBin & BambooHR Example)

Purpose and structure

This folder contains the Test Webhooks in n8n Without Changing WEBHOOK_URL (PostBin & BambooHR Example) workflow. Its executable nodes use aggregate, bambooHr, chainLlm, debugHelper, filter, httpRequest, lmChatOpenAi, manualTrigger, merge, noOp, outputParserAutofixing, outputParserStructured, postBin, renameKeys, set, slack, splitOut, wait. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

When clicking ‘Test workflow’

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Wait/1977_Wait_Splitout_Automation_Webhook.json MIT; preserve source notices.