Skip to content
Notis

Bring page research and your team's Slack context together

Start a review when your process is ready, then let Notis check a public page, look up the relevant Slack conversation, and share a summary with both contexts in view.

Trigger

Webhook received

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

Action

Fetch conversation history

Fetches a chronological list of messages and events from a specified slack conversation, accessible by the authenticated user/bot, with options for pagination and time range filtering.

Why this helps

Research findings and the discussion that explains why they matter often live in separate places.

  • Bring public page findings alongside relevant team discussion.
  • Reduce switching between research and Slack.
  • Share a summary in the conversation where the context already lives.

Setup

Build it in a few focused steps.

  • 1Connect Bright Data MCP and Slack once in Notis.
  • 2Create an automation in the portal or by telling Notis the outcome you need.
  • 3In one instruction, ask Notis to review the public page indicated by the webhook, retrieve relevant Slack conversation history, and post a sourced summary to Slack.
  • 4Choose a webhook trigger and a destination for run reports.
  • 5Test with one real page and a Slack conversation that provides useful context.

Questions about this workflow

What starts the workflow?

A Notis webhook trigger starts the automation when an HTTP request reaches its webhook endpoint.

What Slack information can it include?

It can retrieve history from a Slack conversation the connected account or bot can access. Your instruction should identify the relevant conversation.

Does the workflow know which page to review?

Include the page reference in the request or otherwise make it available in the automation prompt. The workflow can only review information Bright Data MCP can retrieve.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Bright Data MCP triggers

Slack actions

Recurring trigger

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

TriggerScheduled

Set snooze duration

Deprecated: turns on do not disturb mode for the current user, or changes its duration. use `set dnd duration` instead.

ActionInstant

Webhook trigger

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

TriggerInstant

Add a custom emoji to a Slack team

Deprecated: adds a custom emoji to a slack workspace given a unique name and an image url. use `add emoji` instead.

ActionInstant

Add an emoji alias

Adds an alias for an existing custom emoji in a slack enterprise grid organization.

ActionInstant

Add a remote file

Adds a reference to an external file (e.g., google drive, dropbox) to slack for discovery and sharing, requiring a unique `external id` and an `external url` accessible by slack.

ActionInstant

Add a star to an item

Stars a channel, file, file comment, or a specific message in slack.

ActionInstant

Add call participants

Registers new participants added to a slack call.

ActionInstant

Add emoji

Adds a custom emoji to a slack workspace given a unique name and an image url; subject to workspace emoji limits.

ActionInstant

Add reaction to message

Adds a specified emoji reaction to an existing message in a slack channel, identified by its timestamp; does not remove or retrieve reactions.

ActionInstant

Connect any two apps with Notis in the middle.

Bright Data MCP and Slack, 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 Slack.