Skip to content
Slack logoAidbase logo

Connect Slack to Aidbase

Move data between Slack and Aidbase 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.

Slack triggers
14
Slack actions
28
Aidbase triggers
8
Aidbase actions
7

Automation ideas

What you can build with Slack and Aidbase

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

  • New Public Message Posted Anywhere in Slack creates Add Video in Aidbase

    Triggers when a new message is posted to any channel.

  • Email Received in Aidbase creates Add Reaction to Message in Slack

    Fires when a new email is received in an Aidbase inbox.

  • New Public Message Posted Anywhere in Slack creates Add Website in Aidbase

    Triggers when a new message is posted to any channel.

  • Email Received in Aidbase creates Send Message To A User in Slack

    Fires when a new email is received in an Aidbase inbox.

  • New Public Message Posted Anywhere in Slack creates Add FAQ Item in Aidbase

    Triggers when a new message is posted to any channel.

  • Email Received in Aidbase creates Send Message To A Channel in Slack

    Fires when a new email is received in an Aidbase inbox.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Slack and acts in Aidbase, 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.