Keep Knack task records current from Notion
Update a task in Notion and let Notis refresh its corresponding Knack record, helping your team see the latest progress.
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
Update object record
Tool to update an existing record in a specific Knack object. Use when you need to modify field values in an existing record. Only fields provided in the request will be updated; all other fields remain unchanged.
Why this helps
Status updates scattered across tools force founders to remember where each change also needs to be recorded.
- Reflect task property changes in Knack without a second update.
- Reduce stale status information across systems.
- Spend less attention on keeping records aligned.
Setup
Build it in a few focused steps.
- 1Connect Notion and Knack to Notis once through the portal.
- 2Create an automation in the portal or tell Notis your goal in a connected channel.
- 3In one instruction, ask Notis to update the matching Knack record when a Notion task's status or other relevant properties change.
- 4Select Page Properties Updated for the relevant Notion data source and choose a run-report channel.
- 5Change one real task property and check that its Knack record is updated.
Questions about this workflow
Can this react to property changes only?
Yes. Use the Page Properties Updated trigger for the task data source.
Will unrelated Knack fields be overwritten?
Ask Notis to update only the relevant matching record details in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Knack. A trigger fires from one place; an action lands in another.
Notion triggers
Knack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create object record
Tool to create a new record in a specific Knack object. Use when you need to add new data to a Knack database object. Requires object-based API key authentication.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create View Record
Tool to create a new record through a form view in Knack. Use when you need to add a record to a Knack object using a form view interface. Only fields that exist in the form will be used, and any record rules configured on the form will be triggered.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Object Record
Tool to delete a single record from a specific Knack object by its ID. Use when you need to permanently remove a record from an object. This action is permanent and cannot be undone. Requires API key authentication (X-Knack-Application-Id and X-Knack-REST-API-KEY headers).
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 View Record
Tool to delete a record through a view that contains a delete link. Works with tables, lists, searches, calendars, and details views. This operation is permanent and cannot be undone. Use only after confirming the correct scene_key, view_key, and record_id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Object Record
Tool to retrieve a single record by its ID from a specific Knack object. Returns the complete record with all field values in both formatted and raw formats. Use this for object-based access which requires API key authentication.
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 Object Records
Tool to retrieve multiple records from a specific Knack object (table). Returns up to 1000 records per page with pagination support. Use this for object-based access which requires API key authentication and provides full access to all fields and records. Supports filtering by field values and sorting by field keys.
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.
List View Records
Tool to retrieve multiple records from a specific Knack view (tables, lists, searches, calendars). Use when you need to fetch data from a view with pagination support. Returns only fields included in the view configuration.
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.
Update object record
Tool to update an existing record in a specific Knack object. Use when you need to modify field values in an existing record. Only fields provided in the request will be updated; all other fields remain unchanged.
Connect any two apps with Notis in the middle.
Notion and Knack, 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 Knack.