Slack integration
Deal with outages in Slack, not just hear about them
InfraNest watches your sites, servers, domains and certificates, and posts what goes wrong to the Slack channel you pick. Whoever sees it first can acknowledge it, silence it or file it as an issue from the alert itself, and the same message updates itself when the problem is over.
On every plan, one chat on Free · Add to Slack in one click · Posts only to the channels you pick
- Acknowledge, silence or add a note from the alert
- File the incident as an issue in one click
- One message per outage, updated when it is over
- Check status and pause your alerts without leaving Slack
One incident, not several: the effects are grouped under the cause.
- 2:33 PMDeploy of northwyndr/storefront (f19e6c7)Deploys
- 2:36 PMCheckout flow failed: Checkout returning 503Monitoring
- 2:36 PMAPI health failed too, grouped under this incidentMonitoring
- 2:36 PMAlert sent to Ops team — email, On-call — critical only, #infra-alertsNotifications
InfraNestApp14:36
Checkout flow is DOWN
Acknowledge, silence or add a note without leaving Slack
An alert in Slack carries the buttons that make sense right now. While nobody is on it, Acknowledge tells the team you have it and stops the repeat alerts. While it is open, Silence 1 h quiets the monitor for an hour. Once someone is on it, Add a note tells the team what is being done, and Post a status update writes the public update for your status page, with a review first because it is public. The alert changes for everyone in the channel, so nobody chases a problem someone already has.
- The alert says who is on it, for everyone in the channel
- Notes stay with your team and never reach your status page
- Every button acts as the person who pressed it, with their own role
- Status updates when the monitor is on one of your status pages
InfraNestApp15:01
Marketing site is DOWN
Acknowledged by Sam at 15:05
Turn the alert into an issue with one click
With GitHub, Jira or Linear connected, an incident alert carries Create issue until the incident has an issue. Pressing it files the incident in your tracker, in the place your Issues for Incidents setting uses, in the name of whoever pressed it, and says so in the alert’s thread. The button then becomes the issue, so anyone can open it from the alert. When there is a choice only that person can make, such as which tracker, it sends them to the incident in InfraNest instead.
- One issue, however many times the button is pressed
- The thread says who filed it and which issue it became
- Filed in the name of the person who pressed it
- Works with GitHub, Jira and Linear
InfraNestApp15:01
Marketing site is DOWN
Acknowledged by Sam at 15:05
InfraNest15:07
🎫 Sam filed this as infra#86
One message per outage, and it updates itself
A “down” message followed much later by an “up” message nobody can match to it is how a channel loses track. When the problem is over, InfraNest edits the original alert to say so and how long it lasted, and posts the recovery as a reply in its thread. Notes and public status updates written on the incident, in InfraNest or in another connected tool, land in the same thread, so the people following it in Slack see the whole story without opening anything else.
- “Resolved after …” on the alert itself, the recovery in its thread
- Notes and status updates follow the incident into the thread
- The alert that opens an outage can ping @here, a user group or whoever is on call
- Updates and recoveries never ping anyone — see alert routing
InfraNestApp15:01
✅ Resolved after 15 min
Marketing site is DOWN
InfraNest15:07
🎫 Sam filed this as infra#86
InfraNest15:16
Marketing site is UP
Ask what needs you, or pause your alerts, with /infranest
Type /infranest status to see what needs you right now, or add a name to see how one monitor, domain or server is doing. /infranest pause quiets your own alerts for an hour, until tomorrow or for a week, and /infranest back turns them on again. /infranest update lists the open incidents you can post a status update on, and /infranest run starts one of your manual automations after a confirmation. Only you see the answers.
- Look up one monitor, domain or server by name
- Paste a link to one and the channel sees its state and who is on it
- Save any message as a note on an incident from its menu
- Only what your role in InfraNest may see is found
InfraNestApp
Only visible to you
- /infranest status what needs you right now
- /infranest status api.example.com how one monitor, domain or server is doing
- /infranest update post a status update on an open incident
- /infranest run run one of your manual automations
- /infranest pause pause your own alerts for an hour (or
tomorrow,week) - /infranest back turn them on again
- /infranest link link your Slack to your InfraNest account
Your own corner of InfraNest inside Slack
InfraNest’s Home tab in Slack shows whether your alerts are paused, with buttons to change that, what is open right now and whether anyone is on it, who is on call when PagerDuty is connected, and which channel gets which alerts. Each person can also have their own alerts sent to them as direct messages, with buttons that work only for them, and the team’s list of what needs attention can be posted to a channel.
- Pause your alerts for an hour or until tomorrow in one click
- Open incidents, and whether anyone is on them
- Your own alerts as direct messages, updated when they are resolved
- The team’s “needs you” list, posted to a channel
InfraNestLinked to Sam Okoye in InfraNest.
Northwind Cloud
Your alerts
On. Your own alerts reach you as usual.
Open incidents
Checkout returning 503 · Northwind Cloud
Nobody is on it yet
On call now
Platform — production: Priya Raghunathan
Channels in this workspace
#infra-alerts → Northwind Cloud
Bring your alerts into Slack
On every plan, with one chat destination on Free. Add InfraNest to Slack, pick a channel and send a test alert.
Connect Slack in about two minutes
Choose Connect, allow InfraNest in your Slack workspace, and pick the channel. InfraNest welcomes you in Slack, links you to your account, and lets you send a test alert from there. Rather paste an incoming webhook? Alerts still arrive, but without buttons and without updating themselves.
- 1
Connect your workspace
Links InfraNest to Slack so alerts can post and update themselves; go to Integrations → Slack, select Connect, then Allow.
- 2
Pick a channel
Sends alerts to the team that needs them; choose the channel in InfraNest, and add more later with Add channel.
- 3
Send a test
Confirms the alert lands where you expect; select Send a test next to the new destination.
That’s it — Slack is connected.
Full setup guideSet up with AI
I use Slack, and I want to connect it to InfraNest (infranest.io) — it manages domains, DNS, servers and certificates across providers. InfraNest asks for: Sign in with Slack, or a webhook URL. Walk me through creating that in Slack: where each setting is in the current interface, whether a read-only option exists, and how to check it works before I paste it in.
Often connected together
Questions about the Slack integration
#Can people act on alerts without an InfraNest login?
They need an InfraNest account and to link it to Slack once, which happens automatically the first time they press a button there. After that, buttons act as them, using whatever their InfraNest role allows.
#What happens if we remove InfraNest from our workspace or archive the channel?
The destination is marked as needing attention right away and you're told by email. Add InfraNest to Slack again or pick another channel to pick up where you left off.
#Can InfraNest file issues or just alert us?
If you've connected GitHub, Jira or Linear, the Create issue button under an open incident files it in your tracker and posts the link back in the thread. Without a tracker connected, you still get the alert, buttons and status updates.
#Does the webhook option work the same as the full connection?
Alerts arrive the same way, but a webhook can't update itself when a problem resolves, so the recovery shows up as a new message naming the alert it closes instead of updating it in place.
#What do I need before connecting Slack?
You need permission to add an app to your Slack workspace (or to create an incoming webhook if you'd rather not): setup guide.
Let the channel that hears about it deal with it
Create your account, add InfraNest to Slack in one click, and send a test alert to the channel you pick.
Free plan · No credit card required · Set up in minutes