Connect Slackbot to Datascope
When something happens in Slackbot, Notis takes the next step in Datascope. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Slackbot to Datascope
Review new channel field reports
When a Slack channel receives a field report, retrieve recent Datascope answers so the team can review the latest submissions.
Build a submission brief from a Slack DM
When a direct message asks for a field update, retrieve Datascope answers with metadata and return a concise brief.
Check recent tickets when a message is flagged
When someone adds a reaction to a Slack message, retrieve the latest Datascope tickets for quick follow-up.
Start location onboarding from a new Slack channel
When a new Slack channel is created for a site, create its Datascope location using details supplied in the automation instruction or channel context.
Surface generated Datascope files in Slack
When a Slack channel receives a request for exports, list Datascope files generated within the requested date range.
Answer location questions from Slack DMs
When a direct message asks about field sites, retrieve all Datascope locations and return the relevant details.
Explain available ticket types after an issue reaction
When a Slack message receives a reaction, retrieve Datascope ticket types so the team can classify the issue consistently.
Find Datascope list elements from a channel request
When a Slack channel asks for a product, customer or location reference, retrieve all elements from the specified Datascope metadata list.
Retrieve a specific Datascope element from a DM
When a direct message names a Datascope metadata element, retrieve its detailed record for a precise answer.
Supported Triggers and Actions
Notis builds workflows that link Slackbot to Datascope. A trigger fires from one place; an action lands in another.
Slackbot 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.
New Channel Created Trigger
Triggered when a new channel is created in Slack.
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.
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
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.).
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
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.
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
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.
Message Reaction Removed
Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.
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.
Reaction Added Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Slackbot and Datascope
Connect any two apps with Notis in the middle.
Slackbot 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.