Rebase + Slack. Your channel, in the loop.
Paste one incoming webhook and Rebase posts to your channel when tickets are filed and resolved — compact messages that link straight to the ticket.
Create an incoming webhook
In Slack: Apps → Incoming Webhooks → Add to Slack, and pick the channel it should post to.
Paste it into Rebase
Settings → Integrations → Slack. The URL is stored encrypted and never echoed back.
Send a test message
One click posts to your channel, so you know it works before a real ticket does.
// Signal in the channel
Short messages, real links.
Each post is compact: a headline and the ticket title linking straight to the ticket, plus a context line with the page's pathname — and, for new tickets, who reported it.
- New-ticket and resolved posts, each with its own toggle
- Deep links land on the ticket, on the page
- No channel flooding — two event types, that's it
New ticket — Pay now button does nothing on checkout
posted by rebase · no bot user
// Boring reliability
Never blocks a ticket.
Notifications are best-effort by design. Delivery runs as a queued job with retries and backoff — and if Slack is down, tickets still flow to Rebase and your tracker exactly as normal.
- Retries with backoff on transient failures
- Stops immediately if the webhook is revoked
- Webhook stored encrypted; only a masked hint is shown
// The details
The whole surface. Two minutes to wire.
- A standard incoming webhook — no OAuth dance, no bot to install
- The URL is validated against hooks.slack.com
- Write-only secret: stored encrypted, never echoed back
- Per-event toggles — new tickets and resolved tickets
- A test-message button to verify the channel
- Posts link straight to the ticket on your page
- Best-effort delivery that never blocks the ticket pipeline
- Disconnect keeps your preferences for easy reconnects
Frequently asked questions
No. Rebase posts through a standard incoming webhook you create in Slack (Apps → Incoming Webhooks). There's no OAuth flow and no bot user in your workspace.
Two events, each with its own toggle: a post when a ticket is filed and a post when one is resolved — the ticket title linking straight to the ticket, the page's pathname, and, for new tickets, the reporter.
Nothing breaks. Delivery is a queued job with retries and backoff, and tickets keep flowing to Rebase and your tracker as normal. If Slack reports the webhook as revoked, Rebase stops retrying immediately.
// More integrations
Works with the rest of your stack. One layer, every tool.
Start shipping feedback faster.
Start your 7-day free trial.