Retrieve CloudConvert webhook inventory from Notion
Request a webhook inventory in Notion and get the current CloudConvert list without losing your place in setup work.
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
List Webhooks
Tool to list all webhooks. use when you need to retrieve existing webhooks before managing or inspecting them.
Why this helps
When webhook setup is spread across tools, it is easy to forget what already exists.
- Create a clear request trail in Notion.
- Review the current webhook list before making setup changes.
- Avoid relying on memory about prior configuration.
Setup
Build it in a few focused steps.
- 1Connect Notion and CloudConvert to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to create one in plain language.
- 3Use one instruction to retrieve CloudConvert's existing webhooks whenever a new webhook-inventory request page is created.
- 4Choose the Notion Page Created trigger and the channel for run reports.
- 5Create one real inventory request and review the returned list.
Questions about this workflow
Does this create or modify a webhook?
No. It only retrieves the existing CloudConvert webhook list.
Where should I keep the request?
Create it as a new Notion page in the area where you track integration setup or maintenance.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cloudconvert. A trigger fires from one place; an action lands in another.
Notion triggers
Cloudconvert actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Export Google Cloud Storage Task
Tool to create a task to export files to a google cloud storage bucket. use after conversion when you need to store results directly into gcs. ensure service account credentials have the proper permissions.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Export S3 Task
Tool to create a task to export files to an amazon s3 bucket. use after conversion when you need to store results directly into s3. ensure aws credentials have s3:putobject (and putobjectacl if using non-default acl) permissions.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Webhook
Tool to create a new webhook. use when you need to receive event notifications into your system.
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 Webhook
Tool to delete a webhook by its id. use when you no longer need a webhook and want to remove it.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Supported Formats
Tool to list all supported conversion formats, engines, and options. use when you need to discover available conversions before creating tasks.
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 Tasks
Tool to retrieve a list of tasks. use when you need to enumerate tasks with optional filters like status or date ranges.
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 Webhooks
Tool to list all webhooks. use when you need to retrieve existing webhooks before managing or inspecting them.
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.
Show User
Tool to show the current authenticated user's information. use after authentication to confirm account details.
Connect any two apps with Notis in the middle.
Notion and Cloudconvert, 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 Cloudconvert.