Alerts and actions,
in the tools you already use.
Each integration is both a destination for notifications and an action AI can choose and run. Send escalations to chat, records to kintone, and events to your own systems by webhook.
- Supports 10 destinations
- Customize the message for each destination
- Webhooks can be signed with HMAC-SHA256
Integrations
Slack
Notify a Slack channel
Teams
Notify a Teams channel
Google Chat
Notify a Google Chat space
Discord
Notify a Discord channel
LINE WORKS
Notify a LINE WORKS chat room
LINE
Send a message from a LINE Official Account
Chatwork
Post to a Chatwork room
kintone
Add a record to a kintone app
Send an email to a specified address
Webhook
Send JSON to any URL
Sound familiar?
Monitoring alerts are buried in emails no one reads
Every anomaly means creating tickets and records by hand
Each destination needs different information
Choose
where alerts land.
For notifications and actions alike
The same integration can be registered both as an incident notification destination and as an action AI proposes.
Messages tailored per destination
Use placeholders such as the title, body, incident page URL, and severity to write messages suited to each destination.
Approval requests arrive, too
When an action needs approval, the notification makes that clear.
Credentials stored encrypted
Integration tokens are stored encrypted and decrypted only when sending. They never appear on screen or in API responses.
Supported destinations
Register them from either notification settings or actions.
Chat
Posts to channels or rooms in Slack, Discord, LINE WORKS, and Chatwork.
Records
Adds records to a kintone app.
Microsoft Teams and Google Chat
Posts to Teams channels and Google Chat spaces. Teams receives messages through a workflow webhook.
Email and LINE
Sends email to the addresses you specify, and messages from a LINE Official Account.
Webhook
Sends JSON to any URL. Set a secret and the body is signed with HMAC-SHA256.
Context placeholders
Placeholders can also include the severity and event type (incident.opened / connection.unreachable, etc.).
Set up in 3 steps
All you need is a database connection string or an account connection. Nothing to install on your servers.
- STEP 1
Choose a destination
Pick the destination you want from the integrations list in notification settings.
- STEP 2
Set the target and message
Set the target, such as a channel or database, and a message using placeholders.
- STEP 3
Send a test
Send a test notification to see how it arrives.
Who it's for
- You handle incidents in a chat tool
- You want to keep incident records in kintone
- Your team works in Microsoft Teams or Google Chat
- You want to bring notifications into your own systems
- You want to tailor what each destination receives
Use cases
Escalation
Critical anomalies to chat
Send incident notifications to a Slack channel with the incident page URL in the message, so details are one click away.
Records
Keep incident records in kintone
Register recording to kintone as an action, and AI proposes it when the situation fits; once approved, the record is created.
Related features
Approval-gated actions
AI proposes only actions you've registered in advance, and runs them when a person approves.
Automatic investigation
When something looks abnormal, AI digs into the real data to trace the cause, and records its conclusion and evidence.
Ask in chat
Ask "Have orders dropped since last week?" and AI answers by checking the real data.
Send alerts where
your team already is.
Integration credentials are stored encrypted, and a test send lets you check delivery ahead of time.