Connect Your Funnel Builder With softgarden Using Heyflow

Why Sending Paid Traffic to Your softgarden Career Page Is Costing You Applicants

softgarden is built to manage applicants, not convert them. Its native career page forms are designed for candidates who arrive motivated from job boards, already committed to applying. Paid social traffic, whether from Meta, LinkedIn, or TikTok, is fundamentally different. These are passive candidates who need a fast, engaging, mobile-first experience to convert. When they click your ad and land on a standard ATS form, most leave before completing it.

The fix is not replacing softgarden. It is adding a conversion layer in front of it. A purpose-built funnel builder handles the candidate acquisition side, pre-qualifies applicants using conditional logic, validates contact data, and then passes structured, qualified candidate records directly into softgarden, so your recruiters only see submissions worth reviewing.

Heyflow offers a native softgarden integration, meaning no Zapier, no Make, no middleware. Applicant data flows from your funnel into softgarden in real time, with full control over field mapping. This is the architecture that social recruiting agencies and in-house HR marketing teams are using to reduce cost-per-applicant and eliminate recruiter time wasted on unqualified submissions.

What the Native Heyflow and softgarden Integration Actually Does

Heyflow's softgarden integration lives inside the platform's Connect tab, under the Recruiting category alongside Personio and Recruitee. Once connected, every completed funnel submission triggers an automatic candidate record in softgarden, mapped to the fields you specify. There is no polling delay, no third-party processor sitting between the two systems, and no fragile Zap that breaks when a field name changes.

The integration supports full field mapping, meaning you control exactly which Heyflow input maps to which softgarden property. Standard fields like first name, last name, email, and phone number map directly. But you can also pass conditional logic outputs, such as a candidate's selected job preference or availability, qualification answers, file uploads including CVs, and UTM parameters captured via hidden input fields. This gives recruiters structured, queryable data rather than a pile of raw form responses.

If something goes wrong with the integration, Heyflow sends an automatic error notification that includes the flow ID, response ID, and a description of the error returned by softgarden. You are not left debugging in the dark.

To explore the full setup process, the Heyflow softgarden integration guide walks through account connection, channel and job selection, and field mapping step by step.

How to Set Up the Integration: The Core Steps

Step 1: Connect your softgarden account. Inside your Heyflow flow, open the Connect tab and select softgarden from the Recruiting integrations. You will authenticate with your softgarden credentials to link the two accounts.

Step 2: Select the channel and job. Once connected, choose the specific softgarden job channel and job posting you want incoming applicants to be assigned to. This means you can run multiple Heyflow funnels for different roles or locations and route each one to the correct softgarden pipeline.

Step 3: Map your data fields. Map each Heyflow input field to the corresponding softgarden applicant property. Required fields in softgarden need a corresponding input in your funnel. Custom qualification answers, file uploads, and UTM parameters can all be mapped here.

Step 4: Set up UTM parameter tracking. If you are running paid campaigns and want to pass source data into softgarden alongside each applicant, add hidden input fields to your flow to capture UTM parameters. These fields then map to softgarden properties in the response handler, so every applicant record includes the campaign, ad set, and creative that generated it.

Step 5: Test before going live. Submit a test application through your funnel and confirm the candidate record appears in softgarden with all mapped fields populated correctly. Check that file uploads transfer cleanly and that UTM values are captured.

What Data You Can Pass From Heyflow Into softgarden

Pre-Qualifying Candidates Before They Reach softgarden

One of the most overlooked advantages of using a funnel builder in front of your ATS is the ability to filter applicants before they enter softgarden at all. Without pre-qualification, every submission, qualified or not, lands in your ATS and demands recruiter attention. With conditional logic in Heyflow, you can route candidates based on their answers.

A candidate who does not meet a minimum requirement, say, a required certification or a specific work permit status, can be shown a polite rejection screen and never submitted to softgarden. A candidate who qualifies for a fast-track role can be routed to a different softgarden job channel. This is not gatekeeping for its own sake. It is the difference between a recruiter opening softgarden to find 200 unfiltered applications and finding 60 pre-screened, structured records.

Phone validation adds another layer. Heyflow supports carrier-level phone number validation, which checks that submitted numbers are real and active before the form completes. This eliminates ghost applications with fake contact data, a persistent problem in paid social recruiting where ad incentives can attract low-intent submissions.

Partial submit capture works in the opposite direction. If a candidate fills in their name and phone number but drops off before completing the full application, Heyflow can capture that partial data. A recruiter can proactively reach out to those candidates, which is particularly valuable in competitive talent markets like healthcare and IT where every qualified lead matters.

Closing the Loop: Ad Campaign Optimisation With Server-Side Tracking

The Heyflow and softgarden integration solves the data transfer problem. But there is a second problem that most teams ignore: the ad platform has no idea which clicks turned into qualified applicants. Without that signal, Meta or LinkedIn optimises for whoever clicks the ad, not whoever completes a qualified application and enters softgarden.

Heyflow sends conversion events server-side to Meta via the Conversions API, to TikTok via the Events API, and supports Google Ads and LinkedIn tracking. When a candidate completes your funnel and their data flows into softgarden, that completion event fires back to the ad platform server-side. The algorithm then learns to find more people who behave like your completed applicants, not just your ad clickers. This is the same performance loop that powers high-converting lead gen campaigns, now applied to recruitment.

For performance marketers managing recruiting campaigns, this is the mechanism that reduces cost-per-qualified-applicant over time. The funnel improves conversion. The server-side signal improves targeting. Both compound. To understand how Heyflow's integration and automation capabilities connect your funnel data to ad platforms and downstream tools, the features page covers the full picture.

How Social Recruiting Agencies Use Heyflow With softgarden

The typical agency setup involves building a dedicated Heyflow funnel for each client role or campaign, connecting it to the client's softgarden instance, and running paid traffic to the funnel URL. The client's recruiters see only what enters softgarden, which means the agency's conversion layer is invisible to them but fully measurable on the agency side.

For blue-collar roles in logistics or construction, the funnel is typically three screens: location or region preference, shift availability, and contact details. The entire application takes under 90 seconds on mobile. For professional or technical roles, additional screens handle qualification checks before the contact capture. In both cases, conditional logic determines which softgarden job channel receives the submission.

Agencies managing multiple clients benefit from Heyflow's ability to duplicate flows and swap out the softgarden connection for each client's account. The Heyflow agency solution supports multi-client management with a shared workspace, making it practical to run this setup at scale without rebuilding from scratch for each engagement.

For teams that want to go further with funnel design, the funnel design guide covers the structural and visual decisions that affect application completion rates across different candidate audiences.

Integration Method Comparison

The native integration is the right choice for the vast majority of teams. It is faster to set up, cheaper to run, more reliable when field mappings change, and simpler from a GDPR standpoint because no additional data processor sits between Heyflow and softgarden.

FAQ

Does Heyflow have a native integration with softgarden, or do I need Zapier?

Heyflow has a native softgarden integration built directly into the platform's Connect tab, under the Recruiting category. No Zapier, Make, or middleware is required. Candidate data flows from your funnel into softgarden in real time, with field mapping configured inside Heyflow's interface.

Can I pass UTM parameters from my paid campaigns into softgarden alongside each applicant?

Yes. You add hidden input fields to your Heyflow flow to capture UTM parameters from the URL, then map those fields to corresponding properties in the softgarden response handler. Every applicant record in softgarden will include the campaign source data, without candidates ever seeing those fields.

Can candidates upload their CV through a Heyflow funnel and have it appear in softgarden?

Yes. Heyflow supports file upload inputs, including CVs and other documents, and these can be mapped to the application documents field in softgarden. File uploads up to 2 GB are supported within the funnel.

What happens if a candidate starts my Heyflow funnel but does not finish it?

Heyflow's partial submit feature can capture data that candidates enter before abandoning the flow. This data does not automatically push to softgarden as a full application, but it is available in Heyflow's response data, giving you the option to follow up with candidates who dropped off before completing.

Is transferring applicant data from Heyflow to softgarden GDPR-compliant?

Heyflow is fully GDPR-compliant, with all data hosted and processed in Europe. The native integration does not introduce an additional third-party data processor, which simplifies your data processing chain compared to middleware solutions like Zapier. softgarden is also GDPR-compliant and ISO 27001 certified, with data centres in Germany. You should still ensure your funnel includes appropriate consent language and that your privacy policy covers data transfer to your ATS.

Which Heyflow plan includes the softgarden integration?

The softgarden integration is available on Heyflow's paid plans. You can start building flows with Heyflow and check current plan details on the pricing page to confirm which tier includes native recruiting integrations for your team's requirements.