feat(webhook-triggers): multiple webhook trigger blocks (#725)

* checkpoint

* correctly clear status

* works

* improvements

* fix build issue

* add docs

* remove comments, logs

* fix migration to have foreign ref key

* change filename to snake case

* modified dropdown to match combobox styling

* added block type for triggers, split out schedule block into a separate trigger

* added chat trigger to start block, removed startAt from schedule modal, added chat fields into tag dropdown for start block

* removed startedAt for schedules, separated schedules into a separate block, removed unique constraint on scheule workflows and added combo constraint on workflowid/blockid and schedule

* icons fix

---------

Co-authored-by: Waleed Latif <walif6@gmail.com>

apps/docs/content/docs/blocks/meta.json

@@ -4,12 +4,13 @@
     "agent",
     "api",
     "condition",
-    "function",
     "evaluator",
-    "router",
-    "response",
-    "workflow",
+    "function",
     "loop",
-    "parallel"
+    "parallel",
+    "response",
+    "router",
+    "webhook_trigger",
+    "workflow"
   ]
 }

apps/docs/content/docs/blocks/webhook_trigger.mdx

@@ -0,0 +1,113 @@
+---
+title: Webhook Trigger
+description: Trigger workflow execution from external webhooks
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Card, Cards } from 'fumadocs-ui/components/card'
+import { ThemeImage } from '@/components/ui/theme-image'
+
+The Webhook Trigger block allows external services to trigger your workflow execution through HTTP webhooks. Unlike starter blocks, webhook triggers are pure input sources that start workflows without requiring manual intervention.
+
+<ThemeImage
+  lightSrc="/static/light/webhooktrigger-light.png"
+  darkSrc="/static/dark/webhooktrigger-dark.png"
+  alt="Webhook Trigger Block"
+  width={350}
+  height={175}
+/>
+
+<Callout>
+  Webhook triggers cannot receive incoming connections and do not expose webhook data to the workflow. They serve as pure execution triggers.
+</Callout>
+
+## Overview
+
+The Webhook Trigger block enables you to:
+
+<Steps>
+  <Step>
+    <strong>Receive external triggers</strong>: Accept HTTP requests from external services
+  </Step>
+  <Step>
+    <strong>Support multiple providers</strong>: Handle webhooks from Slack, Gmail, GitHub, and more
+  </Step>
+  <Step>
+    <strong>Start workflows automatically</strong>: Execute workflows without manual intervention
+  </Step>
+  <Step>
+    <strong>Provide secure endpoints</strong>: Generate unique webhook URLs for each trigger
+  </Step>
+</Steps>
+
+## How It Works
+
+The Webhook Trigger block operates as a pure input source:
+
+1. **Generate Endpoint** - Creates a unique webhook URL when configured
+2. **Receive Request** - Accepts HTTP POST requests from external services
+3. **Trigger Execution** - Starts the workflow when a valid request is received
+
+## Configuration Options
+
+### Webhook Provider
+
+Choose from supported service providers:
+
+<Cards>
+  <Card title="Slack" href="#">
+    Receive events from Slack apps and bots
+  </Card>
+  <Card title="Gmail" href="#">
+    Handle email-based triggers and notifications
+  </Card>
+  <Card title="Airtable" href="#">
+    Respond to database changes
+  </Card>
+  <Card title="Telegram" href="#">
+    Process bot messages and updates
+  </Card>
+  <Card title="WhatsApp" href="#">
+    Handle messaging events
+  </Card>
+  <Card title="GitHub" href="#">
+    Process repository events and pull requests
+  </Card>
+  <Card title="Discord" href="#">
+    Respond to Discord server events
+  </Card>
+  <Card title="Stripe" href="#">
+    Handle payment and subscription events
+  </Card>
+</Cards>
+
+### Generic Webhooks
+
+For custom integrations or services not listed above, use the **Generic** provider. This option accepts HTTP POST requests from any client and provides flexible authentication options:
+
+- **Optional Authentication** - Configure Bearer token or custom header authentication
+- **IP Restrictions** - Limit access to specific IP addresses
+- **Request Deduplication** - Automatic duplicate request detection using content hashing
+- **Flexible Headers** - Support for custom authentication header names
+
+The Generic provider is ideal for internal services, custom applications, or third-party tools that need to trigger workflows via standard HTTP requests.
+
+### Webhook Configuration
+
+Configure provider-specific settings:
+
+- **Webhook URL** - Automatically generated unique endpoint
+- **Provider Settings** - Authentication and validation options
+- **Security** - Built-in rate limiting and provider-specific authentication
+
+## Best Practices
+
+- **Use unique webhook URLs** for each integration to maintain security
+- **Configure proper authentication** when supported by the provider
+- **Keep workflows independent** of webhook payload structure
+- **Test webhook endpoints** before deploying to production
+- **Monitor webhook delivery** through provider dashboards
+
+