Slack through Squiid

What Slack is

Slack's API covers posting messages with Block Kit layouts, reading channel history, uploading files, opening modals, handling slash commands and responding to interactive buttons, plus Events for reacting to what happens in a workspace. For applications it is the default place to send anything a human needs to see quickly: a failed job, a new signup, an error spike, an approval request that someone has to click. Incoming webhooks are the simplest path for one-way alerts, while a full app is needed for anything interactive.

In AI-coded products Slack is also becoming the interface itself. An agent that reports what it did, asks for a decision, or accepts instructions in a thread is a common pattern, because it puts the agent where the team already is rather than behind another login. That means a bot token with permission to read and post in channels, which is a credential nobody wants copied across three deployments. Rate limits are per method and fairly strict, which matters for a bot that posts on every event rather than in batches.

Why connect it through Squiid

Slack is a connect service on Squiid. You link your existing workspace through the standard OAuth flow, and Squiid holds the token and issues scoped access through https://api.squiid.io/v1/slack/... with Authorization: Bearer $SQUIID_API_KEY, with the official SDKs working by base URL swap (gateway convention). Your Slack plan is billed by Slack directly at the provider's listed price, and the connection is revocable in one click, which is faster than reinstalling an app in a workspace you may not administer. Message formatting with Block Kit is also easier to generate correctly than it looks, since the payload is plain JSON.

• One account, one key, one bill, one dashboard. Slack sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Slack credentials. Your code carries SQUIID_API_KEY, so SLACK_BOT_TOKEN, SLACK_SIGNING_SECRET, SLACK_APP_TOKEN, SLACK_WEBHOOK_URL never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Slack costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Your existing Slack workspace connected, not replaced
• Post messages with Block Kit and read channels
• Slash commands and interactive components
• Scoped, revocable access instead of a stored bot token
• Slack seats stay billed by Slack

How to connect Slack

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces SLACK_BOT_TOKEN, SLACK_SIGNING_SECRET, SLACK_APP_TOKEN, SLACK_WEBHOOK_URL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/slack/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Slack bills your workspace plan directly at the provider's listed price, with no Squiid margin. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Slack usage, with no markup and no per-request margin.

Slack has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Slack usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Your own account: the Slack account was always yours and Squiid only holds an authorised connection, so revoking it leaves nothing behind. Squiid never owns your code, your schema or your domain, and the gateway speaks Slack's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Slack through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Slack usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.