Turn a Notion team roster into a Bitwarden import
Start a team roster in Notion and let Notis prepare its corresponding Bitwarden members and groups in one import request.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Import Members and Groups
Tool to bulk import members and groups in a single request. Use when migrating or seeding an organization with multiple members and groups at once. Import is all-or-nothing: a single malformed entry in `members` or `groups` causes the entire request to fail.
Why this helps
Setting up shared vault access by hand means repeating roster details across tools and increases the chance that someone is missed.
- Reduce repeated entry when a team starts using shared vaults.
- Keep the roster as the context for the import request.
- Get a run report that surfaces import errors for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Notion and Bitwarden to Notis once through the portal.
- 2Create an automation in the portal or ask Notis in plain language to prepare a Bitwarden member and group import from new roster pages.
- 3Pick the Notion New Page trigger for the roster database and choose a channel for run reports.
- 4Test with one real roster page and review the import result before relying on it.
Questions about this workflow
Does this create new Bitwarden members automatically?
The automation can prepare and submit the Bitwarden import request based on the roster. The import is all-or-nothing, so review the run report for malformed entries or rejected requests.
What does the roster need to contain?
Include clear member and group details in the page context so Notis can interpret the intended import. Keep sensitive passwords out of the roster.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bitwarden. A trigger fires from one place; an action lands in another.
Notion triggers
Bitwarden actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Group
Tool to delete a group. Use when you need to permanently remove a group by its ID after ensuring no dependencies exist.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Member
Tool to delete a specific organization member. Use when you need to remove a member from the organization after verifying their member ID.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Group Member IDs
Tool to retrieve the list of member IDs for a specific Bitwarden group. Use when you need only the user IDs of all members in a group.
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 Organization Subscription
Tool to retrieve subscription details of the current organization. Use after obtaining a valid bearer token.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Import Members and Groups
Tool to bulk import members and groups in a single request. Use when migrating or seeding an organization with multiple members and groups at once. Import is all-or-nothing: a single malformed entry in `members` or `groups` causes the entire request to fail.
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.
Reinvite Member
Tool to re-send an invitation to a pending or removed member. Use when an existing member's invite needs re-issuing.
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.
Retrieve Group
Tool to retrieve details for a specific group. Use when you need to fetch group permissions and assigned collections by group ID after authenticating with a valid access token.
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 Member
Tool to retrieve details for a specific member. Use after obtaining a valid member ID to get full metadata.
Connect any two apps with Notis in the middle.
Notion and Bitwarden, 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 Bitwarden.