Broadcast job openings to your followers
New roles submitted by hiring managers post to your Page with the title, location and where to apply.
New submission on your Post a job form
Create a Page post on Facebook with the role and apply link
One-directional. A submission triggers the action — nothing is written back into your form.
Hiring pages get stale because posting a role is a separate chore from opening it. When the requisition form is the thing that starts the process, the Page post can come out of the same submission — title, location, hours and where to apply.
Recruiters and office managers at places without an applicant tracking system use this most; the requisition also carries pay bands, cost centres and internal justification, so the mapping is deliberately narrow. Only the fields you pick reach Facebook, and everything else stays in your responses.
Setting it up
- 1
Publish the Job Requisition Form and treat it as the single place a new role is opened.
- 2
Add a URL field for the application link, or decide that every post points at the same careers page and type that address into the Zap by hand.
- 3
Trigger the Zap on formformform New Submission and select the requisition form.
- 4
Add a filter on Requisition Type so only roles meant for the public — new headcount rather than a confidential backfill — continue.
- 5
Add Facebook Pages, choose Create Page Post, and pick the Page your local audience follows.
- 6
Write the message with Position Title first, Work Location and Employment Type on the next line, and a trimmed Key Responsibilities as the body.
- 7
Map fields one at a time and leave Role Justification, Budget Cost Center / GL Code and Reports To (Name & Title) out — nothing internal should reach the Page.
- 8
Finish with the application link, run a test, and turn the Zap on once the post reads like an advert rather than a form dump.
What maps where
Using the Job Requisition Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Facebook Pages |
|---|---|
| Position Title | Headline of the post |
| Work Location | Location line under the title |
| Employment Type | Same line as the location, after a separator |
| Key Responsibilities | Body of the post, trimmed by Formatter |
| Salary / Compensation Range | Pay line, when you publish ranges |
| Requisition Type | Zapier filter condition — only public roles continue |
Variations worth knowing
Add Paths on Hiring Urgency: anything marked urgent posts immediately, everything else collects in Digest by Zapier for a Friday round-up. The Page gets one hiring post a week plus the roles that genuinely cannot wait.
Map Target Start Date into the message so applicants can judge the timing themselves. It also gives you a field to filter on when you want to stop advertising roles whose start date has already gone by.
If something isn't arriving
Zapier inserts any field you place in the message box, including a full submission summary. Rebuild the message field by field, then re-read the test post on a draft Page before this Zap goes live.
Key Responsibilities is a long-answer field. Run it through Formatter by Zapier to take the first couple of hundred characters, or add a short summary field to the requisition form and post that instead.
Frequently asked questions
Can candidates apply directly from the Facebook post?
No. The post carries your application link and people follow it; nothing comes back down the connection into the form. Track applications wherever that link points, whether that is another formformform form or your careers site.
Does this create a listing in a Facebook jobs section?
No. This connection publishes an ordinary Page post or Page photo. Anything that lives in a dedicated jobs area on Facebook is set up there directly, while the Zap only ever writes to your Page feed.
What happens when the role is filled?
Nothing automatic. The post stays up until someone edits or deletes it on Facebook, because the flow only travels outward. Some teams add a comment saying applications have closed rather than removing the post entirely.
Related automations
- Announce new events the moment they are submitted
Event submissions become a Page post within seconds, so followers see the date and venue without anyone drafting it.
- Post new listings with a photo
New stallholder and product listings post to your Page as a photo, with the caption written from the answers on the form.
- Publish approved testimonials to your Page
Every testimonial that passes your consent check posts to your Page as a quote, credited the way the customer agreed.
- Share every new content drop with followers
Announcements logged in your form publish to the Page with the headline, a short summary and the link.
- Turn member shout-outs into Page posts
Each nomination becomes a short recognition post naming the volunteer, the programme they serve and what they did.
- Alert the on-call team when a support ticket arrives
Each new ticket posts to #support with its subject and priority, and @here fires only when the priority justifies interrupting a shift.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free