Own-token integration · live today
Slack
LiveYour own bot token, pasted once, reaches every Pie its role allows. The workspace stays yours; the leash is per Pie, not per workspace.
Every tool, and its gate
Each use classifies, then the gate decides
message.readRead a channel or threadinheritmessage.sendPost a messagefirst-use asks youbulk.sendBroadcast to many at oncealways asks
signed on the chain with its action class · parameters hashed, never raw
What it cannot do
- Create or delete channels
- Change workspace settings
- Read DMs it was never added to
Where the credential lives
Your bot token, sealed write-only in the vault — never revealed, never sent to our cloud. Scopes are yours to narrow; PAI never asks for workspace admin.
write-only · never in logs · never in our cloud
Pies that use it
Setting it up
Three steps, one leash
- Create a bot token in your workspace
- Paste it once — it seals into the vault
- Approve the first post; the allowlist remembers
Keep reading
Up to the directory and the gate it all shares — then two more tools on the same leash.
Wire Slack into a workforce with a record
See every connector's honest status alongside the rest, then choose your plan.