Connectors

Slack connector for Croft: alerts and daily digests from your apps

Connect Slack to Croft so team apps can post messages, send alerts, and read channels - with your Slack bot token held by Croft, not in app code.

Free to try. No card needed.

How it works

The Slack connector gives apps on Croft the ability to post messages and read channel history through Croft's gateway. Your Slack bot or user token stays with Croft; apps request actions without holding tokens. Share the connection across approved apps so your team can build alert systems, approval bots, and notification tools that post to Slack without scattering tokens through generated code.

Use cases

What you can build

Build an approval workflow app that posts a request to

Create a daily standup bot that pulls project status from your internal tracker and posts a summary to

Let your support tool send an alert to

Post alerts from scheduled tasks

Croft apps can run scheduled tasks, and a scheduled task can call the Slack connector like any other part of the app. That makes Slack the place where an app's results land without anyone having to open it: a check runs on a schedule, and if something needs attention, the app posts to the right channel.

The app never holds your Slack token. It asks Croft to post, Croft checks the app is allowed to use the connector, adds the token on the way out and returns the result.

Example: a daily digest for your team

A common first Slack app is a morning digest. You describe it to your AI assistant in plain language, for example:

“Every weekday at 8:30, summarise what's open in our tracker and post it to #team-updates through the Slack connector. If anything is overdue, list it first.”

Your assistant builds the app and its schedule, and each run reads the app's own data and posts one message to the channel. The same pattern works for a weekly sales summary, a list of overdue approvals, or a heads-up when a number crosses a line you care about.

Permissions and credential handling

  • The token stays with Croft. It is stored encrypted and is never shown to an app or written into the code your assistant generates.
  • Slack decides what the token can do. The connector can only do what the Slack token's permissions allow, so give your bot only the access you want apps to have. Posting messages needs less access than reading channel history.
  • One connection, many apps. Every app you allow can use the same Slack connection, so you change or replace the token in one place.
  • Calls are audited. Every call through the connector is logged.

Set up the Slack connector

  1. Get a Slack token. In your Slack workspace, create a Slack app, give it the permissions you want apps to have (for example, permission to post messages), install it and copy its bot token. Invite the bot to the channels it should post in.
  2. Connect it in Croft. Ask your assistant to “connect our Slack workspace”, or add it by hand as described in the connector docs. Paste the token once; Croft holds it.
  3. Allow the apps that need it. Choose which apps can use the connection.
  4. Ask for the app. Describe the alert or digest, the channel and the schedule, and your assistant builds it.

You bring your own Slack workspace and token; Croft holds the connection. If an app is run before the connector has a token or before it has been given access, it should show a calm “this integration isn't switched on yet” message rather than an error.

Admin controls

Admins decide who gets to use Slack from a Croft app. A sensitive connector can be set to need an admin's approval, so anyone can build an app that asks to use it but it stays off until an admin says yes. Approve it for a specific app or person rather than the whole company, and use the log to answer “which apps can post to our Slack?” See roles and permissions and the security overview, or read the wider guide to Croft connectors for AI-built apps.

Connect Slack to Croft

Your Slack credentials stay encrypted with Croft and never appear in app code. Apps call the connector through Croft's gateway, which checks permissions and adds the key on the way out. One connection can be shared across multiple apps you allow, with a full audit trail of every call.

Free to try. No card needed.

CRM Quotes z z

Your team’s first app could be live tonight.

Free for a day, and a week once your first app is live. No card needed.