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.
New submission on your Submit an event form
Create a Page post on Facebook with the event details
One-directional. A submission triggers the action — nothing is written back into your form.
A community events list only works if it is current. This flow publishes each submitted event to your Page as soon as the organiser sends the form, with the name, date and location laid out the same way every time.
Councils, libraries, church halls and neighbourhood groups tend to use it: whoever runs the Page is rarely the person who knows what is happening next Tuesday. Organisers fill in the form, followers see the announcement, and the comments underneath do the RSVP work.
Setting it up
- 1
Publish the Community Event Proposal Form so organisers have somewhere to send the name, date and location of what they are running.
- 2
Create the Zap with the formformform New Submission trigger and select the event form.
- 3
Add a Formatter by Zapier step that turns Proposed Event Date into the way you write dates on the Page, such as Saturday 5 September.
- 4
Add Facebook Pages, choose Create Page Post, and select the Page your followers actually follow rather than a secondary one.
- 5
Lay the message out as Event Name on the first line, the formatted date and Proposed Venue or Location underneath, then Event Description and Purpose.
- 6
Close the message with a fixed sentence inviting followers to reply in the comments, since the post cannot send answers back to the form.
- 7
Add a filter on Proposed Event Date to drop anything submitted for a date that has already passed.
- 8
Run a test submission, read the post as a follower would, then turn the Zap on.
What maps where
Using the Community Event Proposal 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 |
|---|---|
| Event Name | First line of the post |
| Proposed Event Date | Date line, after a Formatter step tidies it |
| Proposed Venue or Location | Location line under the date |
| Event Description and Purpose | Body of the post |
| Organization or Group (if applicable) | Hosted-by credit at the end of the message |
Variations worth knowing
Add Delay Until from Zapier and feed it Proposed Event Date shifted back a few days, then a second Create Page Post step. The first announcement goes out on submission and the reminder appears while people are planning their week.
If you run more than one Page, add Zapier Paths keyed on Proposed Venue or Location so town-centre events publish to one and village-hall events to another. Each path holds its own Create Page Post step and its own message layout.
If something isn't arriving
That is the raw value from the form. Insert Formatter by Zapier, choose Date/Time, and set the output format you want, then map the Formatter output into the message rather than the original field.
Organisers resubmit to correct a typo. Add a Storage by Zapier lookup keyed on Event Name so a repeat submission stops before the action step, and delete the older post on Facebook yourself — the form cannot retract one it has already sent.
Frequently asked questions
Can followers RSVP through the Facebook post?
Only in the comments. The post is the end of the line for this connection: it carries information out to your Page and nothing travels back into the form. If you need names, link to a separate registration form in the message.
Can this create a Facebook event instead of a post?
No. The actions this connection uses publish a Page post or a Page photo. Create the Facebook event by hand if you need the calendar features, then paste its link into the Zap message so every announcement points at it.
What stops someone posting nonsense to our Page?
The filter steps. Anything the Zap will not let through never reaches Facebook, so gate on a field only trusted organisers can answer correctly, or share the form link with known groups instead of publishing it on your site.
Related automations
- 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.
- 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