Integration

Pilot + Slack: notifications, an AI agent, and Pilot operations from your workspace

Receive Pilot notifications in your Slack channels, query your CRM with a message, and let the AI agent operate from the workspace where your team already lives. Compatible via webhook today, native OAuth integration on the roadmap.

Request a demo

What Slack does with Pilot

Pilot is an AI-driven, end-to-end business system, turnkey out of the box: communication, CRM, sales, scheduling, and operations come native. If you also use Slack, Pilot connects it and operates from your workspace with AI, without asking you to migrate or switch team tools.

Slack is the operating system for internal communication at thousands of technology and professional-services companies. If your team already spends the day there, it makes sense for the things happening in your CRM, calendar, projects, and customer conversations to reach Slack, rather than your team having to go look for them.

Pilot connects with Slack today via incoming webhook and Zapier. It works: you paste the webhook URL into Pilot and configure which events trigger a message to the channel: a new opportunity in the CRM, an alert that a VIP customer is waiting for a reply, a reminder of an overdue task, a low-stock alert, the daily pipeline summary. It's real compatibility (you paste the link and Pilot works) but not a native integration yet.

The native OAuth integration is on the roadmap. When it arrives it will add two-way queries (ask Pilot via Slack and receive an inline reply), a conversational AI agent as a workspace bot, and slash commands to create tasks, move pipeline stages, or schedule meetings without leaving Slack.

What you can do

  • Pilot notifications to Slack channels via incoming webhook: CRM, calendar, task, and operational alert events.
  • Daily summary of the pipeline and sales activity sent to the channel you choose.
  • Alerts that a VIP customer is waiting for a reply or that opportunities have gone N days without movement.
  • Low-stock or restock notifications (if you have connected ecommerce).
  • Pending-approval notices: the owner receives the message in Slack with the approve/reject button (via Zapier).
  • Configuration of which type of event triggers which channel; you don't flood Slack, you choose what matters.
  • Compatibility via Zapier for custom flows (when a channel receives a keyword, create a task in Pilot, etc.).
  • Native OAuth integration on the roadmap: CRM queries via direct message to the bot, slash commands, a conversational AI agent as a workspace app.

Pilot modules that connect

AI Assistants

Your virtual team that runs Pilot for you.

Approvals

Approval flows that move themselves, right from WhatsApp.

CRM

Sales

Sales board with live revenue and real-time alerts.

Team chat

Internal chat with AI summaries of long threads.

What about Slack AI?

Slack AI does channel summaries, smart search, and writing assistance inside Slack. It's useful for helping your team understand what happened while they were away. Pilot operates cross-tool: it brings into Slack what happens outside (CRM, ecommerce, calendar, customer conversations over WhatsApp). The two coexist; Slack AI summarizes the internal conversation, Pilot brings you the customer context. We don't compete for the same job.

Compared with native bots from the Slack marketplace: most are one-trick ponies (a notification from a specific service). Pilot brings the unified context of your sales operation, not just a notification.

Use cases where this integration shines

Teams that connect this tool with Pilot usually start with these scenarios.

Sales automation with AI

An actionable guide for sales teams that want to close more without hiring more reps or migrating CRMs.

AI customer service

Support that replies with real customer context, without dropping threads.

AI project management

Planning, assignment and reassignment with AI — without status meetings.

Industries where this integration is most popular

Sectors with the highest combined adoption of this tool and Pilot.

Technology

Cómo Pilot ayuda al sector technology.

Professional services

Cómo Pilot ayuda al sector professional services.

Manufacturing

Cómo Pilot ayuda al sector manufacturing.

How to connect it

  1. In Slack, go to your workspace > Apps > Incoming Webhooks > Add to Slack. Choose the default channel.
  2. Slack generates a webhook URL (it starts with https://hooks.slack.com/services/...). Copy it.
  3. In Pilot, go to Settings > Integrations > Slack and paste the URL.
  4. Choose which events trigger a notification to Slack and to which channel (you can add several webhooks, one per channel).
  5. For more complex flows (replying from Slack back to Pilot), connect Zapier as a bridge: a Zap that listens for messages in Slack and triggers actions in Pilot via webhook.
  6. Save, and you start receiving notifications in under 5 minutes.

Frequently asked questions

Is it a native integration or via webhook?
Today it's compatibility via incoming webhook and Zapier: functional but one-way (Pilot sends to Slack). The native OAuth integration with a conversational bot, slash commands, and two-way queries is on the roadmap. We'll let you know when it's available.
Can I reply to the Slack bot and have it update Pilot?
Today only via Zapier (you define a Zap that listens to a channel or a command and triggers an action in Pilot via webhook). When the native OAuth integration arrives, queries and commands will be direct, with no Zapier in between.
How many Slack workspaces can I connect?
As many as you want. Each workspace uses a different webhook. Useful for holdings with several workspaces or to separate production from staging.
And DMs and direct messages?
Via webhook, messages are sent to public or private channels where Pilot is authorized. For DMs and inline replies to the bot, we need the native OAuth integration, on the roadmap.
Is it safe to paste the webhook URL into Pilot?
The webhook allows writing to the channel where you created it, not reading the workspace's content. If you revoke it from Slack, it stops working. Pilot stores the URL encrypted at rest and uses it only to send the notifications you configured.
And if I cancel Pilot?
Slack is left intact. The notifications stop arriving. The ones you already received persist in Slack's history; they're yours.

Enable Pilot in your Slack in 5 minutes

Book a demo and we'll show you live how to configure the webhook, what kind of notifications arrive, and how to build a flow with Zapier to reply from Slack back to Pilot. When the native OAuth integration is ready, you'll be on the priority migration list.

Request a demo