Greenhouse

If your team manages hiring through an ATS, there is no native way to pull open roles, department filters, or application forms into your Webflow site. That gap forces manual updates every time a position opens or closes.

Adding Greenhouse to Webflow solves that problem by giving recruiting and marketing teams a shared system for careers content. Open positions can appear automatically on your Webflow careers page, candidates can browse and apply without leaving the site, and job data stays current without manual re-publishing. Teams that need SEO-indexed job pages can sync listings directly into the Webflow CMS for full design control.

This integration is most relevant for talent acquisition teams, HR managers, marketing teams responsible for employer branding, and Webflow agencies building careers pages for clients. Companies ranging from early-stage startups to enterprise organizations with distributed hiring use these methods depending on their technical resources and candidate experience goals.

How to integrate Greenhouse with Webflow

What is Greenhouse? Greenhouse is an applicant tracking system and hiring platform that covers sourcing, interviewing, and onboarding. The platform supports structured hiring workflows, configurable job boards with multiple embed options, and a public API for integrating job data with external websites. Greenhouse is used by companies like Robinhood, HelloFresh, and Anthropic across a range of industries and company sizes.

Teams use Greenhouse and Webflow together when they want their careers page to reflect the same design standards as the rest of their marketing site. Instead of linking candidates to a generic hosted job board, this integration lets you embed listings, sync job data into CMS collections, or build fully custom application experiences — all while keeping Greenhouse as the single source of truth for recruiting data.

The Greenhouse-Webflow integration supports 5 approaches:

• Greenhouse embed widgets display a live job board on any Webflow page without writing code.
• Byteline, Zapier, and Make sync Greenhouse job data to Webflow CMS items for SEO-indexed, fully styled listings.
• Zapier and Make automations connect Webflow form submissions to Greenhouse candidate records and trigger CMS updates when jobs change.
• The Webflow and Greenhouse APIs give you full control over job display, application submission, and real-time data sync, but require server-side development.

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

Embed the Greenhouse job board with a Code Embed element

The fastest way to display Greenhouse job listings on a Webflow page is through Greenhouse's iFrame embed. This method requires no coding or automation setup. Greenhouse provides a two-part embed code — a container div and a script tag — that renders a live, auto-updating job board directly on your page. Candidates can browse open roles, filter by department or location, and submit applications without leaving your site. You can find the embed code in Greenhouse at Configure > Job Boards & Posts > select your board > Dev Center > Embed Code.

To set up the embed:

1. In Greenhouse, go to Configure > Job Boards & Posts, select your board, and open Dev Center. Copy both the container div (<div id="grnhse_app"></div>) and the script tag (<script src="https://boards.greenhouse.io/embed/job_board/js?for=YOUR_TOKEN"></script>), replacing YOUR_TOKEN with your job board token.
2. In Webflow, open the page where the job board should appear. From the Add panel, drag a Code Embed element to the desired location. Double-click the element, paste <div id="grnhse_app"></div>, and click Save & Close.
3. Go to Site settings > Custom code and paste the <script> tag in the Footer code section. Click Save changes. Alternatively, add the script to the specific page by opening Page settings > Custom Code > Before  tag.
4. Publish the site and verify the job board loads in a live browser. Custom code does not render in the Webflow canvas preview.
5. In Greenhouse, go to Configure > Job Boards & Posts > Edit > Dev Center, add your Webflow careers page URL to the Job Board URL field, and click Update tracking links to the URL below to route source attribution correctly.

The embed supports these capabilities out of the box:

• Live job listings that update automatically when positions open or close in Greenhouse
• Department and location filtering via dropdown menus
• Application forms that submit directly to Greenhouse — no Webflow form processing involved
• Visual customization through Greenhouse's Design Studio at Configure > Job Boards & Posts > Open Design Studio, where you can configure colors, fonts, button shapes, and field label positions

The Code Embed element requires a paid Webflow site plan. Webflow CSS cannot reach inside the Greenhouse iFrame due to the browser's same-origin policy, so all styling of the board UI must be done through Greenhouse's Design Studio. Content inside the iFrame is not indexed by search engines, so this method works well for functional careers pages but not for SEO-focused job listings.

Sync jobs to Webflow CMS with Byteline

For teams that need SEO-indexed job pages with full design control, syncing Greenhouse data into Webflow CMS items is the recommended approach. Byteline is the only Greenhouse-to-Webflow sync tool with dedicated documentation in Greenhouse's own support center. It pulls job data from Greenhouse and creates corresponding CMS items in Webflow — no code required. Each job gets its own URL on your domain, rendered as standard HTML that search engines can index.

To set up the sync:

1. Log in to Byteline and create a new sync.
2. Select Greenhouse as the source and Webflow as the destination.
3. Connect both accounts by authenticating with your Greenhouse and Webflow credentials.
4. Configure field mappings between Greenhouse job fields and your Webflow CMS collection fields. Available Greenhouse fields include job name, title, content (rich text description), location name/ID, status, department, office, hiring managers, requisition ID, created/updated/opened/closed dates, questions, job post ID, and custom fields.
5. Click Start Sync.

Once the sync is active, new jobs published in Greenhouse automatically appear as CMS items in Webflow. Closed positions are removed or archived. You can style job listing pages and detail pages using Webflow's visual tools, add Collection Lists with department or location filters, and embed employer branding content alongside live job data.

Keep in mind that Webflow CMS item limits are plan-gated. The CMS plan supports 2,000 items and the Business plan supports 10,000 items base (up to 20,000 with add-ons). Organizations with large job catalogs should confirm their Webflow plan has enough capacity before enabling the sync.

Connect with Zapier or Make

Both Zapier and Make support direct Greenhouse-Webflow connections. These automation platforms let you build workflows that trigger when events happen in either system — a Greenhouse trigger can create or update Webflow CMS items, and a Webflow trigger can send form submission data to Greenhouse.

Zapier offers pre-built templates for common workflows and supports these triggers and actions:

• Greenhouse trigger: New Candidate Application → Webflow action: Create CMS item
• Greenhouse trigger: New Job Post → Webflow action: Create CMS item
• Webflow trigger: Form Submitted → Greenhouse action: API Request to create a candidate or prospect

Make also supports direct Greenhouse-Webflow workflows, including:

• Greenhouse trigger: New Job Post → Webflow action: Create CMS item
• Webflow trigger: Form Submitted → Greenhouse action: Add Application to Candidate
• Webflow trigger: Form Submitted → Greenhouse action: Add Application to Prospect

Greenhouse is a premium Zapier app, so a paid Zapier plan is required. Greenhouse's own documentation notes that the Zapier integration works for up to 100 jobs — organizations with more concurrent open roles should use Make, Byteline, or a direct API approach instead.

Sync job posts to Webflow CMS via Zapier

This workflow keeps your Webflow careers page in sync with Greenhouse without manual updates. When a new job post goes live in Greenhouse, Zapier creates a corresponding CMS item in Webflow.

To set up the workflow:

1. In Zapier, create a new Zap with Greenhouse as the trigger app and select New Job Post as the trigger event.
2. Authenticate your Greenhouse account and test the trigger to pull in a sample job post.
3. Add Webflow as the action app, select Create Item as the action event, and authenticate your Webflow account.
4. Map Greenhouse fields (job title, location, department, description) to the corresponding fields in your Webflow CMS collection.
5. Turn on the Zap.

New jobs will appear as draft CMS items in Webflow. To publish items immediately, you'll need to use the Publish endpoint or configure an additional step in your automation to make items live after creation.

Route Webflow form submissions to Greenhouse

If you collect initial candidate interest through a Webflow form — for example, a "Join our talent network" form — you can route those submissions to Greenhouse as prospect records.

To set up the workflow:

1. In Zapier, create a new Zap with Webflow as the trigger app and select Form Submitted as the trigger event.
2. Add Greenhouse as the action app and select API Request to create a candidate or prospect in Greenhouse.
3. Map form fields (name, email, area of interest) to the corresponding Greenhouse candidate fields.
4. Test the Zap with a form submission and verify the record appears in Greenhouse.

This approach works for talent community forms and general interest submissions. For full job application forms with resume uploads, a server-side proxy is required — see the API section below.

Build with the Webflow and Greenhouse APIs

For teams that need complete control over how jobs are displayed, how applications are submitted, or how data flows between systems in real time, a direct API integration is the most flexible path. This approach requires server-side development and is best suited for engineering teams or agencies building custom careers experiences.

The relevant APIs are:

• The Greenhouse Job Board API provides unauthenticated read access to published jobs, departments, offices, and job detail pages — including the questions array needed to build dynamic application forms
• The Greenhouse Harvest API handles candidate management, application lifecycle updates, and job post status changes via authenticated endpoints
• The Webflow Data API handles CMS collections and item management for creating, updating, and publishing job listings
• Greenhouse webhooks trigger real-time events like job_created, job_updated, and hire_candidate to keep Webflow CMS data current

The Harvest API v1/v2 is deprecated and will be removed on August 31, 2026. New integrations should target Harvest v3.

Fetch and display job listings

The Job Board API returns published jobs without authentication, making it suitable for client-side rendering on Webflow pages.

To display job listings:

1. Call GET https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs?content=true to retrieve all published jobs with full descriptions. For department-grouped display, use GET /v1/boards/{board_token}/departments instead — it returns jobs nested inside each department.
2. Parse the JSON response and render job cards using JavaScript injected via a Code Embed element or the site's custom code section.
3. Link each job's apply button to the absolute_url field for Greenhouse-hosted applications, or fetch GET /v1/boards/{board_token}/jobs/{job_id} to retrieve the questions array and build a custom form.

Content rendered client-side via JavaScript may experience indexing delays with search engines. For reliable SEO indexing, sync jobs to Webflow CMS items using the approach below.

Sync jobs to Webflow CMS via API

This approach stores each Greenhouse job as a Webflow CMS item, giving you server-rendered HTML pages with full design control.

To implement the sync:

1. Fetch jobs from Greenhouse: GET https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs?content=true. Store the id and updated_at fields for deduplication.
2. Create CMS items in Webflow: POST https://api.webflow.com/v2/collections/{collection_id}/items with Authorization: Bearer <token> and scope cms:write. Map title → name, derive slug from title, and map location.name, content, and id (as greenhouse-job-id) to your collection fields.
3. For existing items, compare greenhouse-job-id and updated_at against current CMS items. Update changed records with PATCH https://api.webflow.com/v2/collections/{collection_id}/items.
4. Archive removed jobs by setting isArchived: true on items no longer present in the Greenhouse feed via PATCH https://api.webflow.com/v2/collections/{collection_id}/items. Archiving preserves URLs better than deletion.
5. Publish updated items: POST https://api.webflow.com/v2/collections/{collection_id}/items/publish.

For real-time updates, configure Greenhouse webhooks for job_created, job_updated, job_post_updated, and hire_candidate events. Deploy a serverless function (AWS Lambda or Vercel) as the webhook receiver. Greenhouse signs each payload with HMAC-SHA256 — verify the signature before processing.

Submit applications via a custom form

The Greenhouse Job Board API requires application submissions to be proxied through your server. The official documentation explicitly states that the POST endpoint cannot be called directly from browser-side code because it requires HTTP Basic Auth with your API key.

To implement custom application submission:

1. Fetch the job's questions array from GET /v1/boards/{board_token}/jobs/{job_id} and dynamically render form fields in Webflow based on each question's type and required flag.
2. Intercept the form submission with JavaScript using preventDefault(), build a FormData object, and POST it to your serverless proxy endpoint.
3. Your proxy forwards the request to POST https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs/{job_id}/applications with Content-Type: multipart/form-data and the Authorization: Basic <base64(api_token:)> header.
4. Handle success and error states in JavaScript — Webflow's native form states will not trigger when using a custom submission flow.

Greenhouse will not reject submissions missing required fields, so client-side validation is necessary. If your Greenhouse account uses GDPR Explicit Consent, you must fetch and render the consent question from the dynamic field list — the iFrame embed handles this automatically, but a custom form does not. Candidate PII passes through your proxy infrastructure, which makes your server a data processor under GDPR.

What can you build with the Greenhouse Webflow integration?

Integrating Greenhouse with Webflow lets you run your entire careers experience from your own domain without manually updating job listings or redirecting candidates to external pages.

• Auto-updating careers page: Embed the Greenhouse job board on a Webflow page so open positions appear and disappear automatically as roles change in Greenhouse. Companies like Greenhouse itself use this approach on their own Webflow-built careers site.
• SEO-indexed job listings: Sync Greenhouse jobs to Webflow CMS items so each position gets its own page on your domain, fully indexable by search engines and styled with your brand's visual system. This is particularly valuable for companies competing for organic candidate traffic in technical roles.
• Multi-location job board with filters: Store jobs, departments, and offices as separate CMS collections connected via Reference fields. Use Collection Lists with conditional visibility or filtering to let candidates browse by team, location, or role type — similar to how Flatiron Health handles open positions across departments.
• Branded application forms: Build custom application forms in Webflow that match your site's design, then submit candidate data to Greenhouse through a server-side proxy. Candidates complete the entire application without leaving your domain, which keeps the experience consistent with the rest of your marketing site.

If you need more control over real-time job status updates or candidate pipeline data, the API integration path covers those cases with full flexibility.