Notion

Introduction#

The Notion integration connects your Notion databases to Orshot workflows. A workflow can run whenever a page is added or edited in a database, read pages from a database as a data source, and write results (like the render URL) back to the page that triggered the run. Each page becomes a row of data, one field per database property, so you can render personalized images, social graphics, PDFs, or videos from it and deliver them anywhere a workflow can.

Connect Notion#

1. In Orshot, open Integrations from your workspace sidebar.
2. Find Notion and click Connect.
3. On Notion's consent screen, pick the pages and databases you want Orshot to access, then you're returned to Orshot as Connected.

Only workspace owners and admins can connect or disconnect, and there's one connection per workspace.

The workflow trigger#

Add the New/updated page in Notion trigger to a workflow:

1. Create a workflow and pick New/updated page in Notion as the trigger.
2. Choose your database from the picker.
3. Pick what to trigger on: new pages, updated pages, or both. The default is new pages.
4. Optionally enable Process existing pages to run the workflow for pages that were already in the database before you activated it.
5. Add your render and delivery steps, then activate.

Orshot checks the database for changes on a schedule (how often depends on your plan). Notion records page timestamps at minute precision, so changes made in the same minute a page already fired for may not fire again.

The Notion source and write-back steps#

Besides the trigger, two more workflow steps use the connection:

• Notion (source): reads pages from a database. Useful with a schedule or webhook trigger, for example to render a fresh batch from a database every morning.
• Write to Notion (destination): writes a result back to the page each row came from. By default it writes the render URL; point it at any URL, text, files, or number property in your database.

Page data#

Each page arrives as a flat row your steps can map to template fields:

A few details on how property values are flattened:

• Select and status properties use the option's name; multi-select and people join multiple values with commas.
• Files properties use the first file's URL.
• Formulas and rollups come through as their computed value.
• Date ranges come through as start/end.
• Empty properties come through as empty strings, so your field mappings stay stable.

Notes#

• The Notion trigger, source, and write-back steps are available on paid plans.
• Renders started by the workflow use your workspace's credits, like any other workflow run.
• The number of pages processed per check is capped by your plan.
• Disconnecting Notion stops any workflows that use it until you reconnect. You can also revoke access from Notion under Settings then Connections.

Need Help?#

• Contact support at hi@orshot.com or use the chat button in your Orshot dashboard