Quick Setup

Get dread running in under a minute.

1. Install dread

curl -fsSL https://dread.sh/install | sh

2. Create a channel

A channel is where webhooks get sent. Create one for each service (e.g. Stripe, GitHub):

dread new "Stripe Prod"

This prints your webhook URL. This is the URL you paste into other services:

https://dread.sh/wh/ch_stripe-prod_a1b2c3

Every channel gets its own unique URL. Copy it — you'll paste it in the next step.

3. Paste the URL into your service

Go to whatever service you want to monitor (Stripe, GitHub, Vercel, etc.), find its webhook settings, and paste the URL from step 2. Each guide below shows you exactly where.

4. Start watching

dread

Your First Webhook

Don't have a service ready yet? Send a test event to make sure everything works:

dread test ch_stripe-prod_a1b2c3

Or send a real HTTP request from anywhere:

curl -X POST https://dread.sh/wh/ch_stripe-prod_a1b2c3 \
  -H "Content-Type: application/json" \
  -d '{"event":"test","message":"Hello from curl"}'

Customise Channel Name, Source & Summary

Change the channel name

The channel name is set when you create it with dread new. To rename it, remove and re-add with the new name:

dread remove ch_old-name_abc123
dread add ch_old-name_abc123 "New Display Name"

The channel ID and webhook URL stay the same — only the display name changes in the TUI, notifications, and dashboard.

Change the source label

dread auto-detects the source from HTTP headers (Stripe-Signature, X-GitHub-Event, etc.). For services that aren't auto-detected, add ?source=name to your webhook URL:

https://dread.sh/wh/ch_xxx?source=trigger.dev

Just paste the URL with ?source= into your service's webhook settings — no custom headers needed. You can also use the X-Dread-Source header for programmatic control.

The source label controls how events are grouped in the dashboard and which colour appears in the TUI. Auto-detected sources (stripe, github, vercel, sentry, etc.) always take priority.

Change the summary text

The summary is extracted automatically from known payload formats. For custom services, dread looks for these JSON fields in order:

1. type, event, event_type, action, topic — used as the event type
2. message, description, summary, text, status — used as the summary text

To control what appears in notifications, structure your JSON payload with these fields:

curl -X POST "https://dread.sh/wh/ch_xxx?source=deploy-bot" \
  -H "Content-Type: application/json" \
  -d '{"type":"deploy.success","message":"v2.1.0 deployed to production"}'

Stripe

1. Open Stripe Dashboard → click Developers in the top nav
2. Select Webhooks from the submenu
3. Click Create an event destination
4. Select Account as the event source, then choose Webhook endpoint
5. Paste your dread webhook URL in Endpoint URL
6. Select the events you want (e.g. payment_intent.succeeded, charge.failed) or choose all events for testing
7. Click Add endpoint

PayPal

1. Log in to developer.paypal.com/dashboard
2. Go to Apps & Credentials and select your app (or create one)
3. Open the Webhooks section
4. Click Add Webhook
5. Paste your dread webhook URL (must be HTTPS)
6. Select event types (e.g. PAYMENT.CAPTURE.COMPLETED, BILLING.SUBSCRIPTION.ACTIVATED)
7. Click Save

Paddle

1. Open Paddle Dashboard → Developer Tools → Notifications
2. Click + New destination
3. Select Webhook as the type
4. Paste your dread webhook URL
5. Select events (subscriptions, transactions, customers, adjustments)
6. Click Save destination

Shopify

1. Open Shopify Admin → Settings (bottom left) → Notifications
2. Scroll down to Webhooks and click Create webhook
3. Select an event topic from the dropdown (e.g. orders/create)
4. Set format to JSON
5. Paste your dread webhook URL
6. Click Save

Note: you can't change the event topic after creation — create a new webhook for each topic you need.

Square

1. Log in to developer.squareup.com → open your application
2. Click Webhooks in the left sidebar
3. Click Add subscription
4. Enter a name for the subscription
5. Paste your dread webhook URL in the URL field
6. Select event types: payment.completed, order.created, refund.created, invoice.published, etc.
7. Click Save

Use the Send test event button to verify. Square signs all webhooks with a signature in the x-square-hmacsha256-signature header.

Razorpay

1. Log in to the Razorpay Dashboard
2. Go to Account & Settings → Webhooks
3. Click Add New Webhook
4. Paste your dread webhook URL
5. Enter a Secret (used to verify webhook signatures)
6. Select events: payment.captured, payment.failed, order.paid, subscription.activated, refund.processed, etc.
7. Click Create Webhook

Razorpay sends events in both test and live modes. Toggle between modes in the dashboard to configure webhooks for each.

Recurly

1. Log in to the Recurly Dashboard
2. Go to Integrations → Webhooks
3. Click Configure
4. Click New Endpoint
5. Paste your dread webhook URL
6. Select notification types: new_subscription, successful_payment, failed_payment, canceled_subscription, etc.
7. Click Save

Recurly sends XML payloads by default. dread will detect the source via the X-Recurly-Notification-Type header.

Chargebee

1. Log in to Chargebee → go to Settings → Configure Chargebee
2. Select Webhooks under API & Webhooks
3. Click Add Webhook
4. Paste your dread webhook URL
5. Select V2 API version
6. Choose event types: subscription_created, payment_succeeded, payment_failed, invoice_generated, etc.
7. Click Create

Use the Test Webhook button to send a sample event. Chargebee retries failed deliveries automatically.

Coinbase Commerce

1. Log in to commerce.coinbase.com
2. Go to Settings → Webhook subscriptions
3. Click Add an endpoint
4. Paste your dread webhook URL
5. Click Save
6. Copy the Shared Secret displayed (used for signature verification)

Coinbase Commerce sends events for charges: charge:created, charge:confirmed, charge:failed, charge:pending, charge:resolved.

LemonSqueezy

1. Log in to app.lemonsqueezy.com
2. Go to Settings → Webhooks
3. Click Add webhook (the + button)
4. Paste your dread webhook URL in the Callback URL field
5. Enter a Signing secret
6. Select events: order_created, subscription_created, subscription_payment_success, license_key_created, etc.
7. Click Save webhook

LemonSqueezy signs payloads with HMAC-SHA256 using the signing secret in the X-Signature header.

GitHub

1. Go to your repository → Settings tab → Webhooks in the left sidebar
2. Click Add webhook
3. Paste your dread webhook URL in Payload URL
4. Set Content type to application/json
5. Under "Which events would you like to trigger this webhook?" select Let me select individual events and check the ones you want, or choose Send me everything
6. Make sure Active is checked and click Add webhook

GitHub sends a ping event to confirm the setup.

GitLab

1. Go to your project → Settings → Webhooks
2. Click Add new webhook
3. Paste your dread webhook URL in the URL field
4. Select trigger events: Push events, Merge request events, Issues events, Pipeline events, etc.
5. Click Add webhook

Requires Maintainer or Owner role. Use the Test dropdown to send a test event.

Vercel

Requires Pro or Enterprise plan. Webhooks are configured at the team level, not per project.

1. Go to your Team Settings → Webhooks
2. Click Create Webhook
3. Select events: Deployment (created, succeeded, error), Project (created, removed), etc.
4. Choose target projects (all or specific ones)
5. Paste your dread webhook URL
6. Click Create Webhook and copy the secret key shown (it's only displayed once)

Sentry

1. Go to Settings → Developer Settings
2. Click Create New Integration → select Internal Integration
3. Enter a name for the integration
4. Paste your dread webhook URL in the Webhook URL field
5. Set Permissions: Issue & Event to Read
6. Under Webhooks, check: Issue, Error, and any other events you want
7. Click Save Changes — the integration installs automatically on your org

Linear

1. Click your profile icon → Settings
2. Go to API (under Administration)
3. Click New webhook
4. Paste your dread webhook URL (must be publicly accessible HTTPS)
5. Add a label and select resources: Issues, Comments, Projects, Cycles, etc.
6. Save the webhook

Only workspace admins can create webhooks.

Jira

Requires the Administer Jira global permission.

1. Click the gear icon → System
2. Go to Advanced → WebHooks
3. Click Create a WebHook
4. Enter a name and paste your dread webhook URL
5. Select events (e.g. jira:issue_created, jira:issue_updated, comment_created)
6. Optionally add a JQL filter to limit which issues trigger the webhook (e.g. project = PROD)
7. Click Save

Bitbucket

1. Open your repository in Bitbucket
2. Go to Repository settings → Webhooks
3. Click Add webhook
4. Enter a title and paste your dread webhook URL
5. Under Triggers, select events: push, pull request (created, updated, merged, declined), issue events, etc.
6. Click Save

Bitbucket sends a unique X-Hook-UUID header with each delivery. Use View requests on the webhook to see delivery history.

CircleCI

1. Open your project in CircleCI
2. Go to Project Settings → Webhooks
3. Click Add Webhook
4. Enter a name for the webhook
5. Paste your dread webhook URL in the Receiver URL field
6. Select events: workflow-completed and/or job-completed
7. Click Save

CircleCI includes a circleci-signature header for verification. Payloads include pipeline, workflow, and job details.

Buildkite

1. Go to your Organisation Settings → Notification Services
2. Click Add next to Webhook
3. Paste your dread webhook URL
4. Select events: build.scheduled, build.running, build.finished, job.started, agent.connected, etc.
5. Optionally filter by pipeline
6. Click Add Webhook Notification

Buildkite sends a X-Buildkite-Event header with every delivery. Use the Send test button to verify.

Netlify

1. Open your site in Netlify
2. Go to Site configuration → Notifications
3. Click Add notification → Outgoing webhook
4. Select an event: Deploy started, Deploy succeeded, Deploy failed, Form submission, etc.
5. Paste your dread webhook URL
6. Click Save

Note: Netlify creates one notification per event type. Repeat the steps for each event you want to receive.

AWS SNS

1. Open the SNS console → Topics → Create topic
2. Choose Standard, enter a name, and click Create topic
3. Select your topic, then click Create subscription
4. Set Protocol to HTTPS
5. Paste your dread webhook URL as the endpoint
6. Click Create subscription
7. dread will receive a SubscriptionConfirmation message — the subscription auto-confirms when dread responds with 200

Check the SNS console Subscriptions page — status should change from PendingConfirmation to Confirmed.

PagerDuty

1. Go to Integrations → Generic Webhooks (v3)
2. Click New Webhook
3. Paste your dread webhook URL
4. Select event subscriptions: incident events (triggered, acknowledged, resolved, escalated) and/or service events
5. Optionally add a description and custom headers
6. Click Add Webhook and save the generated webhook secret

Requires Manager, Admin, or Account Owner role. Max 10 webhook subscriptions per scope.

Supabase

Supabase Database Webhooks fire when rows are inserted, updated, or deleted in your tables.

1. Open your project in the Supabase Dashboard
2. Go to Database → Webhooks in the sidebar
3. Click Create a new hook
4. Name your hook (e.g. new-booking) and select the table to watch
5. Tick the events to fire on: Insert, Update, and/or Delete
6. Under Hook type, select HTTP Request
7. Set Method to POST and paste your dread webhook URL
8. Add the header Content-Type: application/json
9. Click Create webhook

The payload includes the type (INSERT/UPDATE/DELETE), the table name, record (new row data), and old_record (previous row data for updates/deletes).

Grafana

1. Open Grafana → go to Alerting → Contact points
2. Click Add contact point
3. Enter a name and select Webhook as the integration type
4. Paste your dread webhook URL
5. Set HTTP method to POST
6. Optionally add a username and password for basic auth
7. Click Save contact point
8. Go to Notification policies and route alerts to your new contact point

Grafana sends alerts with labels, annotations, and the alert state (firing or resolved).

Datadog

1. Log in to Datadog
2. Go to Integrations → Webhooks
3. Click New (or + New)
4. Enter a name for the webhook
5. Paste your dread webhook URL
6. Optionally customise the Payload JSON template using Datadog variables ($EVENT_TITLE, $ALERT_STATUS, etc.)
7. Click Save
8. Use the webhook in monitor notifications by adding @webhook-your-name to the alert message

The webhook only fires when referenced in a monitor — it won't send events on its own.

Cloudflare

1. Log in to the Cloudflare Dashboard
2. Go to Notifications in the left sidebar
3. Click the Destinations tab
4. Under Webhooks, click Create
5. Enter a name and paste your dread webhook URL
6. Click Save and Test — Cloudflare sends a verification request
7. Go to the Notifications tab and create a notification
8. Select an alert type (e.g. Origin Error Rate Alert, DDoS Attack Alert, SSL Certificate Expiration)
9. Choose the webhook as the delivery destination
10. Click Save

Heroku

Heroku uses the app-webhooks add-on for webhook notifications.

1. Install the CLI plugin: heroku plugins:install @heroku-cli/plugin-webhooks
2. Create a webhook:

heroku webhooks:add \
  --app your-app-name \
  --url https://dread.sh/wh/ch_xxx \
  --include api:release api:build api:dyno \
  --level notify

3. Verify with heroku webhooks --app your-app-name

Events include api:release, api:build, api:dyno, api:formation, and api:addon. Set --level sync for guaranteed delivery (slower) or --level notify for best-effort (faster).

Pingdom

1. Log in to my.pingdom.com
2. Go to Settings → Integrations
3. Click Add integration
4. Select Webhook as the type
5. Enter a name and paste your dread webhook URL
6. Click Save integration
7. Go to Monitoring → select a check → Edit
8. Under Connect integrations, select your webhook
9. Click Save

Pingdom sends alerts when checks go up or down, including the check name, status, and response time.

UptimeRobot

1. Log in to uptimerobot.com
2. Go to My Settings (top right)
3. Scroll to Alert Contacts and click Add Alert Contact
4. Select Webhook as the alert contact type
5. Paste your dread webhook URL
6. Select POST as the method
7. Optionally enable Send as JSON (recommended)
8. Click Create Alert Contact
9. Go to your monitor and add the new alert contact under Alert Contacts To Notify

New Relic

1. Log in to New Relic
2. Go to Alerts & AI → Destinations
3. Click Add a destination → select Webhook
4. Enter a name and paste your dread webhook URL
5. Click Save destination
6. Go to Workflows → Add a workflow
7. Set your filter (e.g. policy name, priority, condition)
8. Under Notify, select Webhook and choose your destination
9. Customise the payload template if needed
10. Click Activate workflow

New Relic sends alert notifications with issue details, condition name, and violation details.

Slack (as event source)

This receives events from Slack into dread. (For forwarding dread events to Slack, see Docs → Slack/Discord Forwarding.)

1. Go to api.slack.com/apps → Create New App → From scratch
2. Name your app and select your workspace
3. In the sidebar, click Event Subscriptions and toggle it on
4. Paste your dread webhook URL in Request URL — Slack sends a verification challenge that dread handles automatically
5. Under Subscribe to bot events, add events like message.channels, app_mention, etc.
6. Go to OAuth & Permissions and add the required scopes
7. Click Install App to install to your workspace

Discord (as event source)

This receives interactions from Discord into dread.

1. Go to discord.com/developers/applications → New Application
2. Navigate to the General Information tab
3. Paste your dread webhook URL in Interactions Endpoint URL
4. Click Save Changes — Discord will send test PING requests to verify your endpoint

Your endpoint must handle the PING verification (dread does this automatically). Discord sends all interactions (slash commands, buttons) as HTTP POST requests.

Twilio

1. Log in to console.twilio.com
2. Go to Phone Numbers → Active Numbers
3. Click on the phone number you want to configure
4. Scroll to the Messaging section
5. Under "A Message Comes In", select Webhook
6. Paste your dread webhook URL and set the method to POST
7. Click Save

For Messaging Services: go to Messaging Services → select your service → Integration tab → enter the Inbound Request URL.

SendGrid

1. Log in to SendGrid → go to Settings → Mail Settings
2. Select Event Webhooks
3. Click Create new webhook
4. Paste your dread webhook URL in the Post URL field
5. Select event types: processed, delivered, bounced, open, click, spam report, etc.
6. Toggle Enabled on
7. Click Save

Use Test Your Integration to send a sample payload and verify.

Mailchimp

1. Log in to Mailchimp
2. Go to your Audience → Settings → Webhooks
3. Click Create New Webhook
4. Paste your dread webhook URL in the Callback URL field
5. Select events: subscribes, unsubscribes, profile updates, cleaned, email changed, campaign sent
6. Choose whether to fire for API-initiated changes, admin changes, or subscriber-initiated changes
7. Click Save

Mailchimp sends form-encoded POST data (not JSON). dread handles both formats automatically.

Zendesk

Requires Admin access. Zendesk uses Webhooks (destination) paired with Triggers (rules) to send events.

1. Go to Admin Centre → Apps and integrations → Webhooks
2. Click Create webhook
3. Select Trigger or automation as the connection method
4. Enter a name and paste your dread webhook URL
5. Set request method to POST and format to JSON
6. Click Create webhook
7. Go to Business rules → Triggers → Add trigger
8. Set conditions (e.g. ticket created, status changed)
9. Under Actions, select Notify webhook and choose your webhook
10. Define the JSON body using placeholders ({{ticket.id}}, {{ticket.title}})

Intercom

1. Log in to Intercom
2. Go to Settings → Integrations → Developer Hub
3. Select your app (or create one) → click Webhooks
4. Paste your dread webhook URL in the Webhook URL field
5. Select topics: conversation.created, conversation.user.replied, contact.created, ticket.created, etc.
6. Click Save

Intercom signs webhooks with HMAC-SHA1 using your app's client secret. The signature is in the X-Hub-Signature header.

Postmark

1. Log in to account.postmarkapp.com
2. Select your Server → go to Settings → Webhooks
3. Click Add webhook
4. Paste your dread webhook URL
5. Select message events: Delivery, Bounce, Spam Complaint, Open, Click, Subscription Change
6. Optionally enable Include message content
7. Click Save webhook

Use the Send test button on each event type to verify delivery. Postmark sends a X-Postmark-Webhooks-Auth header if you set an HTTP Auth username/password.

Mailgun

1. Log in to app.mailgun.com
2. Go to Sending → Webhooks
3. Select your domain from the dropdown
4. Click on an event type: Delivered, Opened, Clicked, Bounced, Complained, Unsubscribed, or Failed
5. Paste your dread webhook URL and click Create webhook
6. Repeat for each event type you want

Mailgun signs webhooks using your domain's API key. The signature is in the POST body as signature.token, signature.timestamp, and signature.signature.

Telegram

Telegram uses Bot API webhooks to push updates to your URL instead of polling.

1. Create a bot via @BotFather on Telegram and note the bot token
2. Set the webhook URL using the Telegram API:

curl -X POST "https://api.telegram.org/botYOUR_BOT_TOKEN/setWebhook" \
  -d "url=https://dread.sh/wh/ch_xxx"

3. Verify the webhook is set:

curl "https://api.telegram.org/botYOUR_BOT_TOKEN/getWebhookInfo"

Telegram sends updates for messages, edited messages, channel posts, callback queries, and inline queries.

HubSpot

Requires a HubSpot developer account and a registered app.

1. Log in to your HubSpot developer account
2. Go to your app dashboard and select your app (or create one)
3. Click Webhooks in the left sidebar
4. Enter your dread webhook URL as the Target URL
5. Click Create subscription
6. Select the Object type (Contacts, Companies, Deals, Tickets)
7. Select event types (creation, deletion, property changes)
8. Click Subscribe — subscriptions start paused
9. Hover over the subscription, check it, and click Activate

Typeform

1. Open your form in Typeform
2. Click Connect in the top menu
3. Click the Webhooks tab
4. Click Add a webhook
5. Paste your dread webhook URL
6. Toggle the webhook ON (off by default)
7. Optionally click Edit to add a secret for signature verification

Use View deliveries → Send test request to verify.

Clerk

Clerk uses Svix for webhook delivery.

1. Log in to your Clerk Dashboard
2. Go to Webhooks in the left sidebar
3. Click Add Endpoint
4. Paste your dread webhook URL
5. Select events to receive: user.created, user.updated, user.deleted, organization events, session events, etc. (or leave unselected for all)
6. Click Create
7. Copy the Webhook Signing Secret from the endpoint settings page

Use the Testing tab on your endpoint page to send example events.

Twitch EventSub

Twitch EventSub requires API calls to create subscriptions (no dashboard UI).

1. Register an app at dev.twitch.tv/console → Applications → Register Your Application
2. Note your Client ID and generate a Client Secret
3. Get an access token via the Client Credentials flow:

curl -X POST "https://id.twitch.tv/oauth2/token" \
  -d "client_id=YOUR_CLIENT_ID" \
  -d "client_secret=YOUR_CLIENT_SECRET" \
  -d "grant_type=client_credentials"

4. Create a webhook subscription:

curl -X POST "https://api.twitch.tv/helix/eventsub/subscriptions" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Client-Id: YOUR_CLIENT_ID" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "channel.follow",
    "version": "2",
    "condition": {"broadcaster_user_id": "USER_ID", "moderator_user_id": "USER_ID"},
    "transport": {"method": "webhook", "callback": "https://dread.sh/wh/ch_xxx", "secret": "your-secret"}
  }'

5. Twitch sends a verification challenge — dread responds automatically

Zapier

Zapier can connect 7,000+ apps to dread — even services that don't have native webhooks. Use a Zap to trigger from any supported service and POST to your dread channel.

1. Log in to zapier.com → click Create → Zaps
2. Choose your Trigger app (e.g. Google Sheets, Notion, Airtable, QuickBooks, Monday.com — anything Zapier supports)
3. Configure the trigger event (e.g. "New Row in Spreadsheet", "New Database Item")
4. Connect your account and test the trigger
5. Add an Action step → search for Webhooks by Zapier
6. Select POST as the action event
7. Set the URL to your dread webhook URL
8. Set Payload Type to Json
9. Map fields from the trigger into the payload data (e.g. type = "row.added", message = the row data)
10. Add ?source=google-sheets to the end of your webhook URL to label events
11. Test the action and turn on the Zap

This is the best way to connect services that don't support webhooks natively — Notion databases, Google Sheets, Airtable, Monday.com, Trello, and thousands more.

Calendly

1. Log in to calendly.com
2. Go to Integrations & apps
3. Scroll to Webhooks (under API & connectors) and click Learn more
4. You'll need to use the Calendly API to create a webhook subscription:

curl -X POST "https://api.calendly.com/webhook_subscriptions" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://dread.sh/wh/ch_xxx",
    "events": ["invitee.created", "invitee.canceled"],
    "organization": "https://api.calendly.com/organizations/YOUR_ORG_UUID",
    "scope": "organization"
  }'

5. Get your API token from Integrations & apps → API & connectors → Personal access tokens
6. Get your organisation UUID from GET /users/me

Events: invitee.created (new booking), invitee.canceled (cancelled booking), routing_form_submission.created.

DocuSign

DocuSign Connect sends real-time envelope status updates.

1. Log in to DocuSign Admin
2. Go to Settings → Connect
3. Click Add Configuration → Custom
4. Enter a name for the configuration
5. Paste your dread webhook URL in the URL to Publish field
6. Under Trigger events, select envelope events: Sent, Delivered, Completed, Declined, Voided
7. Set data format to JSON
8. Click Save

Requires DocuSign Admin or Account Administrator role. Use Logs in the Connect settings to debug delivery issues.

Auth0

Auth0 uses Log Streams to send authentication events via webhook.

1. Log in to the Auth0 Dashboard
2. Go to Monitoring → Streams
3. Click Create Log Stream
4. Select Custom Webhook
5. Enter a name and paste your dread webhook URL
6. Set Content Type to application/json
7. Optionally set an Authorization Token (sent as a Bearer token)
8. Under Filter by Event Category, select categories: login success, login failure, signup, password change, etc.
9. Click Save

Auth0 sends events in batches. Each delivery may contain multiple log entries.

LaunchDarkly

1. Log in to LaunchDarkly
2. Go to Integrations in the left sidebar
3. Find Webhooks and click Add integration
4. Paste your dread webhook URL
5. Optionally check Sign this webhook and note the generated secret
6. Select a Policy to filter which events trigger the webhook (or leave blank for all events)
7. Toggle the webhook On
8. Click Save

LaunchDarkly sends events for flag changes, project updates, environment changes, and member actions. Use policy filters to narrow to specific projects or flags.

Figma

Figma webhooks are created via the Figma API (no dashboard UI).

1. Generate a Personal Access Token at figma.com/developers → Manage personal access tokens
2. Find your Team ID from the URL when viewing a team page (e.g. figma.com/files/team/123456)
3. Create a webhook subscription:

curl -X POST "https://api.figma.com/v2/webhooks" \
  -H "Authorization: Bearer YOUR_FIGMA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "event_type": "FILE_UPDATE",
    "team_id": "123456",
    "endpoint": "https://dread.sh/wh/ch_xxx",
    "passcode": "your-secret"
  }'

4. Available event types: FILE_UPDATE, FILE_DELETE, FILE_VERSION_UPDATE, FILE_COMMENT, LIBRARY_PUBLISH

Figma sends events for all files within the specified team. The passcode is included in every payload for verification.

Salesforce

Salesforce sends webhook-style notifications via Outbound Messages in Workflow Rules or Flow.

1. Go to Setup → search Outbound Messages → New Outbound Message
2. Select the Object (e.g. Lead, Opportunity, Case)
3. Set Endpoint URL to your dread channel URL: https://dread.sh/wh/ch_xxx?source=salesforce
4. Select the fields to include in the payload
5. Create a Workflow Rule or Flow that triggers the outbound message on record create/update

Alternatively, use Salesforce Platform Events with a custom Apex trigger to POST JSON to your dread URL for more flexibility.

Notion

Notion doesn't have native outgoing webhooks, but you can use Notion automations with a webhook action or connect via Zapier/Make.

1. Open a Notion database → click Automations (lightning bolt icon)
2. Set a trigger (e.g. When a page is added or When a property changes)
3. Add action → Send webhook
4. Set the URL to your dread channel: https://dread.sh/wh/ch_xxx?source=notion

Alternatively, use the Notion API with a polling script or connect Notion to dread via Zapier using a Webhooks by Zapier action.

Airtable

Airtable supports webhooks via Airtable Automations.

1. Open your base → click Automations in the top bar
2. Create a new automation with a trigger (e.g. When a record is created, When a record is updated)
3. Add action → Send a webhook
4. Set the URL to: https://dread.sh/wh/ch_xxx?source=airtable
5. Configure the body to include the fields you want to track
6. Test and enable the automation

Asana

Asana sends webhooks via its API. Create a webhook subscription using the Asana API.

1. Generate a Personal Access Token at app.asana.com/0/developer-console
2. Find your Project GID from the project URL
3. Create a webhook subscription:

curl -X POST "https://app.asana.com/api/1.0/webhooks" \
  -H "Authorization: Bearer YOUR_ASANA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "data": {
      "resource": "PROJECT_GID",
      "target": "https://dread.sh/wh/ch_xxx?source=asana"
    }
  }'

4. Asana will send a handshake request — dread handles this automatically
5. Events fire for task creation, completion, assignment, comments, and more

Webflow

Webflow supports webhooks for site, form, and e-commerce events.

1. Go to Site Settings → Integrations → Webhooks
2. Click Add Webhook
3. Select a Trigger Type (e.g. Form submission, Site publish, Ecommerce order)
4. Set the Webhook URL to: https://dread.sh/wh/ch_xxx?source=webflow
5. Click Add Webhook to save

Available triggers include: form_submission, site_publish, page_created, ecomm_new_order, ecomm_order_changed, memberships_user_account_added, and more.

Custom / Any Service

Any service that sends JSON webhooks works with dread. Just point it at your channel URL:

curl -X POST "https://dread.sh/wh/ch_xxx?source=myapp" \
  -H "Content-Type: application/json" \
  -d '{"type":"deploy.success","message":"v1.2.3 deployed to production"}'

Add ?source=myapp to the URL to control the source label. Use type or event in your JSON for the event type, and message or description for the summary text. You can also use the X-Dread-Source header instead.

For all other features (muting, alerts, export, digest, forwarding, status page, dashboard), see the Documentation.