AI Form Builder for HR Teams: From Job Posting to Offer

Most HR teams have a stack the size of a sales team. Greenhouse or Workable for the ATS, Typeform or Google Forms for application intake, Notion or Confluence for documentation, Slack for hiring updates, and a Google Sheet tracking who is at what stage. The data lives in five places, syncs through Zaps that break every other Tuesday, and the recruiter spends an hour every Monday reconciling.

The forms are usually the weakest part — bolted on, off-brand, asking the wrong questions, routing applications into an inbox someone is supposed to check.

This is the practical setup for an HR team that wants to fix the form layer without buying a new ATS: an AI-native builder for application intake, routing to Slack and Notion handled by the AI you already use, conditional logic for role-specific fields, and a real GDPR posture for candidate data. With Brieform you build and read these forms from inside Claude, ChatGPT, or any MCP client — describe the form, get a live URL, read applications in the same chat.

The hidden cost of HR form sprawl

The pattern is consistent across teams of 1 to 15: one ad-hoc form per role copy-pasted from the last one, forms scattered across three tools, applications landing in an inbox or the ATS but not both, and candidate data split across CVs in Drive, structured fields somewhere, and free-text notes in Notion. The symptom teams notice first is a candidate going silent because the application was routed somewhere no one was watching. The fix isn't a new ATS — it's fixing the form layer so the data lands in one searchable place from the start.

The five forms every HR team needs

1. Job application form (per role) — contact info, role-specific screening questions, work authorization, salary expectation, notice period, and links (resume in Drive, LinkedIn, portfolio, GitHub). One per role, but built in a couple of minutes each so the friction is gone.

2. New-hire onboarding form — payroll details, emergency contact, banking for direct deposit, equipment preferences, dietary restrictions, t-shirt size.

3. Internal feedback form — quarterly pulse survey, manager feedback, exit interview, with a native GDPR consent field if it's named rather than anonymous.

4. Reference check form — standardized questions for a candidate's references about working style, strengths, and growth areas.

5. Offer acceptance form — confirms start date and final details, closing the loop between offer and onboarding.

Five forms cover the entire candidate-to-employee journey.

How to build a job application form by describing it

The build takes about 90 seconds. Type the prompt straight into your AI or Brieform's builder:

Job application form for a senior product designer at a 30-person SaaS startup. Fields: full name, email, phone (optional), location and willingness to relocate, current employer and role, link to portfolio (required URL), LinkedIn URL, Dribbble/Behance URL (optional), years of experience, design tools (multi-select: Figma, Sketch, Adobe XD, Framer, other), three example projects with a short description each, why this role and why now, salary expectation range, work authorization (yes / requires sponsorship / no), notice period, how did you hear about us, link to your resume (Drive/Dropbox URL), GDPR consent checkbox.

The form is ready in about 12 seconds with the right field types — multi-select for tools, select for work authorization, a native GDPR consent field at the end linking to your privacy policy.

A note on resumes: Brieform supports 13 field types, and file upload isn't one of them. Collect resumes and portfolios as URL fields — a link to the candidate's Drive, Dropbox, LinkedIn, or personal site. In practice this is cleaner: links don't bounce on size limits and stay current.

Then add conditional logic in chat — Brieform supports eight operators (equals, not equals, contains, not contains, greater than, less than, is empty, is not empty):

"Hide the relocation question if location equals our target city. Show 'are you currently under a visa' only if work authorization is 'requires sponsorship.'"

Apply your logo and brand color via the theme presets, set a custom thank-you message ("we review weekly, you'll hear within 7 days"), and publish to a public URL to embed on the careers page.

Routing applications to Slack and Notion — through your AI

Brieform doesn't ship native Slack, Notion, or webhook integrations. It's conversation-first, so the AI you've connected does the routing using its own Slack and Notion connectors plus Brieform's get_responses tool. You describe the rule once:

"For each new Senior Designer application, post a one-line summary (name, role, portfolio link) to #hiring-design in Slack, and create a row in my Notion Candidates database with Stage = New, plus all the fields and links."

Route different roles to different channels by adjusting the sentence. The Notion database becomes a lightweight ATS — filtered views give you "applications this week," "by role," and "needs follow-up." For teams on Greenhouse, Workable, Lever, or Ashby, export responses to CSV (available on every plan, including Free) for import, or have your AI push them in if it has a connector for your ATS. Set the routing instruction to run on a schedule so it happens without you asking.

GDPR-friendly intake

Candidate data is sensitive personal data, and the HR form layer is one of the most-audited surfaces in any compliance review. Brieform's baseline:

Consent. A native GDPR consent field — explicit, opt-in, not pre-checked, with a link to your privacy policy — stored alongside the application.

Data residency. All data is hosted in the EU (Frankfurt), encrypted in transit and at rest, with no cross-border transfer.

Right to erasure. A candidate can request deletion at any time. You own all your data, can delete a form and its responses, and can export everything to CSV first if you need a record. (Note: Brieform itself never deletes your responses for exceeding a plan cap — they queue.)

The practical posture: every application form carries the consent field, candidate data stays in the EU, and you have a documented process for deletion requests. That covers most GDPR reviews for a small HR team.

From application to offer in one workflow

1. Candidate applies via a Brieform job application form on the careers page.
2. Your AI posts a one-line summary to #hiring instantly.
3. Your AI creates a structured record in the Notion Candidates database.
4. Recruiter screens in Notion using filtered views.
5. Interview rounds tracked as Notion sub-pages or properties.
6. Reference check sent via a second Brieform form.
7. Offer letter sent through your signing tool (Docusign, PandaDoc, or a Brieform acceptance form).
8. Onboarding form on the start date collects payroll and equipment details, into the same Notion database — now an employee directory.

No Zapier subscription, no $300-per-seat ATS bill, no reconciliation Mondays.

FAQ

Is Brieform GDPR-friendly for HR data?

Yes. Data is hosted in the EU (Frankfurt), encrypted in transit and at rest, with a native opt-in GDPR consent field and deletion on request. You own and can export all responses on any plan.

Can applicants upload a resume or CV?

Not as a file — Brieform's 13 field types don't include file upload. Collect a resume or portfolio as a URL field (a link to Drive, Dropbox, LinkedIn, or a personal site). It's more reliable than uploads and the link stays current.

Can I send conditional follow-ups?

Within the form, conditional logic shows or hides fields based on earlier answers (eight operators). For post-submission emails to different candidate segments, have your connected AI read responses via get_responses and send through its own email connector.

Does Brieform replace an ATS?

For small teams (1–5 hires a quarter), Brieform plus a Notion candidate database often replaces an ATS at a fraction of the cost. For high-volume hiring, Brieform handles the form layer and you move data to Greenhouse/Workable/Lever/Ashby via CSV export or your AI's connector. The form is one piece of the stack, not the whole stack.