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.
New submission on your Submit a post form
Create a Page post on Facebook with the title and link
One-directional. A submission triggers the action — nothing is written back into your form.
Editorial and comms teams already write the headline twice: once for the article, once for social. This flow removes the second pass by taking the approved headline, summary and link out of the submission form and publishing them to your Page as a link post.
It fits teams where several people ship content and one person owns the Page — an in-house comms desk, a membership body, a small publisher. The embargo answer and the distribution date on the form give you the two controls that matter: whether it posts, and when.
Setting it up
- 1
Publish the Press Release Request Form as the internal log for anything going out — articles, releases, product notes.
- 2
Trigger the Zap on formformform New Submission and select that form.
- 3
Add a filter that stops the Zap when Embargo? is Yes, so nothing under embargo reaches the Page by accident.
- 4
Add Delay Until from Zapier and point it at Target Distribution Date when the post should wait for publication day.
- 5
Add Facebook Pages, choose Create Page Post, and select the Page you announce on.
- 6
Build the message with Headline (Proposed) on the first line, Key Message / Summary underneath, and Supporting Assets URL (images, logos, video) on a line of its own so Facebook can build the preview card.
- 7
Drop Announcement Type into a hashtag at the end, or hold it back to route different announcements to different Pages later.
- 8
Test with a live URL, confirm the preview card renders, then turn the Zap on.
What maps where
Using the Press Release Request 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 |
|---|---|
| Headline (Proposed) | First line of the post |
| Key Message / Summary | Body of the post |
| Supporting Assets URL (images, logos, video) | Link on its own line, which Facebook expands into a preview card |
| Approved Quote from Primary Source | Optional pull quote under the summary |
| Announcement Type | Hashtag at the end, or the routing key for Paths |
| Embargo? | Zapier filter condition — the Zap stops on Yes |
Variations worth knowing
Feed Target Distribution Date into Delay Until so submissions logged days early sit in Zapier and post themselves on the right morning. The team keeps working ahead, and the Page still looks like it is keeping pace.
Add Paths keyed on Announcement Type: product news to the main Page, hiring news to a careers Page, event news to a third. Each path carries its own message layout, so the tone matches the audience.
If something isn't arriving
Facebook builds the card from a URL it can reach, sitting on its own line. Check the field holds a full address including https, that the page is not behind a login, and that no trailing punctuation has been added in the message template.
The filter has to sit above the Facebook step, not below it, and it must read the Embargo? answer exactly as the form stores it. For anything that must wait, add Embargo Date & Time (if applicable) to a Delay Until step.
Frequently asked questions
Can I schedule the Facebook post for a specific time?
Use Delay Until in the Zap and map Target Distribution Date into it. The submission arrives whenever the writer logs it, and the Page post fires on the date you set. Facebook's own scheduler stays separate from this flow.
Will the post pick up the article's image?
It uses whatever the linked page exposes to Facebook. If the article has a preview image set, the card shows it. Otherwise switch the action to Create Page Photo and map a hosted image link into the photo field instead.
Can one submission post to two Pages?
Yes. Add a second Facebook Pages action to the same Zap, choose the other Page, and map the same fields into it. Each step publishes on its own, so a failure on one Page does not stop the other.
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.
- Broadcast job openings to your followers
New roles submitted by hiring managers post to your Page with the title, location and where to apply.
- 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.
- 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