Keep mailed event invitations moving as guests join
Add a guest to your Notion list and let Notis start the invitation print workflow.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Print Job
Tool to create a new print job. Use when a document is ready to submit (optionally confirming immediately).
Why this helps
Invitation fulfillment can become a repetitive side task as a founder coordinates an event and other priorities.
- Starts invitation fulfillment from the guest list you already maintain.
- Reduces repeated manual work as guests are added.
- Helps keep event administration from becoming another memory burden.
Setup
Build it in a few focused steps.
- 1Connect Notion and Intelliprint to Notis once through the portal.
- 2Create an automation in the portal or ask Notis for a guest-to-invitation print workflow.
- 3Describe in one instruction that Notis should create an Intelliprint job for a mailed invitation when a guest is added, using the available invitation document and guest address.
- 4Choose the New Page trigger for the relevant guest database and set a channel for reports.
- 5Test with one eligible guest and inspect the print job.
Questions about this workflow
Will every new guest receive a paper invitation?
Make the intended eligibility clear in the prompt and use the relevant guest database trigger.
What if I need to send one batch after the guest list closes?
This new-page trigger is suited to per-guest fulfillment. For a batch process, choose a Notion status change on the records when they are ready.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Intelliprint. A trigger fires from one place; an action lands in another.
Notion triggers
Intelliprint actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel or Delete Print Job
Tool to delete or cancel an existing Print Job by its ID. Use after confirming the print job ID to remove or refund a job.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create background
Tool to create a new Background. Use when you have a background file (and optional name or team) to upload.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Print Job
Tool to create a new print job. Use when a document is ready to submit (optionally confirming immediately).
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.
List Backgrounds
Tool to list backgrounds with optional filtering and pagination. Use after uploading or managing backgrounds to retrieve current entries. Example: 'List backgrounds for team=team_1234 with limit=50 and skip=10'.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Print Jobs
Tool to list print jobs with optional filters and pagination. Use after confirming API key.
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 Templates
Tool to list all available templates. Use after authenticating API key to browse available templates.
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.
Merge Files
Tool to merge multiple files into one document. Use when you need a single merged document from separate files.
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.
Retrieve Background
Tool to retrieve a specific Background by ID. Use when you need background details before further processing.
Connect any two apps with Notis in the middle.
Notion and Intelliprint, 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 Intelliprint.