Find the right Datascope ticket type from Notion
When a project or issue record changes, Notis can retrieve Datascope ticket types and give you a quick reference before you decide what to do next.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Get Ticket Types
Tool to retrieve available ticket types (findings types) from the DataScope system. Use when you need to access the list of ticket type configurations.
Why this helps
An unfamiliar findings category can send you searching through Datascope while you are trying to keep a Notion task moving.
- See configured ticket types without interrupting your Notion work.
- Get a simple reference tied to the page that changed.
- Spend less time searching when categorization is unclear.
Setup
Build it in a few focused steps.
- 1Connect Notion and Datascope to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to retrieve Datascope ticket types when a relevant Notion record changes.
- 3Describe in one plain-language instruction how to use the updated page context to summarize the available types.
- 4Choose the Notion Page Properties Updated trigger for the intended data source and select a channel for reports.
- 5Test with one real property update and inspect the results.
Questions about this workflow
Does the workflow choose a ticket type for me?
The action retrieves configured types. Your instruction can ask Notis to summarize likely options, but this action does not create a ticket.
Can the trigger watch a particular database?
Yes. Choose Page Properties Updated and scope it to the relevant Notion data source.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Datascope. A trigger fires from one place; an action lands in another.
Notion triggers
Datascope actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Location
Tool to create a new location in DataScope with geographic coordinates. Use when you need to register a physical location with name and code identifiers.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get All Answers V2
Tool to retrieve last answers from Datascope forms (limit 200 per request). Use when you need to fetch form submissions with optional filtering by form, user, date range, or location. Supports pagination via offset parameter for retrieving additional batches.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get All Answers With Metadata
Tool to retrieve all answers with metadata from the DataScope platform. Returns up to 600 form answers with form metadata, user information, timestamps, and GPS coordinates. Use when you need to fetch submission data with filtering options by form, user, date range, or location.
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.
Get all list elements
Tool to retrieve all items from a specific metadata list in Datascope. Use when you need to fetch all elements belonging to a particular list type (products, locations, customers, etc.).
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get All Locations
Tool to retrieve all locations configured in the DataScope system. Use when you need to access location data including addresses, coordinates, and company associations.
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.
Get Last Tickets
Tool to retrieve the last 5 tickets (findings) from the DataScope system. Use when you need to view recent tickets or findings.
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.
Get List Element
Tool to retrieve a specific element from a metadata list by type and ID. Use when you need to fetch detailed information about a specific list element such as locations, products, or other metadata objects.
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 Ticket Types
Tool to retrieve available ticket types (findings types) from the DataScope system. Use when you need to access the list of ticket type configurations.
Connect any two apps with Notis in the middle.
Notion and Datascope, 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 Datascope.