Breezy HR

Webflow has no built-in applicant tracking, so a static careers page needs a manual edit whenever a position opens or closes. Forms collect applications, but they do not move candidates into a hiring pipeline or push positions out to job boards. Teams that run hiring in Breezy HR end up copying position details between the two systems by hand.

Connecting Breezy HR to Webflow removes that duplication. Published positions appear on your site automatically, either inside an embedded widget or as items in the Webflow CMS. Applications submitted on your site route into Breezy HR's candidate pipeline.

The integration suits HR managers and recruiters who own the pipeline, as well as marketing and web teams responsible for keeping the careers page on-brand. Agencies can offer it as a repeatable client service, using the embed widget for quick setups and CMS sync for clients who want indexed job pages. Breezy HR aims at small and mid-sized businesses, so startups, franchises, nonprofits, and other lean hiring teams get the most from the pairing.

How to integrate Breezy HR with Webflow

What is Breezy HR? Breezy HR is an applicant tracking system built for small and mid-sized businesses. It advertises open positions across dozens of job boards from a single click and manages candidates in a drag-and-drop pipeline behind a customizable hosted career portal. It also automates pre-screening, candidate emails, interview scheduling, and feedback collection.

Teams connect the two once a careers page outgrows manual upkeep. A recruiter publishes a position in Breezy HR and it appears on the Webflow site without anyone editing a page. The Webflow site stays the public, on-brand face of hiring, and Breezy HR stays the source of truth for positions and candidates.

Common ways to connect Breezy HR to Webflow include:

• The Breezy HR embed widget drops live job listings onto any page through a Code Embed element, with no API key or automation account.
• A link to the hosted career portal keeps every position on Breezy HR's side and needs only a button or nav item on your site.
• Zapier and viaSocket sync positions into Webflow Collections and route Webflow form submissions into Breezy HR as candidates.
• The Webflow Data API and Breezy HR API give you full control over job-page sync and candidate creation, but they need server-side development.

Many setups combine two or more of these. The right mix depends on how much control you need over field mapping and whether individual job pages have to be indexable.

Add Breezy HR job listings with a Code Embed element

Breezy HR's inline embed widget shows your published positions on any Webflow page, and the snippet accepts custom CSS so listings match your design. You need Admin access in Breezy HR to generate it. On the Webflow side, the Code Embed element is unavailable on the free Starter plan: a paid Site plan or a paid Workspace plan enables it.

To set up the integration:

1. In Breezy HR, click the gear icon in the left sidebar, then Company Settings.
2. Click Career Site in the left sidebar, then Embed Widget near the top.
3. Choose how to group positions, then copy the embed code.
4. In Webflow, open the Add panel, select Advanced, and drag a Code Embed element onto the page.
5. Paste the snippet, save, and publish the site.

The widget suits teams who want the page to stay current without touching pipeline data:

• Always current: Every published position appears on its own, so the page updates itself when a role opens or closes.
• Styleable: Custom CSS in the snippet lets job listings inherit the typography and spacing of the surrounding page.
• No credentials: Setup needs no API key, webhook, or automation platform account, which keeps the whole thing inside one team's control.
• Not indexed: Individual positions inside the widget are not pages on your domain, so they never earn their own search listings.

That last point is the main reason to look at the CMS methods below. The pattern we see on Webflow sites is a careers page that starts with the widget and moves to CMS sync the first time someone asks why the jobs are missing from search. Embedded code also renders only on the published site or in preview, not on the canvas, so publish before judging the result, and load anything long site-wide through custom code in head and body tags rather than stuffing a single Code Embed element.

Link to the hosted career portal

If you would rather not embed anything, Breezy HR's hosted career portal lists all open positions on its own and needs only a link from your Webflow site. The portal supports custom colors, logo, layout, CSS, and JavaScript, per the career portal customization guide.

To connect the portal:

1. Customize the portal's branding in Breezy HR under Company Settings and Career Site.
2. Add a button or navigation link on your Webflow site pointing to the portal URL.
3. Optionally, create a CNAME record pointing a subdomain such as careers.acme.com at your Breezy HR portal URL, then email support@breezyhr.com to attach it, per the custom domain guide.

Custom portal domains are available on any paid Breezy HR plan, and running multiple portals is limited to Pro plans. This route costs you the on-domain SEO of the CMS methods, so pick it when speed matters more than search.

Connect Breezy HR and Webflow with Zapier or viaSocket

Zapier is the confirmed no-code path, with a dedicated Breezy HR and Webflow pairing page and partner status on Breezy HR's own integrations directory. You connect both accounts and map fields, and nothing gets coded. Build the Webflow Collection and its template page first: mapping fields against a collection that does not exist yet is where these setups stall.

To set up the sync:

1. Open the pairing page and start from one of its prebuilt templates, or build a Zap from scratch.
2. Connect your Breezy HR and Webflow accounts.
3. Pick the Breezy HR trigger, then map position fields such as name, location, description, and salary range to your Webflow Collection fields.
4. Test the Zap and turn it on.

Zapier exposes the pieces you need on both sides:

• New Active Position: This Breezy HR trigger fires the first time a position is set active, which is the natural signal to create a job page.
• Create Live Item: This Webflow action adds the position to a Collection on the published site, so the job page goes live without a separate publish.
• Update Item and Update Live Item: These Webflow actions edit an existing listing, and you pair them with Find Item to locate the record that matches a changed position.
• New Form Submission and Create Candidate: The Webflow trigger passes your application form's fields to Breezy HR's candidate action, landing each applicant in the pipeline.

Zapier checks Breezy HR for position changes on a schedule rather than the moment they happen, so listing syncs are not instant; reach for webhooks when the delay matters. viaSocket runs native connectors for both tools, and its Breezy HR connector and Webflow connector support the same cross-app pairings.

Build with the Webflow and Breezy HR APIs

Calling both APIs directly gives you control over field mapping and publish timing, and it is the only route that lets you own application intake end to end. Custom code on a Webflow site runs client-side only, so the sync logic belongs on external infrastructure such as Cloudflare Workers, Vercel, Netlify Functions, or AWS Lambda. Never call either API from the browser, where tokens would sit in public. Check the Breezy HR side before you build: company endpoints return a 403 when the Developer API feature is not enabled on the plan, and Breezy HR sells API access as an add-on on its top Custom Pro tier.

Four references cover everything this build touches:

• Breezy HR API: Version 3 is rooted at https://api.breezy.hr/v3 and covers companies, positions, candidates, and webhook management.
• Breezy HR authentication: A personal access token goes in the Authorization header as a raw value with no Bearer prefix, created under My Settings in the API Keys tab.
• Webflow CMS endpoints: Version 2 of the Data API handles Collection items and form submissions, authenticated with a Bearer token from a Site Token or an OAuth app.
• Webflow webhooks: The webhooks guide covers registering event subscriptions so the two systems push to each other instead of polling.

Breezy HR rate-limits per token at 100 requests in any 60 second window and returns 429 past that, per its rate limit reference, so batch your CMS writes instead of looping one position at a time.

Sync published positions into the Webflow CMS

This flow reads open positions from Breezy HR and writes them as Collection items, so each position gets its own page on your domain.

To build the sync:

1. Fetch open positions with GET /v3/company/{company_id}/positions?state=published. Valid state values are published, draft, archived, closed, and pending, and omitting the parameter leaves archived positions out.
2. List existing items with GET /v2/collections/{collection_id}/items (scope cms:read) to decide between create and update.
3. Create up to 100 items per request with POST /v2/collections/{collection_id}/items/bulk (scope cms:write). Each item's fieldData needs name and slug. Update with PATCH /v2/collections/{collection_id}/items, also capped at 100, including each item's id.
4. Publish with POST /v2/collections/{collection_id}/items/publish, passing an itemIds array.

The Webflow CMS holds 50 items on the Starter plan and 20,000 on Premium, so check the ceiling before you sync a large board. Bind a Collection List to the collection and every synced position renders as a native, crawlable page.

Trigger the sync in real time with Breezy HR webhooks

Instead of polling, Breezy HR webhooks push position events to your handler the moment they happen. They are limited to Pro plans, and you register them by posting to /v3/company/{company_id}/webhook_endpoints with a list of events; Breezy HR's webhook setup guide walks through the call. Delivery is HTTPS-only.

Four Breezy HR events map cleanly onto CMS actions:

• companyPositionAdded fires when a position is created, which is your cue to create a Collection item.
• companyPositionUpdated fires when position details such as name or description change, so patch the matching item.
• companyPositionStateUpdated fires on state transitions and carries state_is and state_was, which tells you whether to publish or unpublish.
• companyPositionDeleted fires when a position is removed, so delete or archive the item.

State changes fire only companyPositionStateUpdated and never companyPositionUpdated, so handle both events or you will miss half the lifecycle. Verify every request against the X-Hook-Signature header, an HMAC-SHA256 signature of the request body, before you write to the CMS. When a payload arrives with state_is set to published, call the bulk create and publish endpoints above.

Route Webflow applications into Breezy HR

This flow captures applications through your own Webflow form and creates candidate records in Breezy HR.

To implement it:

1. Register a webhook with POST /v2/sites/{site_id}/webhooks (scope sites:write), using triggerType: "form_submission" and your handler URL. The trigger can filter by form name.
2. In your handler, read the submission payload's data object, which holds the form's field names and values.
3. Create the candidate with POST /v3/company/{company_id}/position/{position_id}/candidates.

Breezy HR's candidate endpoint always requires name, and email_address becomes required when origin is applied, which also runs the person through the public application path and expects the position to be published. Optional fields cover phone_number, address, summary, tags, source, work_history, education, social_profiles, custom_attributes, and cover_letter. A duplicate on the same position returns 409, so search by email before you create. If you would rather poll than receive webhooks, GET /v2/sites/{site_id}/form_submissions (scope forms:read) lists submissions across the site.

What you can build with the Breezy HR Webflow integration

Connecting Breezy HR to Webflow gets you a self-updating, on-brand careers site without hand-editing job listings or pushing applicants onto an off-brand portal.

These are the setups worth building first:

• Embedded jobs board: Paste the embed widget into a Code Embed element on your careers page. Published positions appear in a styled list, and a position closed in Breezy HR disappears without anyone touching the page.
• Indexable job pages: Sync positions into Collections through Zapier or the API. Each position renders at its own URL, such as /careers/senior-designer, built from one Collection template page.
• Application intake with pipeline routing: A Webflow application form feeds Breezy HR's Create Candidate action. Every submission lands as a candidate card in the pipeline with follow-up already automated.
• Auto-unpublished closed roles: The companyPositionStateUpdated webhook, or a Zapier update flow, unpublishes a job's Collection item the moment the position closes.

If you want the CMS route without renting an automation platform, get started with the CMS API and build the position sync against your own handler.

A careers board that spans dozens of Collection items gets easier to run once an agent can query the site directly. Connect the Webflow MCP server to your AI client and you can audit which job pages have gone stale and unpublish roles that closed weeks ago, in the same session where you review the copy.