Skip to content
Notis

Turn External Form Submissions Into Slack Channels

User submits a form. Webhook fires. Slack channel created instantly. Your team has a space to discuss the request before they know it's coming.

Trigger

Webhook received

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

Action

Create channel

Initiates a public or private channel-based conversation

Why this helps

External submissions (support requests, feature proposals, intake forms) arrive but don't automatically create team spaces—coordination happens via email or DMs instead of organized channels.

  • Automatically creates team spaces for incoming requests without manual setup
  • Routes different types of submissions (support, features, projects) to separate channels
  • Reduces time from submission to first response by having a channel ready
  • Keeps external communication organized and searchable

Setup

Build it in a few focused steps.

  • 1Connect Slack to Notis.
  • 2Create automation: 'Webhook channels from form submissions.'
  • 3Tell Notis: 'When I send a webhook with form data, create a Slack channel based on the submission details.'
  • 4Select 'Webhook' as the trigger and get your unique webhook URL.
  • 5Configure your external form or system to send webhooks to that URL (e.g., Zapier, n8n, custom script).

Questions about this workflow

What information should the webhook payload contain?

Mention what's available: 'the form includes name, email, and description,' and Notis will use those to create the channel name and initial details.

Can I route different submission types to different channels?

Yes. In your prompt, describe the routing: 'if type is support, create a channel in #support-hub; if it's a feature request, create in #features.'

Can I auto-invite the form submitter or a team to the channel?

Yes. Mention this in your prompt: 'invite the submitter's email as a guest' or 'add the support team to every ticket channel.'

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Coda triggers

Slack actions

Coda Document Deleted Trigger

Triggers when a Coda document is deleted.

TriggerPolling

Set snooze duration

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

ActionInstant

New Coda Document Trigger

Triggers when a new Coda document is created.

TriggerPolling

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

New Coda Page Trigger

Triggers when a new page is added to a Coda document.

TriggerPolling

Add an emoji alias

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

ActionInstant

Specific Coda Page Updated Trigger

Triggers when a specific page within a Coda document is updated.

TriggerPolling

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.

Not just Coda and Slack. Any combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7 days free trial with 20$ free usage included.
No card. Works with personal or business Slack.