Make.com Documentation

Start with Make

The easiest way to connect Discord to Make is with the WebhookBridge custom app.

1. Install the custom app in Make.
2. Create a Discord connection and authorize the requested Discord permissions.
3. Add Watch new Discord messages to a scenario.
4. Create a webhook, choose your Discord server, then select one or more channels.
5. Send a message in a selected channel to start the scenario instantly.

Only Discord server administrators can connect channels. When you create or reconnect the Discord connection, Discord lets you choose a server to install WebhookBridge in. Only servers where WebhookBridge is installed and you are an administrator are listed.

Make modules

The current WebhookBridge custom app includes these modules:

• Watch new Discord messages — an instant trigger that runs when a new non-bot message is posted in one of the selected Discord channels.
• Make an API call — the universal module. It performs an arbitrary authorized API call to WebhookBridge for endpoints that are not covered by a dedicated module.

The instant trigger uses a dedicated Make webhook. When the webhook is created, updated, or deleted in Make, the custom app calls the corresponding WebhookBridge API endpoint automatically.

API base URL

https://webhookbridge-api.werkingdev.com

The API is used by the Make custom app. For protected API requests, the app supplies the Discord OAuth access token and WebhookBridge app authentication automatically. Normal users do not need to add those authentication headers manually. The Make an API callmodule accepts a relative path such as /v1/make/me and resolves it against this base URL.

Authentication

Within Make, authentication is added automatically by the WebhookBridge custom app:

Authorization: Bearer YOUR_DISCORD_OAUTH_ACCESS_TOKEN

For protected Make API requests, the custom app also adds its internal X-WebhookBridge-App-Secret header automatically. The OAuth connection validation call uses the Discord bearer token only. Do not enter or expose that secret in a Make scenario.

The integration uses only these Discord OAuth scopes:

identify guilds bot

The connected Discord user must be the server owner or have the Administrator permission for every server they manage through the API.

Connection validation

The Make connection verifies the current Discord OAuth access token through WebhookBridge instead of calling the Discord user endpoint directly. WebhookBridge validates the token with Discord internally and returns basic identity information to Make.

GET /v1/make/me

Successful response:

{
  "id": "456789012345678901",
  "username": "exampleuser",
  "global_name": "Example User",
  "avatar": "example-avatar-hash"
}

This endpoint is also a simple way to verify the authenticated connection with the Make an API call module.

Pagination

The server and channel list endpoints accept these optional query parameters:

List responses include has_more, limit, and offset so an integration can request another page when needed.

List available Discord servers

GET /v1/make/guilds?limit=100&offset=0

Example response:

{
  "guilds": [
    {
      "id": "123456789012345678",
      "name": "Example Server"
    }
  ],
  "has_more": false,
  "limit": 100,
  "offset": 0
}

Only servers where the connected user is an administrator and WebhookBridge is installed are returned.

List eligible channels in a server

GET /v1/make/guilds/{guildId}/channels?limit=100&offset=0

Example response:

{
  "channels": [
    {
      "id": "234567890123456789",
      "name": "#announcements"
    }
  ],
  "has_more": false,
  "limit": 100,
  "offset": 0
}

WebhookBridge returns text and announcement channels that the bot can view.

Create a Make webhook connection

POST /v1/make/hooks
Content-Type: application/json

{
  "guild_id": "123456789012345678",
  "channel_ids": [
    "234567890123456789",
    "345678901234567890"
  ],
  "webhook_url": "https://hook.make.com/your-webhook-url",
  "make_webhook_id": "your-make-webhook-id"
}

One Make webhook can receive messages from multiple Discord channels. The Make custom app handles this setup automatically. The request must contain at least one channel and no more than 25 channel IDs; the Discord server’s current WebhookBridge plan can allow fewer. The webhook_url must be a public HTTPS Make webhook URL on a make.com host.

Successful response:

{
  "id": "your-make-webhook-id"
}

Update a Make webhook connection

PUT /v1/make/hooks/{makeWebhookId}
Content-Type: application/json

{
  "guild_id": "123456789012345678",
  "channel_ids": [
    "234567890123456789"
  ],
  "webhook_url": "https://hook.make.com/your-webhook-url"
}

Successful response:

{
  "id": "your-make-webhook-id"
}

Delete a Make webhook connection

DELETE /v1/make/hooks/{makeWebhookId}

Deleting the saved WebhookBridge webhook in Make > Webhooks disconnects every Discord channel attached to that Make webhook.

Successful response:

{
  "detached": true
}

What a scenario receives

Each new, non-bot Discord message forwarded to the Make webhook uses this payload shape:

{
  "guildId": "123456789012345678",
  "guildName": "Example Server",
  "channelId": "234567890123456789",
  "channelName": "announcements",
  "messageId": "345678901234567890",
  "userId": "456789012345678901",
  "username": "exampleuser",
  "displayName": "Example User",
  "message": "Hello from Discord",
  "attachments": [
    {
      "url": "https://cdn.discordapp.com/...",
      "content_type": "image/png",
      "filename": "example.png"
    }
  ],
  "timestamp": "2026-09-18T12:00:00.000Z"
}

A scenario can route text, image, video, and other attachment posts differently using Make filters.

Connection rules

• A Discord channel can have one active WebhookBridge destination at a time.
• A channel already connected manually through the Discord dashboard cannot also be attached to Make until that manual connection is disconnected.
• A channel managed by a Make webhook must be removed in Make > Webhooks before creating a manual connection from /dashboard.
• Channel limits and forwarded-message allowances apply to each Discord server’s WebhookBridge plan.

Common errors

Support

For setup, privacy, billing, or general support, email:

📧 support.webhookbridge@werkingdev.com

For paid subscription management, open /dashboard, choose Plan & Usage, then useManage Billing.