Keep product context aligned with current positioning
Revise the product positioning in Notion and let Notis update the matching Forcemanager product.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Update Product
Tool to update a product by ID in ForceManager. Use when modifying product details.
Why this helps
Sales conversations can use outdated product context when positioning changes do not reach the product record.
- Keep product records closer to current messaging.
- Reduce repeated manual updates after positioning work.
- Help teams use consistent product context.
Setup
Build it in a few focused steps.
- 1Connect Notion and Forcemanager to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally for this workflow.
- 3Describe in one instruction how relevant changes in a Notion product positioning page should update the matching Forcemanager product.
- 4Choose the Notion Page Content Updated trigger, select a channel for run reports, and test with one real positioning revision.
Questions about this workflow
Does this add a product record?
No. It updates an existing matching Forcemanager product.
Can the prompt limit updates to meaningful changes?
Yes. Describe which positioning changes should be carried into the product record.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Forcemanager. A trigger fires from one place; an action lands in another.
Notion triggers
Forcemanager actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Activity
Delete an existing activity by ID. Tries multiple base hosts and path variants to maximize compatibility across environments and gateways.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Company
Tool to delete a company by its ForceManager ID. Use when you need to remove an existing company from the system.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Contact
Delete an existing contact by ID. Tries multiple base hosts and path variants to maximize compatibility across environments and gateways.
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 Sales Order
Delete a sales order by ID using ForceManager REST API. Tries multiple base hosts and path variants to maximize compatibility across environments. Accepts successful HTTP status codes (< 300) even when the response is non-JSON, capturing response text.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Sales Order Line
Delete a sales order line by ID using ForceManager REST API. Tries multiple base hosts and path variants to maximize compatibility across environments. Accepts successful HTTP status codes (< 300) even when the response is HTML instead of JSON, capturing the response text as a message.
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.
Delete Master Data Value
Delete a master-data value (Z_ table) by ID using ForceManager REST API. Tries multiple base hosts and path variants to maximize compatibility across environments. Accepts successful HTTP status codes (< 300) even when the response is HTML instead of JSON, capturing the response text as a message. Also retries sending authentication headers as query parameters on HTTP 401 as some gateways expect them in query string.
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 View
Delete a saved view by ID. Tries multiple base hosts and path variants to maximize compatibility across environments and gateways.
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.
Get Activity
Tool to get a single activity by ID. Use when you need to fetch a specific activity. Returns empty entity with found=False on non-JSON HTML or if not found.
Connect any two apps with Notis in the middle.
Notion and Forcemanager, 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 Forcemanager.