Turn vendor requests into Brex vendor cards
Capture the request once in Notion, then let Notis carry the vendor card setup into Brex.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Vendor Card
Create a new vendor card.
Why this helps
Vendor payment setup can become a separate follow-up after the team has already documented what it needs.
- Reduce copy-and-repeat work between planning and finance.
- Keep vendor setup tied to a documented request.
- Make the handoff easier to follow up on.
Setup
Build it in a few focused steps.
- 1Connect Notion and Brex to Notis once through the portal.
- 2Create an automation or ask Notis to create a Brex vendor card for each new vendor request in Notion.
- 3Select the Notion New Page trigger for the vendor request database.
- 4Choose where run reports should arrive.
- 5Test with one real vendor request and review the resulting card.
Questions about this workflow
Will it create a vendor card for unrelated pages?
Scope the plain-language prompt to the vendor request database and intended request type.
Can I test it before relying on it?
Yes. Use one real request and review the created card and automation report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Brex. A trigger fires from one place; an action lands in another.
Notion triggers
Brex actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Budget
Create a new budget for departments or projects.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Card
Create a new card and assign it to a user.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Department
Create a new department.
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.
Create Expense
Create a new expense.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Location
Create a new location.
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.
Create Job Title
Create a new job title.
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.
Create User
Create a new user in the brex account.
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.
Create Vendor Card
Create a new vendor card.
Connect any two apps with Notis in the middle.
Notion and Brex, 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 Brex.