
Connect Your Funnel Builder With Tellent Recruitee






Trusted by 3,000+ marketers
Recruitee's default application forms convert well enough for organic candidates who are already sold on the role. When you drive paid traffic from Meta, LinkedIn, or TikTok to those same forms, the experience falls apart. Connecting a funnel builder to Tellent Recruitee solves two problems at once: a multi-step candidate experience that qualifies applicants before they reach your ATS, and closed-loop ad tracking that feeds real conversion signals back to the algorithm.
Key takeaways
Static Recruitee forms lack conditional logic and mobile optimisation, making them a poor fit for paid social recruiting campaigns.
Passing UTM parameters through hidden funnel fields to Recruitee custom fields enables genuine source-of-hire reporting without manual attribution work.
Heyflow connects natively to Recruitee with no middleware, supports multi-role job routing via Job GUID, and sends server-side conversion signals to Meta CAPI and TikTok Events API.
Why Static Recruitee Forms Fail Paid Recruiting Campaigns
Recruitee's built-in career page forms are designed for organic applicants who are already motivated to apply. When you drive paid traffic from Meta, LinkedIn, or TikTok to those same forms, conversion rates collapse. The experience is static, rarely mobile-optimised, and offers no conditional logic to guide candidates through a qualifying conversation. Every extra field and every moment of friction costs you candidates you already paid to attract.
Research shows that applications exceeding 15 minutes see 365% higher abandonment. Multi-step funnels solve this by breaking the application into digestible screens, showing progress, and only asking each question at the right moment. The result is higher completion rates and better candidate quality before anyone reaches your Recruitee pipeline.
The second problem is the tracking gap. Without server-side conversion signals flowing back to Meta or TikTok, the ad algorithm optimises for clicks and form opens, not qualified applicants. You end up paying more for worse candidates. Connecting a purpose-built funnel builder to Recruitee closes both gaps at once: better candidate experience on the way in, and better ad optimisation signals on the way back.
Heyflow: The Funnel Builder Built for Recruitee Integration
Heyflow is a no-code funnel and form builder built specifically for performance marketing use cases, including social recruiting. It connects natively to Recruitee, meaning you do not need Zapier, Make, or any other middleware. Candidate data flows from your funnel into Recruitee in real time, with full field mapping and direct job posting assignment.
The native integration lets you map every funnel field to the corresponding Recruitee candidate property. Name, email, phone, availability, salary expectations, uploaded CV, qualifying answers — all of it arrives in Recruitee structured and ready for your recruiters to act on. No copy-pasting, no CSV imports, no delay.
Beyond the ATS connection, Heyflow gives recruiting teams features that no standard form builder offers: server-side tracking to Meta CAPI and TikTok Events API, phone number validation with OTP verification, partial submit capture for abandoned applications, per-screen drop-off analytics, and built-in A/B testing. These are the features that determine whether your recruiting campaigns generate qualified candidates or just form fills. You can try Heyflow free and build your first recruiting funnel in minutes.
How to Connect Heyflow With Tellent Recruitee: Step-by-Step Setup
What you need before you start
To set up the integration, you need two pieces of information from your Recruitee account: your company ID and a personal API token. Both are found in Recruitee under Settings, then Apps and plugins, then Personal API tokens. Your company ID is listed on that same page. Copy both before opening Heyflow.
Connecting your Recruitee account in Heyflow
Inside your Heyflow flow, open the Integrations panel and select Recruitee from the recruiting integrations category. Enter your company ID and personal API token to authenticate the connection. Once connected, Heyflow will pull your Recruitee account data so you can begin mapping fields and assigning job postings.
Mapping your funnel fields to Recruitee
Field mapping is where the integration delivers its real value. For each field in your funnel, you select the corresponding Recruitee candidate property. Standard fields like first name, last name, email address, and phone number map directly. For qualifying answers — availability, experience level, location preference, salary expectation — you map these to Recruitee custom fields so recruiters can filter candidates without re-asking the same questions.
The table below shows the most common field mappings for a social recruiting funnel:
Heyflow Funnel Field | Recruitee Candidate Field |
First name | First name |
Last name | Last name |
Email address | |
Phone number (validated) | Phone |
CV / resume file upload | Resume |
Years of experience (multiple choice) | Custom field: Experience |
Earliest start date | Custom field: Availability |
Salary expectation | Custom field: Salary range |
UTM source / campaign | Custom field: Ad source |
Job GUID (from multiple choice) | Job posting assignment |
Assigning candidates to specific Recruitee job postings
Every job posting in Recruitee has a unique Job ID (also called Job GUID). You use this ID to route candidates from your funnel directly into the correct Recruitee pipeline, rather than landing them in a general inbox.
To find the Job ID, open Jobs from the Recruitee sidebar and hover over the relevant job in the list. The ID appears to the right of the job title. Click to copy it. Alternatively, open the job itself and the ID is displayed next to the job name at the top of the page.
For funnels covering a single role, enter the Job GUID as a static value directly in the Recruitee integration settings and map it to the Job GUID field. For funnels covering multiple roles, add a Multiple Choice block to your funnel where each option represents a different job. Set the Job GUID for each option as the System Label in Heyflow, then map that field to Job GUID in the integration. When a candidate selects a role, their application routes automatically to the correct Recruitee job posting.
Passing UTM parameters to Recruitee
To track which ad campaign, ad set, or creative generated each candidate, add a hidden input field to your funnel for each UTM parameter you want to capture (utm_source, utm_medium, utm_campaign, etc.). Heyflow captures these automatically from the URL when a candidate lands on your funnel. Map each hidden field to a corresponding custom field in Recruitee. Your recruiters will see the ad source alongside every candidate record, enabling genuine source-of-hire reporting without any manual attribution work.
Features That Improve Candidate Quality Before They Reach Recruitee
Conditional logic for pre-qualification
Use conditional logic to ask knockout questions early in your funnel. If a candidate answers that they do not hold a required licence or certification, route them to a polite rejection screen rather than continuing to collect their details. Only qualified candidates complete the funnel and reach Recruitee. This keeps your ATS pipeline clean and saves recruiters from filtering out unsuitable applicants manually. The engagement features in Heyflow make it straightforward to build these branching paths without writing any code.
Phone number validation and OTP verification
Fake applicants and mistyped phone numbers are a persistent problem in social recruiting, particularly when running broad-audience campaigns on Meta. Heyflow's phone validation with OTP verification confirms that each candidate's phone number is real and reachable before their data is submitted to Recruitee. This single feature can significantly reduce the volume of uncontactable candidates in your pipeline and improve the ratio of qualified applicants your recruiters actually speak to.
Partial submit capture
When a candidate starts your funnel but abandons it before completing, Heyflow captures the data they entered up to that point. This means a candidate who filled in their name, email, and phone number but dropped off at the CV upload step is not lost entirely. Your team can follow up with warm outreach. Heyflow is the only funnel builder that offers partial submit capture natively, and for high-volume social recruiting campaigns, this can meaningfully increase the number of candidates entering your pipeline from the same ad spend.
Drop-off analytics and A/B testing
Heyflow's per-screen analytics show exactly where candidates abandon your funnel. If 40% of candidates drop off at the salary expectation question, you can reword it, reorder it, or test removing it entirely. Built-in analytics and optimisation tools let you run A/B tests across funnel variations and measure completion rates per screen, giving recruiting teams the same optimisation capability that performance marketers use for lead generation campaigns.
Closing the Ad Tracking Loop With Server-Side Signals
Pushing candidates to Recruitee is only half the integration. The other half is sending qualified-applicant conversion signals back to your ad platforms so the algorithm can find more candidates like your best applicants.
Heyflow sends conversion events server-side to Meta CAPI and TikTok Events API. This means that when a candidate completes your funnel and passes your qualification criteria, a conversion event fires directly from Heyflow's servers, not from a browser pixel. Server-side tracking is not blocked by ad blockers or iOS privacy restrictions, and it produces significantly higher Event Match Quality scores. Improving EMQ from pixel-only (3.5–5.0) to CAPI-enabled (7.5–9.0) trains Meta's algorithm to find candidates who actually complete applications, not just people who click your ad.
For agencies running recruiting campaigns across multiple clients, this tracking architecture is a genuine competitive advantage. You can demonstrate cost-per-qualified-candidate metrics that a Zapier-to-Recruitee setup simply cannot produce. The performance marketing capabilities in Heyflow are designed specifically for this kind of closed-loop attribution.
Heyflow for Social Recruiting Agencies
If you manage recruiting funnels for multiple employer clients, all of whom use Recruitee, Heyflow's agency features are worth understanding. You can connect to as many Recruitee accounts as needed, one per client, and manage all your funnels from a single Heyflow workspace. The white-label Agency Portal lets you present flows under your client's branding without exposing Heyflow as the underlying tool.
Agencies like Social Natives, Medwing, and New Work SE already use Heyflow to build interactive recruiting funnels that pre-screen candidates and deliver only qualified applicants to their clients' ATS pipelines. The combination of conditional pre-qualification, phone validation, and native Recruitee integration means recruiters spend their time on candidates who are genuinely interested and contactable, not on filtering out noise. For a deeper look at how agencies use Heyflow to scale candidate acquisition, the agency lead generation guide covers the full workflow.
If you are ready to replace static application forms with a funnel that feeds directly into Recruitee, get started with Heyflow and connect your first flow to Recruitee in under 15 minutes.
FAQ
Do I need Zapier or any middleware to connect Heyflow with Recruitee?
No. Heyflow has a native, direct integration with Tellent Recruitee that requires no Zapier, Make, or any other middleware. You authenticate the connection using your Recruitee company ID and a personal API token, then map your funnel fields to Recruitee candidate properties directly inside Heyflow. Candidate data transfers in real time without any polling delays or per-task automation costs.
Can I assign candidates from my funnel to a specific Recruitee job posting automatically?
Yes. Each Recruitee job posting has a unique Job ID (also called Job GUID). You use this ID to route candidates from your funnel directly into the correct Recruitee pipeline, rather than landing them in a general inbox. For a single-role funnel, you enter the Job GUID as a static value in the integration settings. For multi-role funnels, you add a Multiple Choice block where each option carries the relevant Job GUID as a System Label, and candidates are routed to the correct Recruitee pipeline based on their selection.
Can I send CV or resume file uploads from my Heyflow funnel to Recruitee?
Yes. Heyflow supports file upload blocks that allow candidates to attach their CV or resume directly in the funnel. You map the file upload field to the Resume property in the Recruitee integration, and the file arrives in the candidate record in Recruitee alongside all other submitted data.
How do I track which Meta or LinkedIn ad campaign generated each candidate in Recruitee?
Add hidden input fields to your Heyflow funnel for each UTM parameter you want to capture (utm_source, utm_medium, utm_campaign, etc.). Heyflow automatically reads these values from the landing URL when a candidate arrives from an ad. Map each hidden field to a custom field in Recruitee, and every candidate record will show the ad source that generated them, enabling source-of-hire reporting without any manual work.
Is candidate data transferred between Heyflow and Recruitee in a GDPR-compliant way?
Heyflow is SOC 2 certified and HIPAA-compliant on all plans, and the native Recruitee integration transfers candidate data directly between the two platforms without routing it through a third-party middleware processor. For teams operating in the EU or DACH region, this direct data path simplifies your data processing agreements and reduces the number of vendors handling candidate personal data.
What happens if a candidate starts my funnel but does not complete it?
Heyflow captures partial submissions, meaning data entered by a candidate before they abandon the funnel is saved even if they never reach the final submit screen. This lets your team follow up with candidates who showed intent but dropped off, for example at the CV upload step. Partial submit data can also be pushed to Recruitee or to a separate notification workflow so no interested applicant is lost entirely.


