Check branch availability from a new Notion page
Create a branch or handoff page in Notion and have Notis check the project's available branches in DeployHQ.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Get Repository Branches
Tool to view all available branches in the connected repository for a project. Use when you need to list repository branches and their commit hashes.
Why this helps
A planned branch name can be mistyped or not yet available, creating confusion during handoffs.
- Compare a documented branch against the branches DeployHQ can see.
- Catch availability mismatches before a handoff progresses.
- Keep branch checks out of a separate manual lookup.
Setup
Build it in a few focused steps.
- 1Connect Notion and DeployHQ to Notis once through the portal.
- 2Create an automation prompt asking Notis to identify the project from a new branch page, retrieve available branches, and report whether the documented branch appears.
- 3Select the Notion Page Created trigger and choose a channel for run reports.
- 4Test with one page describing a real branch.
Questions about this workflow
Does this create a repository branch?
No. It checks which branches are available in the connected repository.
Can it tell me the branch's latest commit?
The report can include the branch list returned by DeployHQ; use a separate latest revision check when you need a commit hash.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to DeployHQ. A trigger fires from one place; an action lands in another.
Notion triggers
DeployHQ actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Command
Tool to delete a command from a specified project. Use when you need to remove an SSH command from a project's configuration.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Project
Tool to delete a project from DeployHQ. Use when you need to permanently remove a project by its permalink or identifier.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Build Cache File
Tool to delete an existing build cache file from a project. Use when you need to remove a cached build artifact from the project's build cache storage.
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.
Delete Excluded File Rule
Tool to delete an existing excluded file rule from a project. Use when you need to remove an excluded file pattern from deployment configuration.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Server Group
Tool to delete a server group from a project using the DeployHQ API. Use when you need to remove a server group from deployment configuration.
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.
Delete Template
Tool to delete a template by its unique permalink. Use when you need to permanently remove a template from DeployHQ.
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.
Get Projects
Tool to retrieve all projects from DeployHQ account. Use when you need to list all available projects and their configurations.
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.
Get Project
Tool to view an existing project in DeployHQ. Use when you need to retrieve details about a specific project by its permalink or identifier.
Connect any two apps with Notis in the middle.
Notion and DeployHQ, 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 DeployHQ.