This implementation sends an initial Discord notification immediately, then updates it with enriched data when Clay completes processing.

1. User signs up → Clerk webhook triggers
2. Val sends basic info to Discord immediately (with "enriching..." message)
3. Val sends data to Clay for enrichment
4. Clay processes enrichment (takes 10-60 seconds)
5. Clay calls back to your Val with enriched data
6. Val sends a follow-up Discord message with full enrichment

• Add "HTTP API" as first column
• Set as webhook receiver
• Copy the generated webhook URL
• This receives data from your Val

Map these fields from the webhook data:

• email
• profile_image_url
• signup_timestamp
• callback_url (important!)

• Find Person from Email: Maps email → person data
• Enrich Company: Uses company from person data
• Any other enrichments you want

Add "HTTP API" column at the end:

• Method: POST
• URL: Use the {{callback_url}} field
• Headers:

  {
    "Content-Type": "application/json",
    "Authorization": "Bearer YOUR_SECRET_KEY"
  }

• Body: Map all enriched fields:

  {
    "email": "{{email}}",
    "full_name": "{{person_full_name}}",
    "company": "{{company_name}}",
    "title": "{{person_title}}",
    "linkedin": "{{person_linkedin_url}}",
    "location": "{{person_location}}",
    "industry": "{{company_industry}}",
    "company_size": "{{company_size}}",
    "company_website": "{{company_website}}"
  }

• Configure the table to run automatically when new rows are added
• Or set it to run when webhook is received

Add these to your Val:

• CLAY_WEBHOOK_URL: The inbound webhook URL from Clay
• CLAY_WEBHOOK_SECRET: A secret key for authenticating Clay callbacks
• VAL_TOWN_URL: Your Val's base URL (e.g., https://yourval.val.run)

Your Val now has two endpoints:

1. /newUserWelcomeEmail - Receives Clerk webhooks
2. /clayCallback - Receives Clay enrichment callbacks

1. Trigger a test signup or manually call the Clerk webhook
2. Check Discord for initial message with "Enriching data with Clay..."
3. Wait 10-60 seconds for Clay to process
4. Check Discord for second message with enriched data

• Discord Limitation: Discord webhooks can't edit messages, so we send a second message
• Storage: Current implementation uses in-memory storage (resets on Val restart)
• Cleanup: Old pending enrichments are automatically cleaned up after 1 hour
• Fallback: If Clay fails or is not configured, users still get the basic notification

1. Use Val.town Blob Storage: Store pending enrichments persistently
2. Discord Bot: Use a bot token instead of webhook to edit messages
3. Retry Logic: Re-send to Clay if enrichment fails
4. Batching: Collect multiple signups and enrich in batches