Team & Settings

Messaging

Messaging sends Routebase alerts into a chat channel, formatted for the client instead of as raw JSON. When a live API response drifts from your published contract, when a monitor opens an incident, or when a scheduled test fails, the people who need to act see it where they already work.

Channels are managed per organization under Settings → Messaging (in the Automation & Integrations group).

Messaging is a Starter plan feature and requires the notifications:manage permission (Admins and Owners by default). Connected channels are webhooks under the hood, so they count against the webhook limit of your plan — see the Usage panel in Billing.

Connecting Slack

There are two ways, and both end in the same place — an incoming webhook that Routebase posts to.

Add to Slack (one click)

Select Add to Slack on the Slack card. Slack asks which workspace and which channel the app may post to, and after you confirm you land back in Routebase with the channel connected and a test message already delivered.

You will see a notice on Slack's authorization screen saying the app has not been reviewed by Slack. That is expected and says nothing about the app's safety: Slack shows it for every app that is not listed in the Slack Marketplace, and listing requires an app to already be installed in several workspaces. What you are granting is a single permission — incoming-webhook — which lets Routebase post messages to the one channel you pick. It cannot read messages, cannot see other channels, and cannot access files or member data.

If your workspace requires admin approval for apps, your request goes to a workspace admin instead of installing directly.

Connect manually (webhook URL)

Select Connect manually if your workspace blocks third-party apps, or if you would rather own the Slack app yourself. The dialog contains a setup guide and a ready-made app manifest: create an app from the manifest in your own workspace, enable an incoming webhook for a channel, and paste the resulting URL back into Routebase.

Because the app then belongs to your workspace, Slack shows no marketplace notice at all. The trade-off is a two-minute setup and an app icon you upload yourself.

Connecting Microsoft Teams

Teams has no equivalent one-click install — Microsoft retired the classic Office 365 connectors, and the replacement runs through Teams Workflows. Select Connect on the Teams card and follow the steps in the dialog:

  1. In Teams, open the channel menu (…) and choose Workflows. This entry point preselects the team and channel. If the menu has no Workflows entry, the app is not available in your tenant yet — the dialog links straight to it in the Teams store.
  2. Search the templates for Send webhook alerts to a channel — the dialog has a copy button for the exact name. Older Teams versions call the same template Post to a channel when a webhook request is received.
  3. Confirm the team and channel, then add the workflow.
  4. Copy the workflow URL and paste it into the dialog.

Why there is no Add to Teams button: a Teams webhook URL can only be created by you inside Power Automate. Microsoft offers no API that lets an outside app mint one, and publishes no stable deep link to an individual workflow template — so the steps above are as short as the platform allows.

Teams messages are sent as Adaptive Cards.

What gets sent

When you connect a channel you choose categories rather than raw event names:

Category Sends On by default
Contract drift A live response deviates from your published spec Yes
Incidents & recovery A monitor opens an incident, resolves it, or recovers Yes
Test failures A scheduled test run fails No
Security findings Scan results and newly found issues No
Spec publishes & breaking changes A spec version is published or a breaking change is detected No

A drift alert carries the monitor, the affected route, up to five concrete changes with field path, change type and expected vs. received value, a severity summary, and a link straight into Routebase. Colour follows severity — red when the drift includes errors, amber when it is warnings only. Every other subscribed event arrives as a one-line message.

Channels connected here do not appear on the Webhooks page — that page is for raw JSON integrations with your own services.

Managing a channel

The … menu on a connected channel offers:

  • Send test message — posts a sample message so you can confirm the channel still works. Only available while the channel is active.
  • Edit notifications — change the categories, or the webhook URL for manually connected channels.
  • Delivery history — every delivery with status, HTTP code, attempts and timestamp. The first place to look when messages stop arriving.
  • Pause / Resume — stop delivering without losing the configuration.
  • Disconnect — remove the channel from Routebase. This does not delete the incoming webhook in Slack or the workflow in Teams; remove those on the provider side if you want them gone.

Reconnecting the same channel

Running Add to Slack again for a channel that is already connected does not create a second entry. Slack issues a fresh webhook URL on every install, so Routebase updates the existing connection with the new URL and keeps the categories you selected. Use this if messages stopped arriving after someone reinstalled or removed the app in Slack.

Troubleshooting

No messages arrive. Open Delivery history. If deliveries are listed as failed, the webhook URL is no longer valid on the provider side — reconnect the channel. If there are no deliveries at all, nothing you subscribed to has happened yet; send a test message to confirm the channel itself works.

The connect flow returns with an error. The message names the reason: a cancelled install, an expired link (restart the flow — the connection link is valid for ten minutes), a plan limit that is reached, or a rejection from Slack.

Drift alerts never come, but incidents do. Drift is only detected for monitors linked to a spec endpoint with schema validation enabled. See Monitors for how to turn on drift watching for a spec.

Messages arrive as raw JSON. The channel was created on the Webhooks page rather than here. Reconnect it under Messaging so it gets the provider formatting.