Look up Datascope submissions from a Slack request
When a teammate asks in a Slack channel for recent form submissions, retrieve matching Datascope answers and summarize the useful results in the automation report.
When something happens in Slack, 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
Triggers when a new channel is created.
Do this · Action
Creates a location with geographic coordinates.
When a teammate asks in a Slack channel for recent form submissions, retrieve matching Datascope answers and summarize the useful results in the automation report.
When a direct message asks for field report context, retrieve Datascope answers with metadata such as submission time, form, user, and GPS coordinates for a more useful summary.
When someone asks in a Slack channel about current findings, retrieve the five most recent Datascope tickets and surface the results in the run report.
When a Slack message asks which finding types are available, retrieve the Datascope ticket type configurations and report the current options.
When a Slack message requests a location list or location details, retrieve Datascope's configured locations and report the relevant directory information.
When a Slack request names a supported metadata list, retrieve its elements from Datascope to provide a quick reference for the team.
When a Slack message includes a request to inspect a specific Datascope list element, retrieve its details by type and ID for the run report.
When a Slack message asks for answers from a specific period, retrieve Datascope submissions for the requested date range and summarize the results.
When a Slack request concerns where a form response came from, retrieve Datascope answers with available GPS coordinates and submission metadata.
Notis builds workflows that link Slack to Datascope. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Creates a location with geographic coordinates.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Changes an answer in a submitted form.
Triggers when a new channel is created.
Creates an empty list for organizing categorized items.
Triggers when a message is posted in a channel, excluding direct messages.
Adds a new element to a metadata list.
Triggers when a new direct message, including a thread reply, is sent to a user.
Retrieves all items from a specified metadata list.
Triggers when a reaction is added to a message.
Retrieves all configured locations.
Triggers when a reaction is removed from a message.
Assigns a form to a user at a location with a deadline.
Triggers when a bot posts a new message in a channel.
Retrieves the five most recent tickets or findings.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
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:
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.
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 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Slack and Datascope, or any other combination from 1,500+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Datascope.