Make repository access questions easier to answer
A focused access thread should not require a detour through several tools. Ask Notis to retrieve the organization's visible Codacy repositories when that discussion gets a new comment.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Get Organization Repositories
Tool to list all repositories under a specific organization and provider. use when you need to enumerate organization-scoped repositories.
Why this helps
Repository access questions can sit unresolved while someone searches for an up-to-date inventory.
- Attach repository context to focused discussions.
- Speed up access clarification.
- Keep follow-up tied to the source conversation.
Setup
Build it in a few focused steps.
- 1Connect Notion and Codacy to Notis once.
- 2Create an automation through the portal or by asking Notis.
- 3Write one plain-language instruction to list the relevant organization's repositories when the designated access thread receives a comment.
- 4Select the Notion New Comment trigger and specify the intended page or block context in the setup.
- 5Choose a channel for run reports and test with one real access question.
Questions about this workflow
Can this be limited to one discussion?
The trigger supports a specified Notion block or page. Select the intended discussion context when setting up the trigger.
Can the workflow grant access?
No. It only retrieves the repository list.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Codacy. A trigger fires from one place; an action lands in another.
Notion triggers
Codacy actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create API Token
Tool to create a new api token for the authenticated user's account. use after authenticating when you need to generate a fresh token for integrations.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete API Token
Tool to delete a specific api token from the authenticated user's account. use after confirming the token id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Account Details
Tool to retrieve details of the authenticated user's account. use when confirming authentication before user-level operations.
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 Organization Repositories
Tool to list all repositories under a specific organization and provider. use when you need to enumerate organization-scoped repositories.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get User Organizations
Tool to list all organizations the authenticated user belongs to. use after authenticating and need to discover accessible organizations.
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.
List Projects
Tool to list all projects accessible to the authenticated user. use when you need a list of repositories after confirming api token validity.
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 Codacy, 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 Codacy.