event-hog
Search/

← Changelog

0.1.0

Anyone can copy one prompt from eventhog.cc and be working a conference in two questions

No admin, no secret to edit: the prompt carries a private link, the agent connects itself, asks which company and which conference, and picks up before, during or after. Plus lead enrichment, and CRM sync that brings the meetings and follow-ups along.

Event-HogOnboardingSplash-PageCRMLead-Enrichment

Why Care?

Before this, joining meant the admin made a key, pasted it into the PEOPLE secret along with everyone else’s, and sent the link. Now a teammate (or anyone) opens eventhog.cc, copies one prompt, and pastes it into Claude, ChatGPT, Cursor, Claude Code or Codex.

What’s New?

  • A registration desk on eventhog.cc. “Pick up your badge” holds a setup prompt with a private connector link made in the browser. The agent adds the server itself where it can (Cursor, Claude Code, Codex) and walks the person through Settings, Connectors where it can’t (Claude, ChatGPT).
  • Members are made on first use. A new key becomes a person in D1 (members, migration 0006) the first time an agent calls with it. PEOPLE still works, and still wins for the keys it lists.
  • get_started asks two questions. Which company do you represent, and which conference are you going to. It finds or starts the event’s workspace, works out from the dates whether you’re before, during or after it, and returns that phase’s playbook.
  • Before: who’s worth finding. conference-attendee-export pulls the attendee list from the event’s app or site, save_attendees keeps it, and prioritize-attendees ranks it against your ideal customer into save_targets. During the show, targets answers “who should I find next?”.
  • enrich_people. Name and company in, confirmed title, organization, LinkedIn and location out, from context.dev’s People Enrich API with the deployment’s key, so the person never sees it. Every answer, including “not found”, is cached in D1 (enrichments, migration 0007), so nobody pays for the same person twice.
  • After: the CRM gets the conversations too. crm_queue and export_hubspot_csv take met_by (everyone, ["me"], or ["me", "Michael"]) and owner (whoever met them, or me). Each conversation goes to HubSpot as a completed meeting, owned by whoever had it, and each follow-up as a task. mark_touchpoints_synced records their IDs.
  • draft-follow-up-emails. Ranks who to follow up with and drafts each email from what was actually said, for the person to send (or to hand to a sequencer like Origami).
  • Skills ship inside the Worker. kit/ is bundled at build time (scripts/bundle-kit.mjs), so skills and the event template don’t need pushing to Artifacts. Per-person settings still live in the event-hog-kit repo.
  • Two passes, not three. The splash now offers “Use our Cloudflare” (copy the prompt) or “Self host” (deploy your own Worker).