Connect Slackbot to Agent mail
When something happens in Slackbot, Notis takes the next step in Agent mail. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Slackbot to Agent mail
Email unanswered Slack channel questions
When a channel question needs specialist help, send a focused email with the context and a clear response request.
Turn Slack DMs into client follow-up emails
When a DM contains a client commitment, send a polished follow-up email draft or message through Agent mail.
Check the inbox before replying to Slack threads
When a channel message asks for an email update, search Agent mail for relevant threads and return the latest status.
Triage inbox requests from Slack DMs
When a teammate sends a DM asking what needs attention, list relevant Agent mail messages and return a prioritized view.
Send email after an approval reaction
When an approved Slack message receives a selected reaction, send the requested email through Agent mail.
Email when a Slack approval is withdrawn
When an approval reaction is removed, notify the relevant recipient by email that the request is paused or cancelled.
Send a welcome email for new Slack channels
When a Slack channel is created, send an onboarding email with purpose, links, and first steps for its members.
Retrieve the exact email behind a Slack request
When a Slack channel message references an email, fetch the specific Agent mail message and return its full details.
Fetch email evidence requested in a DM
When a direct message asks for proof or wording from an email, retrieve the specific Agent mail message and return it.
Supported Triggers and Actions
Notis builds workflows that link Slackbot to Agent mail. A trigger fires from one place; an action lands in another.
Slackbot triggers
Agent mail actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Message
Get a specific message from an agentmail inbox
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Messages
List messages from an agentmail inbox
New Channel Created Trigger
Triggered when a new channel is created in Slack.
Send Email
Send an email using agentmail api
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
Message Reaction Removed
Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.
Reaction Added Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Slackbot and Agent mail
Connect any two apps with Notis in the middle.
Slackbot and Agent mail, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Agent mail.