End the day knowing where to begin tomorrow
Close the mental tabs before you log off. Get a concise record of progress, loose ends, and tomorrow's first step.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Create Chat Completion
Tool to generate a chat-based completion for a conversation. Use when you have a list of prior messages and need the model’s next reply.
Why this helps
The workday ends with unfinished thoughts that keep resurfacing and make it harder to restart the next day.
- Capture progress while it is still easy to recall.
- Name unresolved items without trying to solve them all at once.
- Make tomorrow's restart more obvious.
Setup
Build it in a few focused steps.
- 1Connect Notion and Groqcloud to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Give one instruction asking Groqcloud to summarize the Notion context you specify as progress, open loops, and one first step for tomorrow.
- 4Choose a daily Notis cron schedule and select a channel for run reports.
- 5Test with a real day's notes and adjust the recap time or length.
Questions about this workflow
Can I choose when it runs?
Set the daily cron time and timezone to match your end-of-day routine.
Will it know which Notion pages to read?
Name the relevant Notion context in the prompt and keep the instruction within what your connected tools can access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Groqcloud. A trigger fires from one place; an action lands in another.
Notion triggers
Groqcloud actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Audio Translation
Tool to translate an audio file into English text. Use when you have a non-English recording and need an accurate English transcript. Use after confirming the file path.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Chat Completion
Tool to generate a chat-based completion for a conversation. Use when you have a list of prior messages and need the model’s next reply.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Retrieve Model
Tool to retrieve detailed information about a specific model. Use after listing models when you need metadata for a chosen model.
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.
List Models
Tool to list all available models. Use when you need to fetch supported models and their metadata.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List TTS Voices
Tool to retrieve available TTS voices for Groq PlayAI models. Use when you need to discover voice options before calling text-to-speech. Note: static list maintained manually; no live endpoint exists.
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.
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 Groqcloud, 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 Groqcloud.