Bring batch shipping options into your order plan
When a batch plan is ready, let Notis check available shipping options across the listed orders and report what needs a decision.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
List Shipping Options Multiple
Tool to list shipping options for multiple orders. Use when you need a batch rate quote before final submission.
Why this helps
Comparing shipping choices order by order can turn a batch handoff into repetitive admin.
- Consolidates shipping-option review for multiple orders.
- Lets the team make shipping decisions before submission.
- Reduces repeated lookup steps during batch preparation.
Setup
Build it in a few focused steps.
- 1Connect Notion and FinerWorks to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally to create one.
- 3In one prompt, tell Notis to retrieve FinerWorks shipping options for the orders in a new batch plan and report any order details that are not ready for a quote.
- 4Select the Notion New Page trigger for the batch-plan database and choose a run-report channel.
- 5Test with a small batch and review the options before submitting any orders.
Questions about this workflow
Does this submit the orders?
No. It retrieves shipping options for review. Submit orders separately after all customer and line-item details are finalized.
How many orders can the action check?
The listed action is for shipping options across multiple orders; the batch should stay within FinerWorks' supported request limits.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Finerworks. A trigger fires from one place; an action lands in another.
Notion triggers
Finerworks actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Images
Tool to add images to a finerworks library. Use after preparing up to 5 images with metadata and URIs.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get User
Tool to retrieve the current user's profile. Use after authentication to fetch account details.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Media Types
Tool to get available media types. Use when you need to retrieve all or filtered media types after authentication.
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.
List Product Types
Tool to list product types. Use when you need to retrieve available product types from FinerWorks after setting up credentials.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Shipping Options Multiple
Tool to list shipping options for multiple orders. Use when you need a batch rate quote before final submission.
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.
List Style Types
Tool to get a list of style types. Use when you need to retrieve available style options before configuring a product.
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.
Submit Orders
Tool to submit up to five new orders. Use after all customer and line-item details are finalized.
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.
Test My Credentials
Tool to test the configured FinerWorks credentials. Use after setting up your web_api_key and app_key to confirm validity.
Connect any two apps with Notis in the middle.
Notion and Finerworks, 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 Finerworks.