Instructions

Setup state. Not yet configured for this org. Load the Setup sub-page and walk the user through wiring the event-radar trigger (event-platform WEBHOOK, SCHEDULE + Apify scrape for public attendee lists, or the CRM's attendance workflow) with the right monitored event sources and follow-up sequence before running this play. (After setup is performed, rewrite this paragraph via swan-update-skill to describe the current state — trigger source(s) chosen, monitored events by class (owned / exhibited / industry / competitor), ICP filter, sequence wired, success metric, and last-refreshed date — so future runs see the current configuration without re-checking.)

When this fires

Most commonly WEBHOOK from an event platform (Goldcast, Hopin, Splash, Bizzabo, or a manually-uploaded attendee list), SCHEDULE + Apify (for public attendee lists of competitor / industry events that the user wants to scrape post-event), the CRM's workflow trigger (if attendance is stored in CRM — discover via swan-get-available-triggers), or WEBSITE_VISIT as a proxy for post-event landing-page visits.

The 48-72 hour window after an event is the highest-converting time to reach out.

Step 1 — Classify the event type

The play differs sharply by event class: