Make a known generated asset easier to retrieve
When a page moves forward, retrieve a known asset's details so its file link is easy to bring into the next step.
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
Get Asset
Tool to retrieve a specific asset by its id. use when you need to fetch metadata or download url of an existing asset after its generation.
Why this helps
A generated file's ID or download link may be separated from the page where a founder needs it.
- Look up a known asset as part of a relevant page change.
- Reduce manual switching to retrieve file details.
- Make the handoff from a page update to a generated file smoother.
Setup
Build it in a few focused steps.
- 1Connect Notion and Cloudlayer to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally to retrieve a known asset after a relevant property update.
- 3Write one plain-language instruction explaining which asset to retrieve and how to share the result.
- 4Select the Notion Page Properties Updated trigger and choose a channel for run reports.
- 5Test with a real property update and a valid asset ID.
Questions about this workflow
Does this create a new asset?
No. Get Asset retrieves metadata or a download URL for an existing asset by its ID.
Where should the asset ID come from?
Include the relevant ID or its source context in the instruction available to Notis, then validate the lookup with a real example.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cloudlayer. A trigger fires from one place; an action lands in another.
Notion triggers
Cloudlayer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Storage
Tool to add a new user storage configuration. use when you need to attach an external bucket or container for file storage.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Asset
Tool to retrieve a specific asset by its id. use when you need to fetch metadata or download url of an existing asset after its generation.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get API Status
Tool to test api reachability. use when checking if the cloudlayer api is available.
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.
HTML to Image
Tool to convert base64-encoded html to an image. use when you need to render raw html or a url into png, jpeg, or webp after content load.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Convert HTML to PDF
Tool to convert html or a public url into a pdf document. use when you need programmatic pdf generation from html content.
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 Assets
Tool to list the ten most recent assets. use when you need to retrieve your latest cloudlayer assets.
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 Storage Configurations
Tool to retrieve a list of all storage configurations. use after authenticating to cloudlayer to view your account's storage settings.
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.
Convert URL to Image
Tool to convert a webpage url to an image. use when dynamic screenshot parameters are needed.
Connect any two apps with Notis in the middle.
Notion and Cloudlayer, 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 Cloudlayer.