Add Slack webhook integration to demo form

[devin-ai-integration]

Add Slack webhook integration and optional phone number field to demo form

Summary

This PR adds Slack webhook integration to the existing demo form, allowing form submissions to be sent to both PostHog (existing) and a specified Slack channel simultaneously. Additionally, an optional phone number field has been added to the form.

Key Changes:

• Added send_data_to_slack() function to send form data to Slack webhook
• Modified send_demo_event() to call both PostHog and Slack webhooks in parallel
• Added optional phone number field to the form UI with consistent styling
• Updated DemoEvent dataclass to include phone number field
• Added environment variable support for Slack webhook URL with fallback
• Improved error handling and logging for webhook failures

Review & Testing Checklist for Human

⚠️ High Priority (5 items - comprehensive testing needed)

• End-to-end form submission test: Fill out and submit the demo form on /pricing page to verify both PostHog and Slack receive the data correctly with all fields including phone number
• Slack webhook payload verification: Check that the Slack channel receives the expected payload format with all fields (firstName, lastName, businessName, etc.) matching the original screenshot requirements
• Phone number field testing: Test the optional phone number field with various formats (international, US format, empty, invalid characters) to ensure it handles edge cases gracefully
• Environment variable configuration: Verify that SLACK_DEMO_WEBHOOK_URL environment variable is properly configured in production to avoid exposing the hardcoded fallback URL
• Error handling verification: Test what happens when Slack webhook fails (e.g., temporarily break the webhook URL) to ensure form submission still completes successfully and errors are logged appropriately

---

Diagram

%%{ init : { "theme" : "default" }}%%
graph TB
    subgraph "Form Submission Flow"
        A["pcweb/pages/pricing/header.py<br/>QuoteFormState.submit()"]:::major-edit
        B["pcweb/pages/pricing/header.py<br/>send_demo_event()"]:::major-edit
        C["pcweb/telemetry/postog_metrics.py<br/>send_data_to_posthog()"]:::context
        D["pcweb/telemetry/postog_metrics.py<br/>send_data_to_slack()"]:::major-edit
        E["pcweb/telemetry/postog_metrics.py<br/>DemoEvent dataclass"]:::major-edit
        F["pcweb/constants.py<br/>SLACK_DEMO_WEBHOOK_URL"]:::minor-edit
    end
    
    subgraph "External Services"
        G["PostHog API"]:::context
        H["Slack Webhook"]:::context
    end
    
    A --> B
    B --> C
    B --> D
    E --> C
    E --> D
    F --> D
    C --> G
    D --> H
    
    subgraph Legend
        L1[Major Edit]:::major-edit
        L2[Minor Edit]:::minor-edit
        L3[Context/No Edit]:::context
    end
    
    classDef major-edit fill:#90EE90
    classDef minor-edit fill:#87CEEB
    classDef context fill:#FFFFFF

Loading

Notes

• Session Details: Requested by tom@reflex.dev | Devin Session
• Testing Screenshots: Local testing screenshots available at /home/ubuntu/screenshots/localhost_3000_215328.png and /home/ubuntu/screenshots/localhost_3000_215406.png showing successful form submission with phone number field
• Code Review: Addressed automated code review comments including field mapping fix, improved error logging, and environment variable usage
• Backward Compatibility: All existing form functionality remains unchanged; phone number field is optional and doesn't affect existing validation logic

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[greptile-apps]

PR Summary

Added Slack webhook integration for demo form submissions, with potential security and data mapping concerns that need addressing.

• Hardcoded Slack webhook URL in pcweb/constants.py should be moved to environment variables for security
• Incorrect data mapping in pcweb/telemetry/postog_metrics.py where company_email is mapped to businessName field
• Basic error handling in send_data_to_slack() needs more detailed logging
• New reusable DemoEvent object pattern in pcweb/pages/pricing/header.py improves code maintainability

_{3 files reviewed, 4 comments
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

logic: Field mapping appears incorrect - company_email is being mapped to businessName. This may cause confusion in Slack notifications.

Suggested change

	"lookingToBuild": event_instance.internal_tools,
	"businessName": event_instance.company_email,
	"lookingToBuild": event_instance.internal_tools,
	"businessName": event_instance.company_name,

[greptile-apps]

style: Consider logging the actual error details to help with debugging webhook failures.

[greptile-apps]

style: consider adding error handling around the Slack call since webhook failures shouldn't block the form submission

Suggested change

	# Send to Slack (new)
	await send_data_to_slack(demo_event)
	# Send to Slack (new)
	try:
	await send_data_to_slack(demo_event)
	except Exception as e:
	# Log error but don't block form submission
	print(f"Failed to send to Slack: {e}")

[greptile-apps]

logic: Move webhook URL to environment variable like other sensitive URLs in this file (e.g. line 102's POSTHOG_API_KEY)

Suggested change

	SLACK_DEMO_WEBHOOK_URL: str = "https://hooks.slack.com/triggers/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"
	SLACK_DEMO_WEBHOOK_URL: str = os.environ.get("SLACK_DEMO_WEBHOOK_URL")