Incoming webhooks in Team

Generate a secret URL so an external system can post messages into a Team space with a POST.

Jun 26, 2026

Watch this step in the video · Manage the space

What an incoming webhook is

An incoming webhook gives you a secret URL so an external system —GitHub, your own server, an alert monitor, etc.— can post messages into a Team space with a simple POST request. It's the most direct way to bring notifications from other tools into your team conversation, with no full integration to build.

This is an advanced feature, and only space admins can manage it.

Requirements

  • Permission to manage the space (the Webhooks tab only shows for admins).
  • An external system that can send a JSON POST.

Steps to create a webhook

  1. Open the space in Team and go to its settings panel (gear icon in the header).
  2. Open the Webhooks tab.
  3. Type a name (e.g. GitHub, Server) and click Generate.
  4. Omnifox shows the URL only once: "Copy the URL now — you won't be able to see it again." Click Copy and store it safely.

The URL looks like this:

POST https://omnifox.io/api/team/hooks/{token}

How to post a message

Send a POST with a JSON body. Two shapes are accepted:

  • Simple: {"text": "Deploy finished ✅", "title": "CI/CD"} — the optional title becomes a bold first line.
  • Slack-style: {"text": "...", "attachments": [...]} — it reads text, or the first attachment's fallback/text/pretext. So many senders that already post to Slack just work.

curl example:

curl -X POST https://omnifox.io/api/team/hooks/YOUR_TOKEN \
  -H "Content-Type: application/json" \
  -d '{"text":"Nightly backup OK","title":"Server"}'

The message is authored as Integration with a Webhook badge. A 201 response confirms it was posted.

Manage and revoke

  • Regenerate: creates a new token and invalidates the current URL immediately.
  • Revoke: disables the URL permanently.
  • The token is never stored in clear text (only a hash), and the endpoint is write-only: a leaked URL can't read the space's content.

Verify it works

  • Send the curl example and check the card shows up in the space with the Webhook badge.
  • 201 = posted; 422 = no text was found in the body.

If it doesn't work

  • 404: unknown or revoked token (or a POST to the wrong route).
  • 410: the space was archived or deleted.
  • 422: the body had no usable text.
  • 429 / rate limit: the endpoint is limited to 60 requests per minute per IP and token; space your calls out.
  • Text is trimmed to 4 KB; send summaries, not whole logs.

Tips

  • Create one webhook per source (one for CI, one for alerts) so you can revoke them separately.
  • If you suspect the URL leaked, hit Regenerate and update the sending system.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp