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