Connect Slack to Process street

When something happens in Slack, Notis takes the next step in Process street. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Slack to Process street

View example

Turn Slack DMs Into Process Street Workflows

Capture ideas and tasks from direct messages without leaving Slack, automatically creating a workflow run to track them.

View example

Convert Slack Emoji Reactions Into Urgent Process Street Workflows

React to any Slack message with an emoji (e.g., :fire: or :exclamation:) to instantly create a workflow run and prioritize it.

View example

Auto-Create Process Street Workflows From Slack Channel Messages

Monitor a specific Slack channel for new messages and automatically create workflow runs in Process Street based on keywords or patterns.

View example

Auto-Launch Process Street Workflows When New Slack Channels Are Created

Whenever a new Slack channel is created, automatically create a corresponding workflow run in Process Street to track the project or initiative.

View example

Create Daily Standup Workflows on a Schedule

Every morning, create a new Process Street workflow run for your daily standup, ensuring structured capture of goals, blockers, and progress.

View example

Complete Process Street Workflows When Slack Reactions Are Removed

Mark a message reaction as done in Slack to automatically complete the matching workflow run in Process Street, closing the loop.

View example

Turn External Requests Into Process Street Workflows via Webhook

Accept inbound webhooks (from forms, email services, or other tools) and create Process Street workflow runs, routing customer requests to your process system.

View example

Search Process Street Data Sets From Slack DMs

Send a Slack DM with a keyword or ID to search Process Street data sets, instantly retrieving matching records without switching apps.

View example

Get a Weekly Inventory of All Process Street Workflows

Every week, Notis retrieves and reports all your Process Street workflows in Slack, helping you stay aware of available processes and templates.

Supported Triggers and Actions

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

Slack triggers

Process street actions

New Channel Created Trigger

Triggered when a new channel is created in Slack.

TriggerInstant

Complete a workflow run

This tool marks an entire workflow run as completed in process street. it updates the workflow run's status to 'completed', distinguishing it from process street complete task which completes individual tasks.

ActionInstant

Channel Message Received

Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.

TriggerInstant

Create Workflow Run

This tool creates a new workflow run from a specified workflow template. it is one of the most fundamental operations in process street, allowing users to initiate a new instance of a workflow. the tool requires a workflow template id and optionally allows setting a custom name, due date, and whether to enable a share link.

ActionInstant

Direct Message Received

Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.

TriggerInstant

Find Data Set Rows

This tool allows you to search for records within a data set based on form fields. it's useful for retrieving specific records from a data set when you need to find matching entries based on certain criteria.

ActionInstant

Message Reaction Added

Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.

TriggerInstant

List Workflows

This tool retrieves a list of all workflows available in the process street account. it is a fundamental action that allows users to view and access all their workflows, which is essential for other operations that require workflow ids. this action is important because it provides the foundation for other actions that require workflow ids as input parameters, such as creating workflow runs or managing workflow-specific tasks, thereby enabling better workflow management and automation.

ActionInstant

Message Reaction Removed

Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.

TriggerInstant

Undelete Workflow Run

This tool allows you to restore a previously deleted workflow run in process street. it uses the put /v1.1/workflow-runs/{workflowrunid}/undelete endpoint to recover a workflow run within a valid recovery period. it complements the existing process street delete workflow run action by providing a data recovery option to correct deletion mistakes.

ActionInstant

Reaction Added Trigger

DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.

TriggerInstant

Reaction Removed Trigger

DEPRECATED: use `SLACK_MESSAGE_REACTION_REMOVED` instead. Triggered when a reaction is removed from a message.

TriggerInstant

New Bot Message Received Trigger

DEPRECATED: use `SLACK_CHANNEL_MESSAGE_RECEIVED` with `is_bot_message=true` instead. Triggered when a new bot message is posted to a Slack 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 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.

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

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

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.

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.