Carry new vendor context into Borneo recipients
Add a vendor once in Notion and let Notis prepare the corresponding recipient record in Borneo using the context already at hand.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create recipient with details
Creates a new recipient in the borneo integration platform. this endpoint is used to register and manage detailed information about entities that receive or process data within the system. it captures essential details for compliance with data protection regulations, including the recipient's role, location, data storage information, and associated legal documents like data processing agreements (dpas). the endpoint is particularly useful for organizations managing complex data ecosystems with multiple partners, vendors, or internal departments. it should be used when onboarding new data recipients or updating existing recipient information to maintain accurate records for auditing and compliance purposes. note that while many fields are optional, providing comprehensive information enhances the system's ability to manage data flow and compliance effectively.
Why this helps
Vendor details and data-sharing notes get scattered when a supplier is recorded in one place but must be registered elsewhere.
- Start recipient documentation as part of vendor intake.
- Keep relevant vendor context together across planning and compliance.
- Cut down on manual re-entry when a new supplier is approved.
Setup
Build it in a few focused steps.
- 1Connect Notion and Borneo once through the Notis portal.
- 2Create a portal automation or ask Notis to register each new vendor page as a Borneo recipient.
- 3Use one plain-language prompt to describe the recipient record Notis should create from the available vendor context.
- 4Select the vendor database's New Page trigger, choose a run-report channel, and test with one actual vendor.
Questions about this workflow
Does this create a legal agreement as well?
No. This Borneo action creates a recipient record; it does not create a data processing agreement.
Can Notis fill optional recipient details?
The prompt can ask Notis to use supported context from the page and avoid guessing where details are missing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Borneo. A trigger fires from one place; an action lands in another.
Notion triggers
Borneo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Access scan iteration by id
Retrieves detailed information about a specific scan iteration in the borneo integration platform. this endpoint allows users to fetch the current status, results, and metadata associated with a particular scan iteration. it should be used when monitoring the progress of a scan, analyzing results, or troubleshooting integration workflows. the endpoint provides a snapshot of the scan iteration at the time of the request and may not reflect real-time updates if the scan is still in progress. it's particularly useful for auditing, reporting, and maintaining a history of scan operations within borneo's automation and integration processes.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add discovered recipients
Adds multiple discovered recipients to the system as confirmed recipients. this endpoint should be used when you have a list of previously discovered recipient ids that you want to officially add to your recipient database. it's particularly useful for bulk operations where multiple recipients need to be added simultaneously. the endpoint accepts an array of unique uuids, allowing for efficient processing of multiple recipients in a single api call. note that this endpoint only adds recipients; it does not provide any information about the recipients or perform any other actions beyond adding them to the system.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Archive discovered recipient
Archives a specific discovered recipient in the borneo platform. this endpoint is used to move a discovered recipient's data into an archived state, which may be useful for compliance, data retention, or organizational purposes. it should be called when you need to store historical data about a recipient that has been identified through borneo's data visibility and privacy automation processes. the endpoint uses a post method, suggesting it may trigger backend processes to properly archive the recipient's data. note that this operation might affect the visibility or accessibility of the recipient's data in other parts of the system.
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.
Delete data breach by id
Deletes a specific data breach evaluation record from the borneo system. this endpoint should be used when an organization needs to remove an evaluation record, typically in cases where the record is no longer relevant, contains errors, or needs to be purged for compliance reasons. the operation is irreversible, so it should be used with caution. this tool is part of borneo's databreachmanagement functionality, supporting the platform's data protection and privacy management capabilities. it helps maintain an accurate and up-to-date record of data breach evaluations, which is crucial for regulatory compliance and risk management.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create and schedule cloud resource scan
The createscan endpoint initiates a new scan operation in the borneo integration platform, allowing users to configure and schedule data scans across various cloud resources. this powerful tool enables users to set up both one-time and recurring scans, with extensive customization options for resource selection, data inspection policies, and scan limits. it's particularly useful for compliance checks, sensitive data discovery, and regular security audits across cloud environments. the endpoint supports a wide range of resource types and provides flexible scheduling options, from immediate execution to complex cron-based recurring scans. users should carefully consider the scan configuration to balance thoroughness with resource utilization, especially for large-scale environments. while highly versatile, users should note that some features may be resource-type dependent, and should refer to borneo's documentation for specific connector and filter support.
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 dashboard user
Creates a new dashboard user in the borneo integration platform with specified roles, organizational access, and authentication settings. this endpoint allows for granular control over user permissions across different organizations and departments within the borneo ecosystem. it supports integration with external identity providers (okta or gcp) for authentication. use this endpoint when onboarding new users or updating existing user permissions. note that while only the email is required, it's recommended to provide comprehensive role and organization information for proper access control.
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 department with translations
Creates a new department in the borneo integration platform. this endpoint allows you to add a department to the system with support for multilingual information. it's particularly useful when setting up the organizational structure within borneo or when expanding to new regions requiring localized department names. the endpoint should be used when you need to establish a new department entity that other parts of the system can reference. it's important to note that this endpoint only creates the department and does not associate it with any specific workflows or integrations - those would need to be set up separately.
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 domain with polling frequency
Creates a new domain within the borneo integration platform, allowing for automatic polling and management of connected systems or applications. this endpoint is used to set up a new integration point with a specific name and polling frequency. it should be used when establishing a new connection or integration within the borneo ecosystem. the endpoint is particularly useful for setting up automated data synchronization or workflow triggers between different business applications. it does not provide information about existing domains or modify existing ones; it is strictly for creating new domains.
Connect any two apps with Notis in the middle.
Notion and Borneo, 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 Borneo.