About

Objective Build an AI assistant in n8n that collects leads from Facebook Marketplace, qualifies them in Messenger, books property viewings using Google Calendar, and sends confirmations via Gmail. The agent must run in my n8n account at handoff. Scope 1) Facebook Marketplace Connect to my Facebook account and ingest active listings with title, price, availability date, address or location, description, utilities, pet policy, and surface metadata needed for replies. Keep listings current with periodic sync and a manual refresh control. 2) Messenger Lead Handling Listen to incoming messages per listing. Classify intent and qualify leads. Collect phone and email when booking. Respect Messenger’s 24-hour messaging window and handover to human when needed. 3) Scheduling and Calendar Read availability from Google Calendar in my timezone (PST). Offer viewing slots in 30-minute blocks and stack back-to-back where allowed. Place a short-hold “tentative” event when a slot is offered, confirm on acceptance, and release on timeout or decline. Prevent double-booking with conflict checks and etags. Include configurable buffers per property. 4) Email Confirmation and Thread Sync Send a Gmail confirmation email with date, time, address, parking or access notes. Post a matching confirmation message in Messenger that mirrors the calendar source of truth. On any reschedule or cancellation, update the calendar first, then update both channels with a change summary. 5) Reschedule and Exception Handling Handle reschedule requests with the next best available options. Escalate to human after a failed alternative. Provide simple admin commands to pause a conversation, force refresh a listing, or mark “needs human.” Technical Requirements Entirely built in n8n. No external workflow engines. Idempotent design for all writes: calendar events, messages, emails. State store per conversation with stage, listing ID, tentative hold ID, last message hash, and timestamps. Robust retries with exponential backoff and jitter for API errors and Gmail quota limits. Clear timezone handling. All messages include the explicit date and time with timezone. Minimal PII storage, encryption at rest, and a “delete my data” command. Deliverables n8n workflows and configuration running in my account with: Facebook listing ingestion and refresh Messenger listener, NLU classification, and lead qualification Google Calendar free/busy checks, slot holds, confirmations, and reschedules Gmail confirmations with ICS and cross-channel sync updates Setup documentation: OAuth steps for Facebook, Google Calendar, and Gmail Environment variables and secrets Property-level settings (buffers, viewing durations, default messages) Recovery procedures for failed nodes and webhook retries One live end-to-end test from first message to confirmed showing, executed in my account Must-Have Acceptance Tests (pass/fail) Simultaneous booking conflict Two different prospects attempt to book the same time within five seconds. Expected: Only one is confirmed. The second receives the next best option based on current free/busy. No duplicate events are created. Messenger 24-hour rule A prospect goes silent more than 24 hours after the last interaction. Expected: The agent does not send follow-ups in Messenger. If contact info is available, it uses email instead or waits for re-engagement. Listing removed mid-conversation A listing is deactivated or deleted while a conversation is ongoing. Expected: The agent stops offering that unit, informs the user that it is no longer available, and offers alternative active listings. Cross-channel reschedule A prospect reschedules via email reply. Expected: The calendar event updates. Messenger thread posts a concise change summary reflecting the new date and time. No conflicting events remain. Gmail quota or transient send error A confirmation send triggers a quota or transient error. Expected: The workflow backs off with jitter, retries within reasonable limits, and sends a single confirmation when permitted. No duplicate emails are sent. Ideal Candidate Proven n8n builds in production with API orchestration. Experience with Facebook Messenger integrations, Google Calendar, and Gmail APIs. Familiarity with conversational state machines, slot-filling, and lead qualification. Handoff and Success Criteria The solution runs in my n8n account using my credentials and environment variables. All acceptance tests above pass in a live session. I receive a concise “runbook” for common operations: add listing, pause bot, force refresh, reschedule, cancel, escalate to human, rotate API keys. Clear instructions for updating message templates and property-level buffers without editing nodes.