Turn Slack blockers into a Dailybot check-in
When someone shares a blocker in a Slack channel, send them a concise Dailybot message prompting them to name the next step or help they need.
Connect Slack to Dailybot
When something happens in Slack, Notis takes the next step in Dailybot. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Triggers when a new channel is created.
Do this · Action
Retrieves a DailyBot user's details by UUID.
Examples
Ways Notis can move work from Slack to Dailybot
Recognize shipped work with Dailybot kudos
When a teammate reacts to a Slack update with a chosen recognition emoji, give kudos to the message author in Dailybot.
Carry Slack decisions into Dailybot
When a channel message clearly records a team decision, send a short Dailybot message to the relevant group summarizing it for visibility.
Clarify delegated work from Slack DMs
When a Slack DM clearly delegates work, send the recipient a Dailybot message prompting them to confirm the expected outcome and timing if either is unclear.
Gather weekly wins from Slack
When a teammate shares a clear win in a Slack channel, send a Dailybot message inviting the team to include it in their weekly reflection.
Turn a Slack help reaction into a check-in
When a teammate reacts to a Slack message with your chosen help signal, send the author a Dailybot message asking what support would be useful.
Prompt meeting follow-up owners in Dailybot
When a Slack channel message lists meeting follow-ups with named owners, message those people in Dailybot with a concise reminder of their stated next steps.
Recheck a Slack item after its signal is removed
When a chosen status reaction is removed from a Slack message, send the author a Dailybot prompt to confirm whether the item still needs attention.
Welcome members when a Slack channel opens
When a new Slack channel is created, send a Dailybot room message that welcomes its purpose and prompts the creator to share any working agreements.
Supported Triggers and Actions
Notis builds workflows that link Slack to Dailybot. A trigger fires from one place; an action lands in another.
Slack triggers
Dailybot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
TriggerScheduled
Find User by UUID
Retrieves a DailyBot user's details by UUID.
ActionInstant
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
TriggerInstant
Create Check-in
Creates a recurring team check-in from a template, with a schedule, reminders and reporting channels.
ActionInstant
New Channel Created Trigger
Triggers when a new channel is created.
TriggerInstant
Find Workflow by Name
Finds workflows by name on one page of DailyBot results.
ActionInstant
Channel Message Received
Triggers when a message is posted in a channel, excluding direct messages.
TriggerInstant
Get All Users
Retrieves one page of users in your DailyBot organization.
ActionInstant
Direct Message Received
Triggers when a new direct message, including a thread reply, is sent to a user.
TriggerInstant
Give Kudos to Users
Gives kudos to one or more DailyBot users.
ActionInstant
Message Reaction Added
Triggers when a reaction is added to a message.
TriggerInstant
Send Message
Sends a formatted message to users, teams, or channels in Dailybot.
ActionInstant
Message Reaction Removed
Triggers when a reaction is removed from a message.
TriggerInstant
New Bot Message Received Trigger
Triggers when a bot posts a new message in a channel.
TriggerInstant
Trigger Types
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 schedule (recurring or one-time), and a change in one of your Notis databases.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.
New Notion pageStripe chargeCalendar event
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.
Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used
Scheduled triggers
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Daily · 8:00Weekdays onlyOnce · Dec 13
Beta
Database triggers
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Row addedProperty editedValue > limit
Why AI automation
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.
Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use
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:
TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability
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
All12Manager5Telegram1Messages0WhatsApp2Email4Slack8
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.
Related pairs
More ways to connect Slack and Dailybot
Connect any two apps with Notis in the middle.
Slack and Dailybot, or any other combination from 1,500+ 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 Dailybot.