Start each day with a focused priority check-in
Turn an unstructured start into one clear question about today's most important work, using current priorities from Notion as context.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Send Message
This tool allows sending a message through dailybot to either specific users or channels/rooms. the message can include markdown formatting.
Why this helps
Choosing what to focus on can take longer when priorities are split across pages and check-ins are inconsistent.
- Create a predictable moment to state today's focus.
- Bring shared priorities into a familiar team conversation.
- Reduce time spent figuring out what to ask in a standup.
Setup
Build it in a few focused steps.
- 1Connect Notion and Dailybot to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to run a recurring priority check-in using Notion context.
- 3Give one plain-language instruction describing the Dailybot message and select a recurring schedule as the trigger.
- 4Choose a channel for run reports and test with a current priority before relying on the schedule.
Questions about this workflow
Does this trigger come from a Notion event?
No. It uses a Notis recurring schedule and can consult Notion as context when it runs.
Can I choose when it runs?
Yes. Select the recurring schedule that fits the team's working rhythm when creating the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Dailybot. A trigger fires from one place; an action lands in another.
Notion triggers
Dailybot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Find User by UUID
This tool allows you to find and retrieve information about a specific user in dailybot. it uses the provided user uuid to lookup the user and returns detailed information including the user's uuid, full name, image, username, occupation, birth date, chat platform data, and organization details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Find Workflow by Name
This tool allows users to find a specific workflow within dailybot by providing the workflow name. it returns detailed information including the workflow id, workflow name, workflow status, workflow type, created at, and updated at. it is especially useful to locate a workflow before running or modifying it.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get All Users
This tool retrieves a list of all users within the organization from dailybot. it doesn't require any input parameters other than authentication. the returned json contains user details including uuid, active status, full name, and organizational data.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Get Workflows List
This tool retrieves a list of all workflows that the authenticated user has access to in dailybot. it can be executed independently with only the authentication required, and it supports optional pagination parameters (page, per page) to refine the response.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Give Kudos to Users
This tool allows giving kudos to one or multiple users in dailybot. kudos can be given either on behalf of dailybot or the api key owner.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Send Message
This tool allows sending a message through dailybot to either specific users or channels/rooms. the message can include markdown formatting.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion and Dailybot, 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 Dailybot.