AugmentClaude

Luma Webhook Enrichment

Enrich Luma registration events and sync guest data to your CRM or database.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/luma-inbound-webhook-enrich-getaero-io/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Works for every skill.

    What this command does
    1. Makes a new, empty temporary folder.
    2. Downloads the skill's folder, drafts/luma-inbound-webhook-enrich, from github.com/getaero-io/gtm-eng-skills (branch main), the GitHub repository it's listed from. You get the version that is there now, not a copy we keep.
    3. Copies that folder to ~/.claude/skills/luma-inbound-webhook-enrich-getaero-io/.
    4. Deletes the temporary folder.

    Installing runs none of the skill's files; it only downloads and copies them. When you later use the skill, Claude follows its SKILL.md and may run scripts that come with it. Read them first.

    How we check skills, and what we don't · Report this skill

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

DRAFT. Design and harden a standing Luma registration/unsubscribe webhook that enriches guests and writes to CRM or customer DB — with backfill and versioning. Not installed by deepline skills.

What this skill does

Luma inbound webhook enrich (DRAFT)

Goal

Registration events become a durable system: webhook → validate → normalize LinkedIn → enrich → upsert CRM/DB → optional Slack notify. Not a one-off CSV import after the event.

Design checklist

  1. Trigger: Luma registration / unsubscribe (document exact event names you subscribe to).
  2. Idempotency: upsert key = email (plus event id).
  3. Normalize: LinkedIn slug → canonical https://www.linkedin.com/in/... URL.
  4. Enrich: cheap fields first; gate expensive providers.
  5. Write: CRM or customer DB fields listed in references/field-map.md.
  6. Failure mode: keep original failed payload; dead-letter queue; backfill later.
  7. Versioning: bump play/workflow version on each mapping change; never silent overwrite of prod without dry-run.

Backfill pattern

  1. Export failed webhook payloads (or Luma guest delta since last success).
  2. Re-run through the current versioned play.
  3. Leave original failed records intact for audit.
  4. Report: attempted / succeeded / still failing.

Pair with

  • luma-event-campaign for outbound staging
  • event-ops-score-and-door for capacity decisions (separate from inbound enrich)

Guardrails

  • Do not log raw PII into public git.
  • Secrets only via secret store / workflow secrets — never in SKILL.md.
  • Ask before replaying large historical backfills (cost + CRM noise).

Related skills