See launch assets as soon as a launch page begins
Start launch planning with a quick inventory of the assets already collected in Backendless, so you can see what is ready and what is missing.
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
Directory Listing
Tool to retrieve a listing of files and directories at a given path. use when browsing or filtering file storage directories.
Why this helps
Launch work can stall when asset availability is unclear and someone must browse folders manually.
- Bring existing assets into launch planning.
- Spot missing materials earlier.
- Avoid manually scanning a storage folder.
Setup
Build it in a few focused steps.
- 1Connect Notion and Backendless to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to inventory launch assets.
- 3Write one plain-language instruction asking Notis to list files in the Backendless launch directory associated with the new page and summarize the available assets.
- 4Select Page Created for the launch parent page and choose a channel for run reports.
- 5Create a test launch page and verify the listed assets match the folder.
Questions about this workflow
Does the folder have to be created already?
Yes. The instruction should point Notis to an existing Backendless asset directory.
Can the inventory call out missing assets?
Tell Notis which asset types are expected and ask it to flag any that are absent from the listing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Backendless. A trigger fires from one place; an action lands in another.
Notion triggers
Backendless actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Copy File
Tool to copy a file or directory within backendless file storage. use when duplicating files to a new location after verifying source and destination paths.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Directory
Tool to create a new directory at the specified path. use when you need to organize files under a new folder structure.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Backendless Hive
Tool to create a new hive. use when you need to provision a new hive resource before performing hive operations. example: create a hive named 'grocerystore'.
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 Backendless Timer
Tool to create a new timer with schedule and code. use when scheduling recurring or one-off tasks to run server-side logic after confirming parameters.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Directory
Tool to delete a directory at the specified path in backendless file storage. use when you need to remove folders after confirming the path.
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.
Delete File
Tool to delete a file at the specified path in backendless file storage. use after confirming the file's relative path and filename.
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.
Delete Backendless Timer
Tool to delete a backendless timer by name. use when you need to remove a scheduled timer after confirming its name.
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.
Directory Listing
Tool to retrieve a listing of files and directories at a given path. use when browsing or filtering file storage directories.
Connect any two apps with Notis in the middle.
Notion and Backendless, 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 Backendless.