Check meeting document details after an update
When meeting notes change, have Encodian retrieve metadata from the associated PDF so the current file is easier to review.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Get PDF Metadata
Tool to extract PDF metadata and properties. Use when you need to retrieve details like page count, author, file size, and custom attributes.
Why this helps
A changed meeting record may point to a revised document, but checking its properties manually adds another step to close out the notes.
- Retrieve available metadata for the meeting PDF.
- Make revised document details easier to review.
- Reduce extra file-opening steps during meeting follow-up.
Setup
Build it in a few focused steps.
- 1Connect Notion and Encodian to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to retrieve metadata from the PDF associated with updated meeting notes.
- 3Select the Notion Page Content Updated trigger for the meeting notes location or database.
- 4Choose a channel for run reports and test with a meeting page linked to a PDF.
Questions about this workflow
Does this action extract meeting notes from the PDF?
No. It retrieves PDF metadata and properties; it does not extract the document's text.
Can this run for every meeting page?
You can scope the trigger to a page or data source when configuring the Notion trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Encodian. A trigger fires from one place; an action lands in another.
Notion triggers
Encodian actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Decode Base64 String
Tool to decode a Base64 string to a file. Use when you need to extract binary content (e.g., PDF, image) from Base64 data.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Base64 Encode
Tool to encode a string to Base64. Use when you need to convert text into Base64 representation for use in other operations.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Compare Text
Tool to compare two text strings and determine if they match. Use when you have two strings and need to verify if they are equal.
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.
Hash Data
Tool to compute a cryptographic hash (MD5, SHA256, etc.) of text or file data. Use when you need to verify integrity or generate digests.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Unzip File
Tool to extract files from an archive. Use when you need to unzip a package and retrieve its contents.
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.
Get File Properties
Tool to retrieve properties of a file. Attempts multiple Encodian Filer endpoints and fallbacks.
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.
Resize Image
Tool to resize an image by percentage or dimensions. Use when you need to scale or reshape an image with optional aspect-ratio enforcement.
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.
Move File
Tool to move a file between containers. Use when you need to relocate a blob within your storage without manually copying then deleting.
Connect any two apps with Notis in the middle.
Notion and Encodian, 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 Encodian.