Review Flutterwave transaction timelines from Notion comments
When someone flags a payment in a comment, get the transaction sequence ready for follow-up without starting a separate search.
Trigger
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.
Action
View Transaction Timeline
Tool to retrieve the event timeline for a transaction. use after obtaining the transaction id to audit or track the sequence of events.
Why this helps
Questions left in comments can linger while someone manually tracks down the transaction history.
- Make payment questions easier to investigate from the discussion.
- See the sequence of events for a relevant transaction.
- Reduce the chance a comment gets separated from its follow-up.
Setup
Build it in a few focused steps.
- 1Connect Notion and Flutterwave to Notis once through the portal, and ensure the Notion connection can read comments.
- 2Ask Notis to create an automation or select New Automation in the portal.
- 3Use one prompt asking Notis to fetch the Flutterwave timeline for the transaction referenced by a new payment comment.
- 4Choose Comment Created and select where run reports should appear.
- 5Test with one comment that clearly identifies a transaction and review its timeline.
Questions about this workflow
Does Notion need comment access?
Yes. The Notion integration needs the Read comments capability. If it was enabled after authorization, re-authorize the connection.
Can a comment without a transaction reference be handled?
Tell Notis to report that it cannot identify a transaction rather than guessing, and test with an unambiguous comment.
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.