Announce approved roles from Notion
Keep hiring details in Notion and let Notis publish an opening when you mark it ready to share.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Create a LinkedIn post
Creates a new post on linkedin for the authenticated user or an organization they manage; ensure the user has necessary permissions if posting for an organization.
Why this helps
A role can be ready for candidates but still wait on someone to create and publish a separate announcement.
- Link hiring preparation with candidate outreach.
- Choose when a role is ready to be shared.
- Save the extra step of re-creating the announcement.
Setup
Build it in a few focused steps.
- 1Connect Notion and LinkedIn to Notis once through the portal.
- 2Create an automation in the portal or tell Notis the hiring outcome you want.
- 3Ask Notis in one plain-language instruction to publish the role when its Notion record is marked approved for sharing.
- 4Select Page Properties Updated for the hiring data source, choose a report channel, and test with one real approved role.
Questions about this workflow
Can I control which openings get posted?
Tell Notis to publish only records marked approved for sharing.
Does LinkedIn need any special permissions?
The authenticated LinkedIn user needs permission to publish to the intended profile or organization.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Linkedin. A trigger fires from one place; an action lands in another.
Notion triggers
Linkedin actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a LinkedIn post
Creates a new post on linkedin for the authenticated user or an organization they manage; ensure the user has necessary permissions if posting for an organization.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete LinkedIn Post
Deletes a specific linkedin post (share) by its unique `share id`, which must correspond to an existing share.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get company info
Retrieves organizations where the authenticated user has specific roles (acls), to determine their management or content posting capabilities for linkedin company pages.
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.
Get my info
Fetches the authenticated linkedin user's profile, notably including the 'author id' required for attributing content such as posts or articles.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Linkedin, 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 Linkedin.