Keep corrected delivery addresses from getting lost
Record the correction in Notion and let Notis update the matching Detrack delivery.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Edit Delivery
Tool to edit specific deliveries by date and d.o. number. use after confirming delivery identifiers to update their details (max 100 per call).
Why this helps
Address changes are especially easy to miss when the same correction must be repeated in another system.
- Reduce repeated correction work.
- Make the Notion change a cue to update dispatch details.
- Lower the chance of working from an outdated address.
Setup
Build it in a few focused steps.
- 1Connect Notion and Detrack to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3In one prompt, ask Notis to find the matching Detrack delivery and edit its address when a Notion delivery record is corrected.
- 4Choose the Notion Page Properties Updated trigger and a channel for run reports.
- 5Test with one real correction and verify the intended Detrack delivery was edited.
Questions about this workflow
What if several Detrack jobs match?
Tell Notis in the prompt to report ambiguous matches for review before editing.
Does Notis need a field map?
No. Describe in plain language how to identify the job and what correction to apply.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Detrack. A trigger fires from one place; an action lands in another.
Notion triggers
Detrack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Collection
Tool to add a new collection in detrack. use after gathering all necessary collection details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete All Collections
Tool to delete all collections in the account. use when you need to purge every collection for a specific date after confirmation.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete All Deliveries
Tool to delete all deliveries for a specific date. use when you need to purge deliveries in bulk before scheduling new ones.
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 Delivery
Tool to delete one or more deliveries by date and d.o. number. use after confirming delivery entries to avoid accidental data loss (max 100 items per call).
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Edit Delivery
Tool to edit specific deliveries by date and d.o. number. use after confirming delivery identifiers to update their details (max 100 per call).
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 Jobs
Tool to list all jobs with optional filters and pagination. use when you need to retrieve jobs by date, status, country, or other criteria.
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.
Search
Tool to search for deliveries, collections, or vehicles. use after defining search criteria to retrieve matching jobs.
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.
View All Collections
Tool to view all collection jobs in detrack. use when you need to retrieve every collection job currently stored.
Connect any two apps with Notis in the middle.
Notion and Detrack, 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 Detrack.