Automate workflows with form submission webhooks

A webhook is a URL that receives data when an event happens. When someone submits your form:

1. LazyForms processes the submission
2. LazyForms sends a POST request with JSON data to your webhook URL
3. Your receiving system processes the data however you want

It's a simple, standardized way to connect systems.

LazyForms sends this JSON to your webhook URL:

{
  "form_id": "abc123",
  "form_name": "Contact form",
  "data": {
    "name": "Jane Doe",
    "email": "jane@example.com",
    "message": "Hello!"
  },
  "submitted_at": "2025-01-15T10:30:00Z",
  "ip": "203.0.113.1"
}

The `data` object contains all form fields. The request includes a `Content-Type: application/json` header.

1. Go to your form settings in the LazyForms dashboard
2. Paste your webhook URL in the "Webhook URL" field
3. Save

That's it. Every new submission triggers a POST to your URL.

Send form submissions to a Slack channel:

1. Create a Slack Incoming Webhook URL in your Slack workspace settings
2. Create a small serverless function (or use Pipedream/Make/n8n) that receives LazyForms webhook data and formats it for Slack
3. Paste that function's URL as your LazyForms webhook

Or use Zapier/Make to connect LazyForms webhooks directly to Slack without code.

Add form leads to your CRM automatically:

1. Use your CRM's API endpoint as the webhook URL (if it accepts POST JSON)
2. Or use a middleware like Zapier/Make/n8n to transform the data and push to your CRM

Popular CRMs with webhook-compatible APIs: HubSpot, Pipedrive, Salesforce (via middleware).

Post submissions to a Discord channel:

1. Create a Discord Webhook URL in your server's channel settings
2. Use a middleware to transform LazyForms payload into Discord's embed format
3. Or use a serverless function to reformat and forward

Discord webhooks expect a specific format (`content` or `embeds`), so a transformation step is needed.

LazyForms webhook delivery:

• Sends immediately on submission (fire-and-forget)
• Timeout: 10 seconds
• No automatic retries currently (planned for Pro)
• Your webhook should respond with a 2xx status code

For critical workflows, use a reliable intermediary like Zapier or a queue-based system.