Skip to content
Notis

Connect Slack to Eventee

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

When this happens · Trigger

Do this · Action

Examples

Ways Notis can move work from Slack to Eventee

View example

Turn Slack speaker nominations into Eventee speakers

When a team member nominates a speaker in a Slack channel, add that person to the relevant Eventee event so the nomination does not get lost in chat.

View example

Add confirmed speakers from Slack DMs

When a direct message confirms a speaker and gives the event context, have Notis add the speaker to Eventee so private coordination turns into a maintained roster.

View example

Add a speaker when the team shares their bio

When Slack contains a speaker introduction with a bio and event context, add the person as a speaker in Eventee so the profile is ready for event coordination.

View example

Add confirmed panelists to Eventee

When a Slack message confirms a panelist and identifies the event, add them to the Eventee speaker list so panel planning has a current roster.

View example

Capture keynote speaker announcements

When the team announces a confirmed keynote speaker in Slack, add that speaker to the corresponding Eventee event and keep the roster in sync.

View example

Reflect a confirmed speaker replacement

When a Slack message confirms a replacement speaker and clearly identifies the new person and event, add the replacement to Eventee so the roster reflects the change.

View example

Add a replacement after a speaker withdraws

When Slack confirms that a speaker has withdrawn and names a replacement, add the replacement to Eventee so the organizer has a current roster to work from.

View example

Add speakers who confirm rehearsal participation

When a speaker confirms in Slack that they are participating in the event, add them to the Eventee speaker list so the organizing team can work from a current roster.

View example

Capture speakers introduced in planning threads

When a Slack planning thread introduces a speaker and identifies the event, add the person to Eventee so their name does not disappear when the thread moves on.

Supported Triggers and Actions

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

Slack triggers

Eventee actions

Recurring trigger

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

TriggerScheduled

Add speaker

Tool to add a new speaker to a specific eventee event. use after creating an event and obtaining its id.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete Speaker

Tool to delete a speaker by their id. use when you need to remove a speaker after confirming their id.

ActionInstant

New Channel Created Trigger

Triggered when a new channel is created in Slack.

TriggerInstant

List Events

Tool to retrieve a list of all events. use when you need an overview of all events.

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

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

Message Reaction Added

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

TriggerInstant

Message Reaction Removed

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

TriggerInstant

Reaction Added Trigger

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

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.

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 Eventee

Connect any two apps with Notis in the middle.

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