BambooHR

A careers page built in Webflow lists jobs as Webflow CMS items or static text that someone edits by hand. The jobs themselves live in an applicant tracking system, and employee records live in an HR database. Webflow has no built-in connection to BambooHR, so every new job, title change, or departure becomes a manual site update. Within a few weeks, the site no longer matches the HR system.

Connecting BambooHR to Webflow closes that gap from both sides. BambooHR's embed code drops a live Open Positions widget onto any Webflow page. Automation platforms and the two APIs copy job openings and employee records into Webflow CMS items that you style like any other content. Webflow form submissions can flow the other direction and create applicant or employee records in BambooHR.

HR managers and People Ops leads get the most out of this, because publishing a role stops depending on a web request. It also helps marketing and web managers who own the Webflow site without owning BambooHR, and freelancers and agencies building careers and team components that read live from a client's BambooHR account.

How to integrate BambooHR with Webflow

What is BambooHR? BambooHR is an HR platform that acts as the system of record for people, payroll, benefits, time, hiring, and performance. Its applicant tracking system covers job posting through onboarding, and its HR data module includes a People Directory and Org Chart searchable by department, location, or team. The BambooHR Marketplace advertises over 150 integrations, and it carries no Webflow listing: its listing slug for Webflow returns a 404 while comparable slugs such as the Zapier one resolve.

Teams pair the two when hiring and staffing data already lives in BambooHR and the public site needs to match it. Manual website updates create delays between HR system changes and what visitors see, so a careers page keeps showing filled roles and a team page keeps listing people who left. The hosted BambooHR careers site carries your company logo and primary color, and its guide documents no other styling controls. Companies that want listings on their own domain, in their own design, bring the data into Webflow instead.

The BambooHR-Webflow integration supports three approaches:

• BambooHR's embed code places the live Open Positions widget on a Webflow page through a Code Embed element, with no code of your own.
• Zapier, Make, n8n, or IFTTT copy employee and job records into Webflow CMS items and route Webflow form submissions into BambooHR.
• The Webflow and BambooHR APIs give you full control over CMS sync, applicant creation, publishing, and webhooks, but require server-side development.

Most implementations combine two or more of these methods depending on the complexity of the setup.

Add the BambooHR Open Positions widget with Code Embed

BambooHR generates an embed code from its Hiring tab that renders an Open Positions widget on an external site. Paste it into a Code Embed element and, per BambooHR's recruiting guide, the widget updates in real time and links candidates straight into the ATS when they click a posting. This is the fastest path for a founder or HR generalist without a developer. Custom code needs a Core, Growth, Agency, or Freelancer Workspace or an active Site plan; the free Starter plan does not include it. If you cannot upgrade yet, link to the hosted careers site instead.

Link to the BambooHR hosted careers website

BambooHR hosts a careers site for every account, and linking to it needs no code or plan change on either side. It lists your open roles with the same company logo and primary color BambooHR applies elsewhere.

To link to the hosted careers site:

1. In BambooHR, open the Hiring tab and click View Careers Website in the upper right corner.
2. Copy the URL of the page that opens.
3. In Webflow, add a Button or Text Link to your site and paste the URL as its link destination.
4. Publish the site.

Applicants leave your domain the moment they click, so treat this as a placeholder until you can run the widget or a CMS sync.

Paste the embed code into a Code Embed element

The embed code keeps applicants on your Webflow page until they choose a specific posting. Each Code Embed element accepts up to 50,000 characters of HTML, CSS inside <style> tags, and JavaScript inside <script> tags. Server-side languages such as PHP, Python, or Ruby do not run inside it.

To add the widget:

1. In BambooHR, open the Hiring tab and click Get Embed Code in the upper right corner.
2. Copy the code.
3. In Webflow, open the Add panel and drop a Code Embed element onto your careers page.
4. Paste the code into the element and click Save and close.
5. Publish the site. The widget does not render on the live domain until you publish.

The jobs render client side from BambooHR and each posting links off your domain, so no individual role gets a URL of its own on your site, and the guide documents no CSS hook for restyling the widget. When search visibility or full design control matters, sync the jobs into the CMS with one of the methods below.

Connect with Zapier, Make, n8n, or IFTTT

Zapier, Make, n8n, and IFTTT each carry both a BambooHR connector and a Webflow connector, so records move between the two without server code. Zapier publishes a BambooHR pair page with two prebuilt templates, and IFTTT documents a ready-made trigger and action combination on its BambooHR page. Make carries connectors for both products but publishes no prebuilt pair template. On Zapier you generate a BambooHR API key first, per BambooHR's Zapier partner article, then connect Webflow as described in Webflow's Zapier article.

The direct trigger and action pairs cover both directions:

• Webflow New Form Submission → BambooHR Create Employee through a published Zapier form template.
• BambooHR New Employee → Webflow Create Item or Create Live Item through a published Zapier employee template.
• BambooHR Updated Employee (Zapier) → Webflow Update Item, so a title or department change reaches the team page.
• BambooHR Terminated Employee (Zapier) or Employee terminated (IFTTT) → Webflow Update Item or Create collection item, to archive or flag the departed person's entry. IFTTT documents this as a polling trigger rather than a push, so the update lands on the next check.
• A scheduled Make scenario polling the BambooHR ATS → Webflow Create or Update Item, which fills a careers Collection with open roles. The setup path is in Webflow's Make help article.
• n8n schedule trigger → BambooHR Employee: Get Many → Webflow Item: Create or Update, for teams running n8n themselves.

Zapier's form template creates an employee record, not a candidate, so ATS applicant creation still needs an HTTP step against the BambooHR ATS endpoint or the API path below. BambooHR publishes no job-opening webhook events either, so every job sync on these platforms polls on a schedule and lags by the polling interval.

Build with the Webflow and BambooHR APIs

The APIs give you control over which fields cross between systems, when CMS items publish, and how applicants enter the ATS. BambooHR's deprecation notice reserves the older API-key flow for existing integrations and directs new ones to OAuth 2.0. Where an API key is still in play it goes over HTTP Basic Auth, with the key as the username and any string as the password. The key inherits the permissions of the user who created it, and ATS endpoints require that user to have access to ATS settings. Webflow's Data API takes a Bearer token, either a site token or an OAuth token; relevant scopes include cms:write plus sites:write and forms:read.

• BambooHR API handles the employee directory and webhook management at https://{companyDomain}.bamboohr.com/api/v1/
• BambooHR ATS endpoints cover job openings and candidate creation under the hiring:applications and hiring:applications.write scopes, and require a caller with access to ATS settings
• Webflow's Data API handles CMS collections and form submissions at https://api.webflow.com/v2/
• Webflow webhooks trigger real-time events such as form_submission and collection_item_changed

A site token is shown once when you generate it and expires after 365 consecutive days of inactivity, so keep it in the same secrets store as the BambooHR credential.

Ask an agent to read BambooHR and drive Webflow

Both products now expose an MCP server, so an assistant can read hiring data and edit the site without you writing the glue. BambooHR's MCP server is in closed beta at the time of writing, needs the AI Connectors app switched on by an admin, and enforces the caller's existing BambooHR permissions. Its own documentation flags the trap worth knowing before you trust an answer: when a caller cannot read a field, some tools silently omit it and the roster tool drops those people from the result entirely, so a short list means "nothing this caller can see", never "nothing exists". On the Webflow side the Webflow MCP server covers collections, items, pages and publishing under your existing roles and permissions, which is the half of this workflow that never touches employee data.

Sync job openings into a Webflow CMS Collection

A scheduled job pulls open roles from the BambooHR ATS and upserts them as CMS items. Each job becomes a Collection page with its own URL on your domain, which the embed widget cannot give you. Because BambooHR has no ATS webhook events, polling is the only trigger.

To build the sync:

1. Call GET https://{companyDomain}.bamboohr.com/api/v1/applicant_tracking/jobs with statusGroups=Open. The job summaries endpoint takes no paging parameters and returns the matching jobs as one array: ID, title, posted date, location, department, status, hiring lead, applicant counts, and the posting URL.
2. Create a Jobs Collection in Webflow with fields for title, department, location, and apply link, plus a plain-text BambooHR Job ID field as the upsert key. Confirm the schema with GET /v2/collections/{collection_id}.
3. For each job, look up the item by BambooHR Job ID. Create missing items with POST /v2/collections/{collection_id}/items/bulk, which accepts up to 100 items per request under the cms:write scope, and update existing ones with PATCH /v2/collections/{collection_id}/items/{item_id}.
4. Items created through the staged endpoint are drafts. Publish them with POST /v2/collections/{collection_id}/items/publish, or write to /v2/collections/{collection_id}/items/live to publish on creation.
5. Archive or delete items whose BambooHR Job ID no longer appears in the Open list with DELETE /v2/collections/{collection_id}/items.

Render the Collection on your careers page with a Collection List, and store the postingUrl the same response returns as each item's apply link so candidates land in the ATS.

Send Webflow application forms to the BambooHR ATS

A Webflow form on your careers page can create an applicant in the BambooHR hiring pipeline instead of an employee record. A form_submission webhook posts each entry to your endpoint, which maps the fields and calls the ATS. Résumé uploads use Webflow's form file upload field, which needs a Premium Site plan or an Ecommerce plan and accepts a single file of up to 10MB, PDF included.

To wire the form:

1. Build the form in Webflow with First Name and Last Name fields and a job dropdown or hidden field that carries the BambooHR jobId. Pre-fetch valid IDs from GET /api/v1/applicant_tracking/jobs.
2. Register the webhook with POST /v2/sites/{site_id}/webhooks under the sites:write scope. Add a filter object to target one form: the reference supports filter only for the form_submission trigger, and caps registrations at 75 per trigger type per site.

{
  "triggerType": "form_submission",
  "url": "https://your-middleware-endpoint.example.com/webhook"
}

3. On receipt, verify the x-webflow-timestamp and x-webflow-signature headers with SHA-256 HMAC and reject any request whose timestamp is more than 5 minutes old, per Webflow's webhook signature guide.
4. Map payload.data keys to firstName, lastName, and jobId, then call POST /api/v1/applicant_tracking/application as multipart/form-data. The create candidate endpoint returns a candidateId, and the calling user needs access to ATS settings.
5. Store the Webflow event payload.id alongside the returned candidateId and check it before each call, so a retried webhook cannot create a duplicate applicant.

The form submission payload also carries payload.schema, and you can log that with payload.formId and payload.submittedAt for troubleshooting without forwarding any of it to BambooHR.

Update a team page from BambooHR employee webhooks

Employee changes, unlike job openings, can drive Webflow updates in real time. BambooHR fires employee.created, employee.updated, and employee.deleted events to an HTTPS endpoint, and your middleware fetches the changed record and upserts the matching CMS item. Global Webhooks are configured by an admin in Account Settings under Webhooks; permissioned webhooks are created through the API and carry the creating user's access level.

To build the webhook receiver:

1. Create the webhook with POST /api/v1/webhooks according to BambooHR's create webhook reference. Name the events explicitly, because a webhook created without an events array falls back to BambooHR's legacy employee_with_fields events. Store the returned privateKey immediately: it is returned only at creation and cannot be retrieved again.

{
  "name": "Webflow Team Page Sync",
  "url": "https://your-middleware.example.com/bamboohr-webhook",
  "format": "json",
  "events": ["employee.created", "employee.updated", "employee.deleted"],
  "monitorFields": ["firstName", "lastName", "jobTitle", "department", "location", "status"]
}

2. On each POST, verify X-BambooHR-Signature by computing an HMAC-SHA256 over the raw body plus X-BambooHR-Timestamp with the stored private key, as described in the webhooks overview.
3. For employee.created and employee.updated, read data.employeeId and data.changedFields from the employee.updated payload, then fetch the record with GET /api/v1/employees/{employeeId} or GET /api/v1/employees/directory.
4. Fetch the photo with GET /api/v1/employees/{employeeId}/photo/{size}, where size is one of original, large, medium, small, xs, or tiny, and upload the bytes to Webflow as an asset rather than hotlinking anything BambooHR returns.
5. Query the Team Collection by a plain-text BambooHR ID field, then PATCH the item if it exists or POST it if new. On employee.updated, archive or delete the item when the monitored status field shows that the employee has been terminated or is otherwise no longer current. Reserve employee.deleted handling for actual deletion of the employee record, then archive or delete the corresponding item and publish.

Both employee.created and employee.updated fire in sequence when a new employee is added, so make the upsert idempotent. BambooHR retries a delivery up to five times when the network fails or your endpoint returns a 500 level status, immediately and then after 5, 10, 20, and 40 minutes with jitter, and the delivery log covers the last 14 days up to 200 entries. Monitor only the fields you intend to publish. BambooHR's monitorable list includes SSN, Pay Rate, Birth Date and Home Email, and a CMS item on a published site is readable by anyone who can reach the page, so anything you sync becomes public the moment the item does.

What you can build with the BambooHR Webflow integration

Integrating BambooHR with Webflow lets you publish hiring and team data on your site without re-entering it by hand.

• Embedded careers page with live openings: Sealevel Construction runs the widget on a Webflow-built careers page, grouping open roles under five departments and sending each application to sealevelinc.bamboohr.com/careers/<id>.
• Job board on your own domain: A Jobs Collection filled by the API or a scheduled automation gives every role its own Collection page on your domain, styled in Webflow, with an apply button that hands the candidate to the BambooHR ATS.
• Team directory that updates itself: A Team Collection fed by employee.created, employee.updated, and employee.deleted webhooks shows current names, titles, departments, and photos. Monitoring the employee status field lets an employee.updated event remove a person's card during offboarding, while employee.deleted is reserved for actual record deletion.
• Application and new-hire intake forms: A Webflow application form posts candidates into the ATS through POST /api/v1/applicant_tracking/application, while an internal onboarding form uses the Zapier template to create the employee record with required fields populated before day one.

If you need more control over two-way sync, applicant creation, or publish timing, the API path covers all three. See how we automate job listings end to end.