Webhook Trigger

​

Overview

​

When to Use Webhook Trigger

• Receiving events from external services (GitHub, Stripe, custom apps)
• Real-time data processing from external systems
• Building custom integrations
• Connecting services that support webhooks (including other workflows)
• API-driven workflows initiated by other systems

• User-facing data collection (use Form Trigger)
• Scheduled recurring tasks (use Scheduled Trigger)
• Native integration events (use Integration Trigger)

​

Configuration

​

Basic Setup

• Unique Webhook URL: A secure endpoint for receiving requests
• Webhook ID: Identifier for your webhook

​

Security Options

1. Add a Secret (optional)
   • Set a secret value in the webhook configuration
   • Include this secret in the request header or body when calling the webhook
   • Only requests with the correct secret will trigger the workflow
2. No Secret (default)
   • Webhook is publicly accessible
   • Anyone with the URL can trigger it
   • Good for testing and low-security use cases

​

How It Works

1. External system sends HTTP POST request to webhook URL
2. Webhook validates authentication (if configured)
3. Request payload is parsed (JSON)
4. Workflow starts with payload data available as {{trigger}}
5. Webhook responds immediately with 200 OK
6. Workflow processes asynchronously

​

Making Requests to Your Webhook

​

Basic Request

curl -X POST https://app.langdock.com/api/workflows/webhooks/abc123 \
  -H "Content-Type: application/json" \
  -d '{"key": "value"}'

​

Example Use Cases

​

GitHub Webhook Integration

Webhook Trigger (GitHub push events)
→ Agent: Analyze commit messages
→ Condition: Check if documentation updated
  → Yes: Regenerate docs
  → No: Continue
→ Notification: Send deployment status

• URL: Your webhook URL
• Events: Push, Pull Request
• Content type: application/json

​

Stripe Payment Webhook

Webhook Trigger (Stripe events)
→ Code: Validate Stripe signature
→ Condition: Check event type
  → payment_succeeded: Update user account
  → payment_failed: Send retry notification
  → subscription_canceled: Deactivate access

​

Custom Application Integration

Webhook Trigger
→ Code: Validate and transform data
→ HTTP Request: Enrich data from external API
→ Agent: Analyze and categorize
→ Action: Create record in CRM

​

Slack Command Integration

Webhook Trigger (from Slack slash command)
→ Agent: Process natural language command
→ HTTP Request: Execute action in external system
→ HTTP Response: Send result back to Slack

​

Accessing Webhook Data

{{trigger.output.user_id}}
{{trigger.output.event_type}}
{{trigger.output.data.amount}}

Event: {{trigger.output.event}}
Order: {{triggeroutput.order_id}}
Customer: {{trigger.output.customer_name}}
First Item: {{trigger.output.items[0].product}}

​

Response Codes

​

Next Steps