Hireflow Lever Integration - What It Does and When to Use It

The Hireflow integration with Lever connects sourcing activity directly to your applicant tracking system so you can move candidates from discovery to pipeline without manual data entry. It detects existing records in Lever while you source on LinkedIn, creates new prospects automatically, and advances candidates based on outbound email activity and replies. This article explains the integration’s capabilities, practical scenarios for use, setup and mapping considerations, monitoring and troubleshooting steps, and guidance on when the integration will deliver the most operational value.

At a glance, the integration reduces duplicate records, reduces time spent copying candidate data into Lever, and ensures follow-up events are reflected in the ATS. It accomplishes this by performing three core actions: existence checks in Lever during sourcing, automated prospect creation, and automated stage progression tied to email sends and replies.

Core features — what the integration actually does

• Existence check while sourcing Hireflow queries Lever in real time to show whether a LinkedIn profile or prospect already exists in your ATS, preventing duplicates and giving sourcers visibility into prior interactions.
• Automatic prospect creation When a sourced candidate is not found in Lever, Hireflow can create a prospect record automatically using mapped fields (name, email, company, title, source).
• Progression triggers Send an email or receive a reply from a prospect in Hireflow and the integration can automatically advance that person to a defined stage in Lever (e.g., Outreach → Interested).
• Selective sync You control when records sync — some teams sync every sourced contact; others only push contacts after a warm response or manual approval.
• Field mapping Map Hireflow fields to Lever custom fields to preserve sourcing context, tags, and campaign metadata for downstream reporting.

Trigger-action mapping: Hireflow events to Lever actions

When to use: sourcing at scale. If your sourcers routinely review dozens of LinkedIn profiles per day, the real-time existence check prevents re-sourcing candidates already in Lever and preserves historical context. Use the integration to enforce single-source-of-truth records and reduce time spent reconciling duplicates across systems.

When to use: automated engagement and follow-up. Teams that run outbound sequences benefit when email sends and replies automatically update the ATS stage. This keeps recruiters and hiring managers aligned on candidate progress without requiring manual status changes after every outreach or reply.

Pre-integration checklist

• API access and admin rights Ensure you have a Lever admin account or an API key with sufficient scopes to create and update prospects, read candidate records, and change stages.
• Field inventory Document the Lever fields (standard and custom) you want populated by Hireflow, and identify any fields that must be mandatory.
• Naming and tags standard Agree on consistent naming for sources, campaigns, and tags so data remains clean after automated syncs.
• Data retention and consent Confirm your candidate data retention policies and that sourcing activities comply with consent requirements for your region.
• Pilot group Start with a small team to validate mappings and triggers before enabling organization-wide syncing.

Field mapping and data hygiene: map only what you need. Common fields to sync are name, email, current company, current title, LinkedIn URL, source, and initial outreach method. Avoid mapping fields that duplicate existing information or create noise; instead use Lever’s custom fields for campaign metadata and a single 'sourced via' field to track origin consistently.

Sample workflows and expected operational outcomes

Common questions about the integration

Troubleshooting checklist for common failures

• Authentication errors Verify the Lever API key and scopes haven't expired and that the account has required permissions.
• Missing fields after sync Check mapping configuration in Hireflow and ensure required Lever fields are not set to 'system only' or hidden.
• Stage not advancing on reply Confirm the rule conditions match the reply content and that Hireflow received the inbound email; review logs for webhook delivery failures.
• Duplicate records persist Ensure matching logic uses reliable unique identifiers (email, LinkedIn URL) and run an initial dedupe in Lever before broad syncing.

Metrics to monitor and KPIs: track time-to-create (how long it takes to get a sourced candidate into Lever), reduction in manual data entry hours, duplicate rate, and conversion rate from outreach to reply. A successful integration should reduce time spent on administrative tasks and increase the proportion of sourced candidates with complete ATS records.

Security and permissions: limit the integration’s API key to the minimal scope required. Audit created records regularly, and configure role-based access in Lever so that only designated users can approve stage changes or edit sensitive fields. Maintain an access rotation policy for API credentials and monitor activity logs for unexpected behavior.

Limitations and when not to use the integration: if your hiring process relies on heavy manual qualification before any ATS record should exist (for example, strict pre-screening by sourcers), automatic creation may clutter the ATS. Also, if your team uses a different canonical system for candidate data or has compliance constraints that prevent automated syncing, pause the integration and use a manual push workflow instead.

Operational best practices: run a short pilot with a single team, document and enforce naming conventions for campaigns and tags, schedule a weekly review of newly created records to correct mapping issues, and iterate on the rules that trigger stage changes. Treat the integration as a way to automate routine steps while keeping human decision points for qualification and final progression.