Track Demo Bookings with Google Calendar to Meta...
When a new demo booking appears in Google Calendar, this workflow automatically sends the event details to Meta's Conversion API to track...
What it does
You automatically track every "Schedule a demo" event from your Google Calendar as an ad conversion in Meta. This workflow filters new calendar events and instantly sends their details to the Meta Conversion API so you can measure campaign performance accurately.
Step by step
- Configure the Google Calendar trigger to watch for new events in a specific calendar ID.
- Add a filter node that checks if the event title contains the string 'Schedule a demo'.
- Set up an HTTP Request node targeting the Meta Conversion API endpoint with method POST.
Where the LLM does the work
- Generate the exact JSON payload structure required by the Meta Conversion API for conversion tracking.
- Determine how to map Google Calendar event fields like start time and attendee count to Meta's custom data parameters.
- Draft error handling logic that parses non-JSON responses from the Meta API gracefully.
Watch out for
Tools that fit
The agent brief
You are helping me build the following AI agent workflow. ## Goal Track Demo Bookings with Google Calendar to Meta...: When a new demo booking appears in Google Calendar, this workflow automatically sends the event details to Meta's Conversion API to track... ## Specification - What it does: You automatically track every "Schedule a demo" event from your Google Calendar as an ad conversion in Meta. This workflow filters new calendar events and instantly sends their details to the Meta Conversion API so you can measure campaign performance accurately. - Trigger: Triggered by an event (Event · on new calendar event) - Autonomy: Fully hands-off - Expected setup effort: about an afternoon - Tools/services involved: - Google Calendar: Trigger and source of booking events - Meta Conversion API: Sending formatted conversion data to Meta Ads - HTTP Request: Executing the API call to Meta - Crypto: Security or data processing within the workflow ## Known pitfalls, handle each one explicitly in your implementation 1. Meta requires a valid Access Token for every request so you must store it securely in environment variables rather than hardcoding it. 2. The Crypto node is unnecessary for standard OAuth flows but might be needed if you are signing specific headers, so verify the exact authentication requirement first. 3. Event titles often have slight variations like 'Schedule a Demo' vs 'schedule a demo', so use case-insensitive matching in your filter to avoid missed conversions. ## Reference implementation https://n8n.io/workflows/6331 (workflow template) Fetch and inspect this before building. If it matches my stack, adapt it; if not, rebuild the pattern with my tools. ## Process requirements 1. Before building: ask me which of the listed tools I actually use and what my platform is (n8n / Make / code / other). Do not assume. 2. Adapt the pattern to my answers; do not force the reference stack. 3. Address every pitfall above; tell me how you handled each. 4. Provide a test plan I can run before letting this touch real data. 5. Ask before any step that sends messages, modifies data, or spends money. Source: https://usecasesforagents.com/use-case/track-demo-bookings-with-google-calendar-to-meta/ via usecasesforagents.com
Frequently asked questions
Can I use a different Calendar than Google Calendar?
Yes. Google Calendar is only the example calendar in this recipe. The same flow works with Cal.com, Calendly and Eventbrite. Swap the calendar connection and keep the rest of the setup as written.
Want this running in your business?
Who it's for
Built for founders and execs who need marketing handled without hiring for it.
Sales teams can plug this into their own CRM and call cadence just as easily.