Slack integration

Prompt apps and agents from the thread where the idea starts.

Recursiv for Slack turns everyday team conversation into a shared AI development surface. Ask for an app, agent, deploy, or approval in Slack, and Recursiv runs the real workflow behind it.

See how it works View architecture

# product-build Prompt-driven development

@recursiv build a Slack-native project room where agents can create apps, deploy previews, and ask for approval.

I created the project, started the app workflow, and opened a durable run.

Project room: ready
Agent plan: queued
Deploy preview: warming

Slack Events API Recursiv workflow Project + agents

Why it matters

AI development becomes multiplayer.

Today, a capable AI agent usually lives inside one operator's IDE or terminal. Recursiv for Slack moves that power into the shared workspace without giving up the infrastructure that makes work real: auth, projects, sandboxes, deploys, agents, memory, billing, and approvals.

Architecture

Slack is the surface. Recursiv is the system of record.

The live bot path is thread-first and bot-token based. Optional ETL is separate, admin-enabled, and scoped to public-channel context.

Slack

Prompt

Mentions, commands, files, and approval clicks arrive through signed Slack webhooks.

Ingress

Verify

Recursiv verifies the signature, dedupes the event, normalizes the thread, and binds it to an org/project.

Recursiv

Run

Project creation, agent setup, sandbox work, deployment, memory, approvals, and audit logs stay in Recursiv.

Delivery

Reply

Progress and final results return to the original Slack thread through the bot token and retryable delivery outbox.

Live bot

Built for everyday prompting. It sees the current Slack thread, runs a Recursiv workflow, and posts updates back where the request started.

Optional ETL

Built for searchable company context. It is off by default, uses a separate token, and syncs only approved public channels.

How to use it

Ask in Slack. Get the working object back.

Build an app @recursiv build a donor CRM with auth, saved contacts, CSV import, and a polished dashboard.

Recursiv creates the project, starts the app workflow, and returns the project room and preview.

Create an agent @recursiv create a support triage agent for this project. Give it Slack and Linear context.

Recursiv configures the agent, tools, memory seed, scope, and approval rules.

Ship a change @recursiv deploy the latest version and tell me what changed before it goes live.

Recursiv runs the deploy path, summarizes the diff, and asks for approval when policy requires it.

Permission model

Useful by default. Explicit when broad context is needed.

The integration should not imply workspace-wide Slack access. The default path is deliberately narrow; broader indexing is a separate admin choice.

Mode

Access

Best for

Thread-first bot

Mentions, files, and bounded history where the bot is present.

Prompting apps, agents, deploys, and approvals.

Channel-aware bot

Channels where the bot is invited and granted history scopes.

Project rooms, support channels, build discussions.

Admin ETL

Selected public channels through a separate ETL token.

Company context search and agent retrieval.

Setup path

Start with one channel. Expand only after proof.

Install the Recursiv Slack app, choose a default Recursiv organization, invite the bot to a test channel, and run the first prompt. ETL remains off until an admin selects public channels for indexing.

Connect Slack