Event questions, access problems, praise, and recap posts can appear before, during, and after the official schedule. A dated source list helps organisers see which public questions need an answer and which content may support the event recap.
This Facebook event promotion workflow tracks public discussion without claiming access to private attendee activity.
SocialListeningAPI lets Claude or ChatGPT search public Facebook posts through the MCP. It returns normalized records with source URLs. External tools handle scheduling, storage, classification, and delivery.
Step 1: Build the Facebook event promotion query list
Use the terms attendees and local readers may write:
- Full event name and abbreviation
- Venue and city
- Headline speaker, performer, or team
- Campaign phrase or hashtag
event name ticketsevent name parking,access,cancelled, orrecap
Record the event dates and keep each query separate.
Step 2: Search public event posts through the MCP
Create a SocialListeningAPI account, claim the 100 free credits, and connect the MCP to Claude or ChatGPT through OAuth.
Ask for a dated, sourced result:
Search public Facebook posts for each event phrase. Return the matched phrase, published date,
author, post text, available reactions, comments count, shares, and source URL. Group questions,
access or logistics issues, praise, complaints, and recap content. Do not infer attendance and do
not draft a reply.Each successful Facebook search costs 7 credits. Run a manual search before any recurring schedule.
Step 3: Build the external event log
Store source URL, query, published date, first-seen time, category, and review owner in an external database. An external agent can run the fixed searches at approved times and skip seen URLs.
The live endpoint searches public posts only. It does not search Facebook Event objects, private attendee activity, closed groups, or comment text. It returns one page with no next cursor.
Step 4: Route questions and prepare the recap
Send current logistics and access questions to the event owner. Verify cancellations, schedule changes, or safety claims through an official source before responding. Keep public replies under human control.
After the event, group useful public recaps and media into a source pack. Do not reuse attendee or creator content without checking permission and attribution.
Conclusion
The finished brief should show what people asked, which issues were verified, and which public posts may support follow-up. It is a directional view of public discussion, not a measure of total event attendance or satisfaction.
Continue with Build an Event-Based Account List.
