Create Flutterwave virtual accounts for new Notion customers
Give customer onboarding a clear next step by having Notis arrange a unique account when the customer record is created.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Create Virtual Account
Tool to create a new virtual account number. use after confirming customer details when assigning a unique account for bank transfers.
Why this helps
Assigning individual bank transfer accounts can become a separate follow-up task that is easy to miss during onboarding.
- Start account assignment from the customer onboarding record.
- Reduce manual handoffs during payment setup.
- See whether the account creation run completed.
Setup
Build it in a few focused steps.
- 1Connect Notion and Flutterwave to Notis once through the portal.
- 2Create a new automation in the portal or ask Notis conversationally to create it.
- 3Write a single prompt asking Notis to create a Flutterwave virtual account for a new customer when the needed details are present.
- 4Select the Notion Page Created trigger and choose a run-report channel.
- 5Test with one real customer record and verify the account details in Flutterwave.
Questions about this workflow
What if the customer record lacks required details?
Tell Notis in the prompt to proceed only when the needed customer information is available, and review the test run.
Does this create an account for every page?
Use the Page Created trigger scoped to the relevant database and describe the intended customer records in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Flutterwave. A trigger fires from one place; an action lands in another.
Notion triggers
Flutterwave actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Beneficiary
Tool to create a new transfer beneficiary. use when you need to add a beneficiary before making a transfer.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Bulk Virtual Account Numbers
Tool to create multiple virtual account numbers. use when you need to generate multiple static virtual accounts for customers in a single request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Payment Link
Tool to create a hosted payment link. use when you need a shareable payment url for one-time transactions.
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 Payment Plan
Tool to create a new payment plan. use after confirming plan and customer details.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Subaccount
Tool to create a new subaccount. use when you need to configure split disbursement accounts.
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 Virtual Account
Tool to create a new virtual account number. use after confirming customer details when assigning a unique account for bank transfers.
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.
Delete Beneficiary
Tool to delete a beneficiary by id. use when you need to remove a saved transfer beneficiary by its unique id after confirming the id.
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.
Disable Payment Link
Tool to disable a flutterwave payment link. use when you need to prevent further payments from an existing link after confirming the link is valid.
Connect any two apps with Notis in the middle.
Notion and Flutterwave, 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 Flutterwave.