Never Over-Promise Again: Campaign Launch Sync
Add a campaign page in Notion. Instantly see if your design team has capacity. No more scrambling to find out about bottlenecks after the deadline has been promised.
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 API info
Tool to retrieve api root information. use when you need to discover the api's description and version details.
Why this helps
You map out campaigns in Notion but don't discover capacity issues until after clients are expecting delivery.
- Catch production conflicts before they become client issues
- Stop switching between Notion and Adrapid to check status
- Prevent over-scheduling that leads to burnout
Setup
Build it in a few focused steps.
- 1Connect your Notion workspace and Adrapid account to Notis through the portal (single setup)
- 2Open Automations and click New Automation, then tell Notis: 'When I create a campaign page in Notion, check my Adrapid production capacity'
- 3Notis configures the workflow automatically from your plain-language instruction
- 4Select 'Page Created' as the trigger and choose your Slack or email channel for alerts
- 5Test by creating a sample campaign page and confirm you receive the Adrapid capacity check in your channel
Questions about this workflow
What if the production capacity is at max?
Notis alerts you immediately in your chosen channel with the full status, so you can adjust timelines or scope before making promises.
Does this work for all campaign types?
Yes - every new campaign page triggers the check. Use Notion properties to flag priority, budget, or complexity, and Notis learns what details matter most to your team.
How fast is the capacity check?
Seconds. Notis retrieves live data from Adrapid so you have instant visibility.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Adrapid. A trigger fires from one place; an action lands in another.
Notion triggers
Adrapid actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get API info
Tool to retrieve api root information. use when you need to discover the api's description and version details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get user and API info
Tool to get user account and api information. use when you need to retrieve authenticated user details and api versions.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Banners
Tool to list all banners and their statuses. use when you need to retrieve banners after creation or to audit existing banners. ensure you apply filters to narrow down results (e.g., status='ready').
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.
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 Adrapid, 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 Adrapid.