See the sites involved before rollout day
A pre-rollout location check gives you a calmer starting point for coordinating catalog image work across physical sites.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
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.
Why this helps
A rollout can stall when site context is scattered and someone has to reconstruct the locations at the last minute.
- Retrieves available site details ahead of a planned image rollout.
- Surfaces addresses and coordinates useful for operational planning.
- Creates a lightweight preparation step on your calendar.
Setup
Build it in a few focused steps.
- 1Connect Slazzer and Datascope to Notis once through the portal.
- 2Create an automation in the portal, or tell Notis what you want in plain language.
- 3Use one instruction to retrieve Datascope locations before the next Slazzer catalog rollout and summarize the sites that need coordination.
- 4Choose a schedule that runs before the rollout and a report channel.
- 5Review the first result against the locations included in a real rollout.
Questions about this workflow
Can it run only before rollout dates?
Choose a schedule that fits your planning cadence, or use a webhook from a planning system.
Will it add rollout locations to Datascope?
No. It retrieves existing configured locations for preparation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Slazzer to Datascope. A trigger fires from one place; an action lands in another.
Slazzer 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.
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.
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.).
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.
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.
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.
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.
Slazzer 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.