Skip to content
Notis

Connect Slack to Databox

When something happens in Slack, Notis takes the next step in Databox. 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 dataset in Databox.

Examples

Ways Notis can move work from Slack to Databox

Capture weekly KPI updates in Databox

Turn clear KPI updates posted in Slack into records in an existing Databox dataset, keeping progress visible without copying numbers by hand.

Log customer feedback shared in Slack

Push customer feedback explicitly relayed in Slack into a Databox dataset for a searchable, consistent view of recurring themes.

Record sales wins from Slack

Capture sales wins announced in Slack as Databox records, so the team can review its progress without maintaining a separate manual log.

Track launch milestones from Slack

Save launch milestones shared in Slack to a Databox dataset, giving the team one place to review progress and completed steps.

Log project blockers shared in Slack

Record explicitly described blockers from Slack in Databox to help teams spot repeated friction and follow progress over time.

Capture campaign results shared in Slack

Save campaign performance figures posted in Slack to Databox, making later comparisons less dependent on finding the original update.

Capture support volume updates from Slack

Add support volume snapshots explicitly shared in Slack to Databox, so operational changes are easier to compare over time.

Save cash runway updates from Slack

Capture runway figures explicitly shared in Slack in a Databox dataset, keeping important planning updates available in one place.

Record product feedback signals from Slack

Preserve product feedback signals explicitly reported in Slack as Databox records for easier review alongside other business indicators.

Supported Triggers and Actions

Notis builds workflows that link Slack to Databox. A trigger fires from one place; an action lands in another.

Slack triggers

Databox actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create Dataset

Creates a dataset in Databox.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Data Source

Creates a data source in Databox.

ActionInstant

New Channel Created Trigger

Triggers when a new channel is created.

TriggerInstant

Delete Dataset

Permanently deletes a Databox dataset; this action cannot be undone.

ActionInstant

Channel Message Received

Triggers when a message is posted in a channel, excluding direct messages.

TriggerInstant

Delete Data Source

Permanently deletes a Databox data source and its datasets; this action cannot be undone.

ActionInstant

Direct Message Received

Triggers when a new direct message, including a thread reply, is sent to a user.

TriggerInstant

Get Dataset Ingestion Status

Checks the status of a Databox dataset ingestion.

ActionInstant

Message Reaction Added

Triggers when a reaction is added to a message.

TriggerInstant

List Accounts

Lists Databox accounts available to the authenticated user.

ActionInstant

Message Reaction Removed

Triggers when a reaction is removed from a message.

TriggerInstant

Push Data to Dataset (V1)

Pushes data points to a Databox dataset.

ActionInstant

New Bot Message Received Trigger

Triggers when a bot posts a new message in a channel.

TriggerInstant
Trigger Types

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 schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used

Scheduled triggers

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.

Daily · 8:00Weekdays onlyOnce · Dec 13
Beta

Database triggers

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.

Row addedProperty editedValue > limit
Why AI automation

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.

Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use

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.

Notis

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:

TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability

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

All12Manager5Telegram1Messages0WhatsApp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything 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.

Related pairs

More ways to connect Slack and Databox

Connect any two apps with Notis in the middle.

Slack and Databox, or any other combination from 1,500+ 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 Databox.