Spot missing or duplicate staff accounts early
A quick roster check after a Notion staff record arrives helps prevent duplicate setup and forgotten accounts.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Get Users
Tool to retrieve a list of all users associated with your account. use when you need to fetch and filter user data.
Why this helps
Founders can lose time checking separate staff lists by hand whenever a new teammate is documented.
- Surface possible existing accounts before setup.
- Reduce repeated roster searches across tools.
- Make the next onboarding step easier to see.
Setup
Build it in a few focused steps.
- 1Connect Notion and Connecteam once in the Notis portal.
- 2Create a new automation or tell Notis the desired check in plain language.
- 3In one prompt, ask Notis to retrieve Connecteam users when a new staff record is added and report likely matches or gaps.
- 4Choose the Notion New Page trigger for the staff data source and a run-report channel.
- 5Test with one real staff record and review the surfaced roster result.
Questions about this workflow
Does this create the account too?
This workflow only retrieves users and reports likely matches or gaps. Use a separate approved-hire workflow for account creation.
Does it require a special Notion page template?
No. The prompt should tell Notis how to recognize a staff record in the pages you already use.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Connecteam. A trigger fires from one place; an action lands in another.
Notion triggers
Connecteam actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive Users
Tool to archive one or more users by their unique ids. use when you need to deactivate users without deleting their records.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Users
Tool to create multiple users in connecteam. use when you need to add several staff or admin accounts at once.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Generate Upload URL
Tool to generate a pre-signed url for uploading a file. use when you need a secure, time-limited url prior to file upload.
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 Chat
Tool to retrieve chat conversations. use when you need to list all team chats/channels after confirming your communications hub is on expert plan.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Custom Field Categories
Tool to retrieve all custom field categories. use when you need to list or filter custom field categories in your connecteam account.
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 Custom Fields
Tool to retrieve all custom fields associated with the account. use when you need to filter, sort, or page through custom fields after authentication.
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.
Get Forms
Tool to retrieve all form definitions from connecteam. use when you need to list all existing forms after enabling the forms api.
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.
Get Jobs
Tool to retrieve a list of job objects relevant to a specific instance id. use after confirming scheduler or time clock instance id when you need to filter and page through jobs.
Connect any two apps with Notis in the middle.
Notion and Connecteam, 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 Connecteam.