Review available Griptape assistants as workflows evolve
A new Notion view can mark a new way of working. Use it to prompt a check of the assistants available to support your growing workflow.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
List Assistants
Tool to list all assistants. Use after authenticating with Griptape Cloud to retrieve available assistants. Supports optional pagination.
Why this helps
As workspace routines grow, it becomes harder to remember what assistant support is already available.
- Make existing assistant options easier to revisit.
- Connect workspace changes with a review of available support.
- Reduce repeated checking when exploring a new routine.
Setup
Build it in a few focused steps.
- 1Connect Notion and Griptape to Notis once.
- 2Create an automation and say that Griptape should list assistants when a view is created.
- 3Choose the Notion View Created trigger.
- 4Choose a channel for run reports and test by creating a view.
Questions about this workflow
Does listing assistants run one of them?
No. This action retrieves the available assistants. Starting a run is a separate Griptape action.
What view details are available?
The trigger includes the view type and its parent, which can help provide context for the review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Griptape. A trigger fires from one place; an action lands in another.
Notion triggers
Griptape actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Assistant Creation
Tool to create a new assistant. Use when you need to register a uniquely named assistant in Griptape Cloud before initiating runs.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Assistants
Tool to list all assistants. Use after authenticating with Griptape Cloud to retrieve available assistants. Supports optional pagination.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Cancel Assistant Run
Tool to cancel an ongoing assistant run. Use when you need to stop a run prematurely after confirming the run ID is valid.
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.
Assistant Run Creation
Tool to initiate a new assistant run. Use when starting a fresh execution with custom arguments or resources after selecting the assistant.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Assistant Run Error Details
Tool to fetch detailed error information for a specific assistant run. Use after an assistant run has failed to inspect error details.
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.
Stream Assistant Run Events
Tool to stream real-time events for a specific Assistant run. Use after initiating a run to monitor its progress.
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.
List Assistant Runs
Tool to list all runs for a given assistant. Use when you need historical run executions for analysis after using the assistant.
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.
Assistant Run Logs Retrieval
Tool to retrieve logs generated during the execution of a specific assistant run. Use after confirming the run_id to fetch all log events once the run has completed.
Connect any two apps with Notis in the middle.
Notion and Griptape, 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 Griptape.