Can NocoDB and Slack talk in both directions?

Yes. Build one flow that starts in NocoDB and acts in Slack, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.

Connect NocoDB to Slack

Move data between NocoDB and Slack the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Start building Explore NocoDB Explore Slack

NocoDB triggers: 0
NocoDB actions: 5
Slack triggers: 14
Slack actions: 29

Automation ideas

What you can build with NocoDB and Slack

A few flows teams run between NocoDB and Slack. Use one as a starting point, or build your own from scratch.

New Public Message Posted Anywhere in Slack creates Create a Record in NocoDB
Triggers when a new message is posted to any channel.
New Public Message Posted Anywhere in Slack creates Delete a Record in NocoDB
Triggers when a new message is posted to any channel.
New Public Message Posted Anywhere in Slack creates Update a Record in NocoDB
Triggers when a new message is posted to any channel.
New Message Posted to Channel in Slack creates Create a Record in NocoDB
Triggers when a new message is posted to a specific #channel you choose.