Skip to content
Notis

Keep Coda Updates and Slack Feedback Connected

Coda page updates to Slack. Thread fills with feedback and questions. Notis fetches the replies and links them back to Coda. No feedback gets lost.

Trigger

Specific Coda Page Updated Trigger

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

Action

Retrieve conversation replies

Retrieves replies to a specific parent message in a slack conversation, using the channel id and the parent message's timestamp (`ts`).

Why this helps

Coda pages get updated and posted to Slack, but thread discussion stays siloed—team feedback and questions never make it back to the doc, so changes lack context.

  • Connects Slack feedback directly to Coda updates where decisions live
  • Reduces silos by pulling all discussion into one place
  • Helps teams stay aware of feedback without checking multiple channels
  • Preserves discussion context alongside the work being discussed

Setup

Build it in a few focused steps.

  • 1Connect Coda and Slack to Notis.
  • 2Create automation: 'Fetch Slack thread replies for Coda updates.'
  • 3Tell Notis: 'When a Coda page is updated and posted to Slack, fetch all replies in the thread and include them with the update notification.'
  • 4Select 'Specific Coda Page Updated' as the trigger.
  • 5Test by updating the page, posting it to Slack, collecting thread replies, and verifying Notis fetches them.

Questions about this workflow

How long after the update should Notis fetch replies?

Mention your preference: 'immediately,' 'after 1 hour,' 'at end of day,' etc., and Notis will wait accordingly.

Should Notis fetch only top-level replies or nested threads too?

Specify in your prompt: 'get direct replies only' or 'include the full conversation tree.'

What does Notis do with the fetched replies—does it post them back to Coda?

You control this. In your prompt, say 'just notify me of the replies' or 'add them to the Coda doc as comments.'

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.