Start NetSuite vendor setup from a Notion onboarding page
A new supplier onboarding page can trigger vendor setup in NetSuite once it clearly indicates the supplier is ready and provides the essential details.
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 Vendor
Creates a new vendor record in NetSuite. Required: vendor name (companyName) and subsidiary ID. Use this when you need to add a new vendor to NetSuite's vendor list for procurement or accounts payable purposes.
Why this helps
Vendor onboarding has several small steps, and the finance-system entry can be missed while attention moves to other work.
- Give vendor onboarding a consistent starting point.
- Reduce the chance that supplier setup stays unfinished in a notes system.
- Keep creation conditional on readiness.
Setup
Build it in a few focused steps.
- 1Connect Notion and NetSuite to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to start NetSuite vendor setup from a ready Notion onboarding page.
- 3Use one plain-language instruction to create a vendor only when the new page marks the supplier ready and contains its name and subsidiary information.
- 4Select the Notion Page Created trigger, choose a run-report channel, and test with one ready onboarding page.
Questions about this workflow
Will this create vendors from draft intake pages?
No, if the instruction requires the page to explicitly indicate readiness and the required details to be present.
What should it do with missing details?
Have Notis report what is missing and wait for the page to be completed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Netsuite. A trigger fires from one place; an action lands in another.
Notion triggers
Netsuite actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Async Job Status
Retrieves the current status of an asynchronous NetSuite REST job. Use this tool to check whether an async job has completed and its progress state. When you submit any NetSuite REST API request with the 'Prefer: respond-async' header, NetSuite returns a Location header containing the job ID. Use that job ID with this tool to poll the job's status. The response indicates if the job is completed, its progress state (pending/processing/succeeded/failed), and provides links to retrieve the job results once completed.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Async Job Task
Retrieves the task reference (task ID and URL) for an asynchronous job in NetSuite. Use this action after submitting an async request with 'Prefer: respond-async' header and receiving a job_id in the Location header. The task ID is required to retrieve the job's result using the async get job task result action. Typical workflow: 1) Submit async request → 2) Get job_id → 3) Use this action to get task_id → 4) Poll job status → 5) Retrieve results with task_id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Async Get Job Task Result
Tool to retrieve the payload result of a completed async task. Use after confirming the async job and task have completed to fetch the operation's output.
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 Customer
Creates a new customer record in NetSuite. Requires subsidiary ID and either company name (for business customers) or first/last name (for individual customers). Returns the location URL of the created customer record, or an async job URL if using async mode.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Customer Payment
Creates a customer payment record in NetSuite. Requires account (deposit account), customer reference, and payment amount. Optionally link payment to specific invoices via the 'apply' sublist. Returns the URL of the created payment record.
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 Employee
Creates a new employee record in NetSuite. Required: firstName, lastName, and subsidiary ID. Returns the URL of the created employee in the location field. Supports async creation with 'respond-async' preference.
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 Invoice
Tool to create a new invoice record. Use when you have all required invoice details and want to add them to NetSuite.
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 Item
Creates a new item record in NetSuite via REST API. Supports multiple item types including inventory items, service items, and description items. Returns the URL of the created item. Use this when you need to add new products, services, or descriptive items to the NetSuite catalog.
Connect any two apps with Notis in the middle.
Notion and Netsuite, 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 Netsuite.