Skip to content
Notis

Connect Slack to Discordbot

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

This action is deprecated and unsupported.

Examples

Ways Notis can move work from Slack to Discordbot

Give project decisions a focused Discord thread

When a decision lands in a Slack channel, start a Discord thread so the team can keep its follow-up focused and easy to find.

Mirror new Slack work areas in Discord

When a Slack channel is created, create a corresponding Discord channel so a cross-platform team has a place to coordinate.

Give Slack help requests a Discord follow-up thread

Turn a clear Slack help request into a Discord thread where someone can take ownership and continue the conversation.

Carry important Slack DMs into a private Discord conversation

When a Slack DM contains a follow-up worth keeping visible, have Notis send a concise recap to a designated Discord channel.

Share Slack-approved announcements in Discord

Use a designated Slack reaction as the signal to post an announcement in the right Discord channel.

Bring launch updates from Slack to Discord

Post launch milestones shared in Slack to your Discord community so supporters can follow progress without manual reposting.

Turn Slack deadlines into Discord reminders

Recognize deadline commitments in Slack and post a concise reminder in a Discord channel where the team can see it.

Make Slack blockers visible in Discord

Share clear blockers from Slack in a Discord team channel so they can get attention and support sooner.

Surface unowned Slack tasks in Discord

Post tasks that lack a clear owner to Discord so the team can assign responsibility before they are forgotten.

Supported Triggers and Actions

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

Slack triggers

Discordbot actions

Recurring trigger

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

TriggerScheduled

Add recipient to group channel

This action is deprecated and unsupported.

ActionInstant

Webhook trigger

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

TriggerInstant

Add guild member

Adds a user to a guild using an OAuth token with the guilds.join scope.

ActionInstant

New Channel Created Trigger

Triggers when a new channel is created.

TriggerInstant

Assign role to guild member

Assigns a role to a guild member; requires MANAGE_ROLES permission.

ActionInstant

Channel Message Received

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

TriggerInstant

Add reaction to message

Adds an emoji reaction from the bot to a message.

ActionInstant

Direct Message Received

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

TriggerInstant

Add thread member

Adds a user to an unarchived thread if they can access its parent channel.

ActionInstant

Message Reaction Added

Triggers when a reaction is added to a message.

TriggerInstant

Ban user from guild

Permanently bans a user from a guild, optionally deleting their recent messages.

ActionInstant

Message Reaction Removed

Triggers when a reaction is removed from a message.

TriggerInstant

Bulk ban users from guild

Bans up to 200 guild users, optionally deleting their recent messages; BAN_MEMBERS is required.

ActionInstant

New Bot Message Received Trigger

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

TriggerInstant

Bulk Delete Messages

Deletes 2–100 messages under 14 days old from a channel; requires message-management permission.

ActionInstant
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 Discordbot

Connect any two apps with Notis in the middle.

Slack and Discordbot, 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 Discordbot.