Squidgy for Slack

Your own AI agent in Slack.

Build a no-code AI agent and drop it into Slack — it answers questions, qualifies leads, books meetings, and drafts replies inside your channels and DMs, with the same knowledge base everywhere else you deploy it.

A real agent, not just a notification bot

Most Slack bots push alerts. A Squidgy agent holds a conversation: it remembers context across the thread, retrieves from your knowledge base, calls tools (look up an order, book a slot, create a ticket), and only sends customer-facing replies you have approved. Same agent you ship to your website or marketplace, now living where your team already works.

One agent, every surface

The agent you put in Slack is the same skill file you can publish as a website widget, a marketplace listing, or an installable app. Build it once with Ace, change its behaviour in one place, and every surface updates. Slack becomes one channel, not a separate build.

How it works

  1. 1

    Describe your agent

    Tell Ace what the agent should do and which tools it needs. No code, no Slack app manifest to hand-write.

  2. 2

    Connect Slack

    Authorise the Squidgy Slack connection and pick the channels and DMs the agent should listen in.

  3. 3

    Go live

    The agent starts answering in Slack with your knowledge base, your approval rules, and your tools wired in.

What your agent does with Slack

Internal helpdesk

Answer staff questions from your docs, policies, and wikis — instantly, in the channel where they ask.

Lead qualification

Qualify inbound leads posted to a #sales channel, enrich them, and book the meeting.

Ops copilot

Look up records, trigger workflows, and draft updates without leaving Slack.

Frequently asked

Do I need to write a Slack app to use this?+

No. Squidgy handles the Slack app, OAuth, and event wiring. You describe the agent's behaviour to Ace and connect Slack with a couple of clicks.

Can the Slack agent use the same knowledge base as my website agent?+

Yes. It's the same agent. Upload your docs and URLs once; the agent retrieves from them whether it's answering in Slack, on your site, or in the marketplace.

Does every message get sent automatically?+

Only if you want. Approval workflows let you require human sign-off on customer-facing replies, so the agent never goes off-script in front of someone important.

Is it just for internal use?+

No. Run it as an internal copilot for your team, or as a customer-facing agent in a shared or Connect channel. Same build, your choice of audience.

Put your agent in Slack

Describe it to Ace, connect Slack, and it's answering in your channels today — no code, no developers.

Chat with Squidgy