Bullhorn

How to integrate Bullhorn with Webflow

Recruiting teams need to publish job listings automatically and capture applications without switching between systems. Manual job posting updates waste time, and disconnected application workflows create data entry overhead that slows candidate processing.

You can connect the platforms through third-party automation tools like Zapier or Make, embed Bullhorn widgets in Webflow pages using HTML, or build custom integrations with the Bullhorn REST API and Webflow Data API.

Use third-party automation platforms

Zapier and Make connect Bullhorn to Webflow without writing code. These platforms authenticate with both services, handle data transformation, and manage errors automatically. Zapier offers a prebuilt template that adds candidates to Bullhorn CRM from new Webflow form submissions.

When someone submits an application through your Webflow career site, Zapier captures the form data and creates a corresponding candidate record in Bullhorn with name, email, phone, and resume attachments.

Make has separate native apps for Bullhorn and Webflow that connect through scenario templates. The platform supports conditional logic for routing candidates to specific workflows based on application details and checking for existing candidates before creating duplicates.

Make's scenario templates can watch Webflow form submissions, create or update candidates in Bullhorn based on Webflow data, and sync job postings from Bullhorn to Webflow CMS collections bidirectionally.

Zapier connects Bullhorn triggers to Webflow actions through multi-step workflows:

• Create candidates from Webflow forms and automatically generate Bullhorn candidate records with parsed data from form fields
• Sync Bullhorn job postings to Webflow CMS and automatically publish them to your careers page through CMS collections when recruiters create jobs in Bullhorn
• Attach application notes from Webflow to Bullhorn and generate timestamped notes whenever candidates submit applications through Webflow
• Prevent duplicate entries between platforms by searching for existing candidate records in Bullhorn before creating new ones

Embed Bullhorn widgets and job boards

Bullhorn provides iframe-based widgets (HTML elements that embed external content within a page) for embedding job boards, application forms, and candidate portals directly into Webflow pages. This method displays Bullhorn-hosted content without requiring API integration, though you must contact Bullhorn support to obtain account-specific embed codes and widget URLs.

Contact Bullhorn support to obtain your account-specific embed code. Bullhorn's iframe integration framework documents authentication methods and configuration parameters, but individual embed URLs contain account-specific identifiers that support teams provide.

Once you have the iframe code from Bullhorn, add an Embed element to your Webflow page through the Add panel ( icon). Paste the Bullhorn iframe code into the embed field. Webflow wraps the content in a <div class="w-embed"> container for responsive design control, and you can adjust dimensions through the Style panel.

For mobile optimization, apply responsive iframe CSS patterns to maintain proper proportions across devices. Test the embedded content across tablet and mobile breakpoints before publishing.

This approach works for several use cases:

• Display current openings from Bullhorn on your Webflow careers page using embedded iframes
• Capture job applications through Webflow forms that connect to Bullhorn via middleware platforms like Zapier or Make, which automatically create candidate records in your ATS
• Embed Bullhorn-hosted candidate portals on Webflow pages to give applicants access to application status and profile updates

Build with Webflow and Bullhorn APIs

Direct API integration gives you complete control over data flow, transformation logic, and synchronization timing. Build custom connections when you need complex workflows, real-time bidirectional sync, or functionality that middleware platforms don't support.

Both platforms use REST APIs with OAuth authentication. Webflow's Data API manages sites, CMS collections, and form submissions. Bullhorn's REST API handles candidates, job orders, placements, and client relationships.

Authentication requires multiple steps for both platforms. Webflow supports OAuth 2.0 tokens for user-authorized access or site tokens for server-to-server integrations. Bullhorn uses a two-phase flow to obtain an OAuth access token through authorization, then complete a login call that returns a session token (BhRestToken) for subsequent requests.

API integration enables several workflows:

• Publish Bullhorn jobs to Webflow CMS with POST /collections/{collection_id}/items and update job status in Webflow when positions close in Bullhorn
• Configure Webflow form webhooks to capture submissions in real-time, then create Bullhorn candidates with PUT /entity/Candidate
• Upload candidate files to Bullhorn using POST /entity/Document after capturing them from Webflow form submissions
• Subscribe to Bullhorn entity events with PUT /event/subscription/{subscriptionId} to receive notifications when candidates, jobs, or placements change, then update corresponding Webflow CMS items

API integration requires managing authentication tokens, handling errors, and implementing retry logic for failed requests. Both platforms enforce rate limits that vary by subscription tier and may require request queuing and exponential backoff strategies. Bullhorn tokens expire after 10 minutes by default and require automated refresh logic, while Webflow tokens expire after 365 days of inactivity.

Sync job postings from Bullhorn to Webflow CMS

Query active job positions from Bullhorn and publish them to your Webflow CMS automatically. This integration pattern keeps job listings current without manual updates, supporting bidirectional synchronization between your ATS and public careers page.

Use Bullhorn's Search endpoint to find open positions with GET /search/JobOrder?query=isOpen:true AND isDeleted:false&fields=id,title,publicDescription,employmentType,address,salary. The query filters for active jobs only, and the fields parameter controls which data returns.

Transform Bullhorn's JobOrder data to match your Webflow CMS collection schema. Create or update items with POST /collections/{collectionid}/items or PATCH /collections/{collectionid}/items/{itemid}. Move staged items to live with POST /collections/{collectionid}/items/publish.

Store Bullhorn's job ID (such as the JobOrder entity ID) in a Webflow custom field to track which CMS items correspond to which JobOrder records. This supports incremental updates that only sync changed data by using Bullhorn's dateLastModified timestamp field to identify modifications since the last synchronization.

Capture form submissions and create candidates

Configure webhooks to receive form data immediately when candidates submit applications through Webflow forms. Create corresponding Bullhorn candidate records using the Bullhorn REST API's PUT /entity/Candidate endpoint without requiring polling for new submissions.

Register a webhook with POST /sites/{site_id}/webhooks, specifying triggerType: form_submission and your endpoint URL. Webflow's webhook documentation explains payload structures and signature verification. Webflow sends POST requests to your endpoint whenever someone submits a form, with the complete payload including form field data and metadata.

Validate the x-webflow-signature header to confirm requests originate from Webflow. Extract form fields from the payload and transform them to Bullhorn's candidate schema using field mapping logic, as Bullhorn uses numeric field IDs while Webflow uses human-readable field names.

Create candidates with PUT /entity/Candidate (Bullhorn uses PUT for create operations, not POST). Include fields like firstName, lastName, email, phone, and source. Link candidates to specific jobs by creating JobSubmission records with PUT /entity/JobSubmission.

Return HTTP 200 to Webflow's webhook request. Non-200 responses trigger retries, which may result in webhook deactivation if failures persist.

Monitor Bullhorn changes with event subscriptions

Subscribe to real-time notifications through Bullhorn's Event Subscription System when entities like job postings and candidates change. Use integration platforms like Zapier or Make to automatically update Webflow CMS items when recruiters modify job postings or candidate statuses in Bullhorn.

Create subscriptions with PUT /event/subscription, specifying entity types (Candidate, JobOrder, ClientContact) and event types (INSERTED, UPDATED, DELETED). Bullhorn queues events for your subscription, which you retrieve by polling the subscription endpoint. Unused subscriptions expire after 7 days, and unretrieved events also expire after 7 days, so continuous polling is required to avoid permanent data loss during integration downtime.

When you retrieve events, Bullhorn returns entity IDs and change types. Fetch full entity details with GET /entity/{EntityType}/{id} using the fields parameter to specify required data. Update corresponding Webflow CMS items with the changed information.

What you can build

Integrating Bullhorn with Webflow through middleware platforms like Zapier or Make lets you build automated candidate pipelines, self-service portals, and bidirectional job synchronization between your ATS and public website.

• Automated career portals with Bullhorn and Webflow: Sync Bullhorn JobOrder records to a Webflow CMS collection at yourcompany.com/careers, automatically publishing job listings when recruiters create positions in Bullhorn. Query active jobs via GET /search/JobOrder?query=isOpen:true and create CMS items with POST /collections/{collection_id}/items, or use Make's scenario template to watch jobs in Bullhorn and update Webflow automatically
• Branded application flows connecting Webflow to Bullhorn: Design custom application forms at yourcompany.com/careers/apply that capture candidate data (name, email, resume, cover letter) and automatically create Bullhorn candidate records via Zapier's prebuilt template or webhook-triggered API calls to PUT /entity/Candidate
• Client job request systems from Webflow to Bullhorn: Create a client portal at yourcompany.com/submit-job-request where hiring managers submit job details through Webflow forms, automatically generating JobOrder records in Bullhorn via Zapier or Make integration to PUT /entity/JobOrder
• Candidate self-service portals on Webflow with Bullhorn data: Embed Bullhorn-hosted status dashboards at yourcompany.com/candidates/portal using iframe embed codes from Bullhorn support, allowing applicants to view interview schedules, update contact information, and track application progress