Carry variant attributes from planning into Cloudcart
Record a custom attribute in your variant plan and let Notis apply it to the corresponding Cloudcart variant.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Create Variant Parameter
Tool to create a new variant parameter for a product variant. use when you need to add custom attributes (e.g., color, size) after a variant is created.
Why this helps
Product attributes can be missed when they are captured during planning but entered later by hand.
- Keep product attributes connected to their planning context.
- Reduce repetitive catalog entry.
- Make detailed product setup less dependent on memory.
Setup
Build it in a few focused steps.
- 1Connect Notion and Cloudcart to Notis once in the portal.
- 2Create an automation that adds approved custom attributes to the matching Cloudcart variant when its Notion page is updated.
- 3Select Page Updated for the specific parent page containing those plans and choose a report channel.
- 4Test with one variant and one real custom attribute.
Questions about this workflow
What does Page Updated watch?
It triggers when a block within the specified Notion page is updated.
How should the automation identify the variant?
Describe the variant's matching identifier and the attribute details in the plain-language prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cloudcart. A trigger fires from one place; an action lands in another.
Notion triggers
Cloudcart actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add to Cart
Tool to add an item to the cart. use after confirming a product selection with desired quantity.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Clear Cart
Tool to remove all items from the specified cart. use when you need to empty the cart before adding new items or starting over.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Category
Tool to create a new category. use when you need to add organizational structure to your product catalog.
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 Customer
Tool to create a new customer in cloudcart. use when you need to register a new customer profile. provide validated customer details (name, email, and password).
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Order
Tool to create a new order. use after assembling customer id, cart items, and optional addresses/payment info.
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 Product
Tool to create a new product. use when you have all details and want to add it to cloudcart.
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 Variant
Tool to create a new product variant for a given product. use when you need to add a variant with specific sku, price, and options.
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 Variant Option
Tool to create a new variant option for a specific product variant. use when you need to add an option (e.g., 'large') with an optional price adjustment to an existing variant.
Connect any two apps with Notis in the middle.
Notion and Cloudcart, 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 Cloudcart.