Carry customer profile details from Notion to Canny
Record customer context once and let Notis keep the corresponding Canny profile ready for feedback activity.
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
Create or Update User
Tool to create or update a user in canny. use when you need to provision a new user or synchronize updates to an existing user profile. example: "create or update user with email user@example.com"
Why this helps
Manually creating a feedback profile after documenting a customer adds another opportunity to forget or repeat work.
- Avoid duplicate customer data entry.
- Make customer feedback easier to associate with a profile.
- Reduce setup steps when a new customer is documented.
Setup
Build it in a few focused steps.
- 1Connect Notion and Canny to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Explain which new Notion customer profiles should create or update a Canny user and what profile context to use.
- 4Choose Page Created, select a run-report channel, and test with one real customer profile.
Questions about this workflow
Can it update a profile that already exists?
Yes. The Canny action can create or update a user. Tell Notis how to identify the customer.
Should I include sensitive customer notes?
Include only profile details that belong in Canny and are appropriate for your feedback workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Canny. A trigger fires from one place; an action lands in another.
Notion triggers
Canny actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Post Tag
Tool to add a tag to a specific post. use when you need to categorize or group content by applying an existing tag.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete User
Tool to delete a user and their comments and votes. use when you need to fully remove a user's account and all associated data (e.g., gdpr compliance).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Change Post Status
Tool to change a post's status. use when you need to update a post's workflow stage and optionally notify voters.
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.
Create Changelog Entry
Tool to create and optionally publish a new changelog entry. use when you need to add a product update record, control publish timing, and notify users. example: "create changelog entry titled 'version 1.2' with details '...' and publish immediately.".
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Comment
Tool to create a new comment on a post. use when you have the authorid and postid and want to submit feedback or replies.
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.
Create or Update User
Tool to create or update a user in canny. use when you need to provision a new user or synchronize updates to an existing user profile. example: "create or update user with email user@example.com"
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.
Create Post
Tool to create a new post on a board. use when you have the boardid and userid and need to submit new feedback.
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.
Create Tag
Tool to create a new tag. use when you have the boardid and tag name and need to categorize posts.
Connect any two apps with Notis in the middle.
Notion and Canny, 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 Canny.