Domain mapping & impact
minThe single feature that turns Intello from "we got an alert" into "we got an alert and we already know which service breaks." Worth the fifteen minutes it takes to set up.
What a mapping is
A domain mapping connects a slice of an external API to a thing inside your product. Most teams map at the service or feature level:
| External API | Endpoint scope | Maps to |
|---|---|---|
| Stripe | /customers/*, /subscriptions/* | billing-service |
| OpenAI | /v1/chat/completions | chat-feature |
| Twilio | /Messages | notifications-service |
When a change hits any endpoint in a mapped scope, the alert names the affected service.
How to set them up
Settings → Domain mappings. For each mapping:
- Pick the integration.
- Pick the path scope (whole API, specific paths, specific tags).
- Name the affected internal service or area in your product.
- Optionally assign a default owner — that person gets the alert routed to them automatically when changes hit this scope.
That's it. There's no code instrumentation, no SDK to install. You're telling Intello what your team already knows.
Why this is high-leverage
Alerts without mappings say "X changed on the vendor API." Alerts with mappings say "X changed, which affects billing-service, owned by Sam." The second version is one Slack message instead of a triage thread.
For multi-team orgs, mappings are also how you keep alerts targeted. Without them, every change goes to one channel and someone has to figure out who cares. With them, changes route to the team that owns the affected service.
When in doubt, over-map
A mapping that's slightly too broad (whole API mapped to one service when only part is used) costs you nothing — alerts still fire correctly, you just get a few extra mentions of an unrelated service.
A missing mapping costs you the targeting benefit. If you're not sure whether a service uses an endpoint, map it anyway. You can refine later.
Mappings and severity routing interact
Default routing is org-level (everything goes to the org's channels). Mappings let you layer per-service routing on top — this service's owners get a private DM, that service's changes always route to a specific channel.
Set this up at the mapping level, not the integration level, when you want different parts of the same API to route differently.