Know your repository options for new technical work
A new Notion data source can prompt a quick list of the repositories Devin is able to research for your team.
Trigger
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.
Action
List available repos
List all repositories available to query with your Devin account. Only available in private mode (via devin.ai endpoints).
Why this helps
New technical workflows often arrive without a clear link to the repository context people will need to investigate them.
- Make repository availability visible early in workflow setup.
- Avoid repeatedly asking which codebases can be researched.
- Provide a concrete repository list for follow-up planning.
Setup
Build it in a few focused steps.
- 1Connect Notion and Devin MCP to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Give one instruction asking Devin to list all repositories available to query when a new technical data source is created.
- 4Select Notion's Data Source Created trigger and choose a channel for run reports.
- 5Test with one real data source creation and review the returned repository list.
Questions about this workflow
Will a data source creation always mean a technical workflow?
No. Use the instruction to focus on technical sources, or scope the automation's use to workspaces where new data sources are engineering-related.
What access is required?
The Devin MCP repository-list action is available in private mode via devin.ai endpoints.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Devin MCP. A trigger fires from one place; an action lands in another.
Notion triggers
Devin MCP actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Ask question
Ask any question about a GitHub repository and get an AI-powered, context-grounded response. Args: repoName: GitHub repository or list of repositories (max 10) in owner/repo format question: The question to ask about the repository
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List available repos
List all repositories available to query with your Devin account. Only available in private mode (via devin.ai endpoints).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Read wiki contents
View documentation about a GitHub repository. Args: repoName: GitHub repository in owner/repo format (e.g. "facebook/react")
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.
Read wiki structure
Get a list of documentation topics for a GitHub repository. Args: repoName: GitHub repository in owner/repo format (e.g. "facebook/react")
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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 Devin MCP, 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 Devin MCP.