Discord setup

  • Open the Discord server and choose the operations channel.
  • Open channel settings and create a webhook.
  • Name the webhook clearly, for example `InstaChime Leads`.
  • Copy the webhook URL.
  • Paste it into `/settings` in InstaChime and save.

Payload shape

Discord requires at least one content field such as `content` or `embeds`. InstaChime sends a compact lead alert with the contact, source, and message context.

{
  "content": "New lead: Jamie Lee from google_ads",
  "embeds": [
    {
      "title": "Need pricing today",
      "fields": [
        { "name": "Phone", "value": "+15555550123" },
        { "name": "Email", "value": "jamie@example.com" }
      ]
    }
  ]
}

Verify

  • Send an alert test from `/integrations`.
  • Confirm the message appears in the correct channel.
  • Confirm Discord returns a successful response and InstaChime records the delivery.
  • Confirm private channel permissions allow the webhook to post.

Exact Discord setup

  • Open Discord and choose the server.
  • Open the target channel settings.
  • Open Integrations.
  • Create a Webhook.
  • Name it `InstaChime Leads`.
  • Copy the webhook URL.
  • Paste it into InstaChime `/settings` for Discord alerts.
  • Send an alert test from `/integrations`.

Discord payload requirements

  • Send at least one of `content`, `embeds`, `components`, `poll`, or attachment fields.
  • Keep lead messages concise enough to be readable in a channel.
  • Use embeds for structured contact fields when the message is longer.
  • Do not publish the webhook URL; anyone with it can post to the channel.
  • Regenerate the webhook if it is accidentally exposed.

Discord troubleshooting

  • If Discord returns 404, the webhook was deleted or the URL was copied incorrectly.
  • If Discord returns 400, the payload shape is invalid.
  • If messages go to the wrong channel, create a new webhook in the correct channel.
  • If alerts are noisy, create a dedicated private operations channel.
  • If rate limits occur, reduce duplicate alerts and keep one alert per lead event.

Official references

These vendor-owned pages explain the controls and requirements referenced in this guide.