5 minutes to your first alert

By the end of this page you will have one integration under active monitoring and a real change from that integration delivered to Slack — a live alert, not a sample.

Prerequisites

• A signed-in Intello account. If you do not have one, create one; the process takes about 30 seconds.
• A Slack workspace where you have permission to install apps. (Email follows the same flow — substitute in step 3.)

No spec URL or API token is required.

The steps

1. Add an integration from the library

   From the left navigation, open Dependencies → Add Dependency, or browse Dependency Library first. Select a vendor your team relies on in production — for example, Stripe, OpenAI, Anthropic, or Twilio. The library covers approximately 140 vendors, so you should not need to locate a spec URL.

   If the vendor is not in the library, proceed to Add an integration → Bring your own. The remainder of this guide still applies.

2. Confirm the defaults

   Intello suggests a name, a sync cadence, and a default severity-routing configuration. The defaults are appropriate for the majority of teams, and you can adjust them after your first alert.

   Click Save. Intello fetches the current specification and stores it as your baseline — the reference state against which all subsequent changes are compared.

3. Connect Slack

   Open Settings → Integrations → Slack and click Connect. You will be redirected through Slack's OAuth flow, where you can select a default channel. We recommend a dedicated channel such as #api-changes rather than a general channel.

4. Wait for a real change

   No further action is required. The integration is now under active monitoring; when the vendor next ships a change, the alert will appear in Slack. For widely used vendors, this is typically hours to days rather than weeks.

   To see an alert sooner, add a second dependency known to change frequently — fast-moving AI providers and large public APIs commonly publish updates within a day or two.

Next steps

The most valuable follow-up task is to refine who is notified about which changes. The defaults route every alert to a single channel; over time, most teams prefer that breaking changes page the on-call rotation while less urgent changes accumulate in a digest.

This configuration takes only a few minutes; see Tune severity & noise.