Incident Management Agent
Automatically post Slack incident updates to Notion, keeping teams aligned without manual overhead.
Overview
This agent monitors Slack incident channels, summarizes key updates, and posts structured reports to Notion. It reduces manual effort, ensures consistent documentation, and keeps stakeholders informed with real-time updates.
You can also extend this workflow to integrate Jira or PagerDuty, or refine it to match your team's incident response playbook.
Tools used by this agent
Slack: Gathers incident-related messages
Notion: Stores incident status, summaries, and updates
How does this agent work?
Use the /incident-management* command to trigger the agent in Slack. Then, the agent:
Creates a new Slack channel based on the description provided with the slash command.
Invites itself and the user who triggered the command into that new channel.
Collects Slack messages from the incident channel.
Checks Notion to see if an incident page already exists. If not, it creates one.
Analyzes messages and generates structured summaries:
Detailed incident overview
Technical summary for engineering
Support-friendly update for external communications
Updates the Notion page with the current status and metadata, such as severity.
Determines whether to notify leadership based on incident severity and message content.
Handles resolution events and updates the Notion page with closure summaries.
*The /command can be customized within the Slack app
Get started fast. Clone this agent template in Postman
Use TemplateHow to use this template
This agent requires the following configurations to function
Slack | slack_bot_token |
Notion | notion_api_key notion_database_id |
Set up the template
To set up the template, do the following:
Clone the agent template from the Flows workspace.
Set up Slack:
Create a Slack app.
Get your Slack token and make sure it has the following permissions:
channels:history
channels:manage
channels:read
chat:write
commands
pins:write
users:read
Get the Slack channel ID.
Enable event subscriptions for
message.channels
.
Set up Notion:
Create a Notion database with the following fields:
Name: Title (default)
Incident Date: Date
Status: Select (options: Not started, In progress, Done)
Severity Level: Select (options: Critical, High, Medium, Pending)
Create a new Notion integration.
Make sure to enable the connection with your application on the database page.
Add the following credentials to the Configurations panel to the right of the flow:
slack_bot_token
notion_api_key
notion_database_id
Deploy the agent to the Postman cloud. Copy the
action_url
from the deployment output.Create a slash command, such as
/incident-management
, pointing to the deployed action URL.In Slack, use your slash command to trigger the agent.
Review the output:
Check Notion and Slack for the incident summary
Customize alert logic, summary formatting, or stakeholder notifications as needed
Popular Templates
Prepare for customer meetings
Gathers support, deal, and calendar data to deliver a daily Slack brief before calls.
Route urgent tickets automatically
Detects severity of incoming tickets and escalates them to PagerDuty, Slack, or email.
Summarize and analyze industry news
Pulls and analyzes news articles from APIs, then sends a daily summary straight to Slack.
Score GitHub issues by urgency
Analyzes comments and sentiment to summarize GitHub issues and flag those needing triage.