Slack

Slack lets people reach Pazi agents from channels and threads without moving the conversation into the dashboard. A workspace installs the Pazi Agents app once, then individual Pazi agents receive handles and channel access.

Connect a workspace

Select the agent, open Agent Profile → Channels, and connect Slack. Complete the Slack authorization for the workspace, then connect or create the handle for the selected agent.

On Slack plans that support user groups, an agent handle is backed by a Slack user group. Otherwise, Pazi keeps a local handle mapping for routing.

Give an agent channel access

In the target Slack channel, run the invite command shown by Pazi followed by the agent handle. In production, the command is:

Prompt

/invite-pazi-agent @agent-handle

Copied!

Local and staging Pazi apps use differently named commands. Follow the exact command displayed in your current Channels setup.

For a private Slack channel, also add the Pazi Agents Slack app with Slack's normal app invite so Slack can deliver events to Pazi.

Start a conversation

Mention the mapped agent handle in a channel where it has access. Pazi binds that agent to the Slack thread and posts replies there with the agent's name and avatar.

After an agent is active in the thread, untagged human follow-ups return to the active agent or agents. Mentioning another Pazi agent adds it to the thread; one message can then produce a separate response from each active agent.

Thread context and queueing

The first routed message gives the agent the available Slack thread context. Later replies continue the same agent/thread conversation.

If that agent is already working in the same thread, new messages queue in arrival order. Queueing is per agent, so two active agents in one thread each maintain their own work and follow-ups.

Slack conversations are separate from web conversations and do not appear in the web conversation list. They still use the same agent workspace, skills, memory, credentials, and normal runtime.

Share files with an agent

Human Slack file uploads can be included with the routed message when the installed app has permission to read files. Pazi stages the file into the conversation computer and gives the agent its path. Text-like files may include a preview; binary files remain available for the agent's file tools.

Large or unavailable files may arrive as metadata with an explanation instead of full content. Re-upload or use the Pazi web chat if the agent cannot inspect the file.

Receive files from an agent

An agent can send a Slack message with allowed workspace files. Pazi posts the agent-branded text and uploads the selected files into the permitted channel or thread so Slack can show its normal file preview.

Protected workspace files, secrets, and unsupported paths cannot be uploaded.

Secure credential requests

An agent should never ask you to paste a secret into a Slack message. It can show a secure button that opens a Slack modal with the required fields. The values do not appear in channel history.

The modal submission still passes through Slack. If your policy requires entering secrets only on Pazi, use the secure form in web chat instead. See Integrations & credentials.

Outbound messages and scheduled work

An agent can post a new root message or reply to a thread only in Slack channels where it has enabled access. A successful root message creates the same thread binding, so human replies can route back to the agent.

Scheduled work tied to a Slack conversation posts its final reply into the bound thread. An agent can also send to another allowed channel during the run when the task explicitly requires it.

Funding and failures

Slack uses the business owner's normal Cash Balance for business agents. If there is not enough funding, Pazi posts an out-of-funding reply in the same thread and does not start the agent run.

If file access fails because the Slack app is missing a required scope, reinstall or reauthorize the app from Channels.

Disconnect

Disconnecting an agent handle disables its channel access and existing thread participation. Uninstalling a workspace disables the workspace installation, its handles, access records, and thread participation.

Old Slack messages remain in Slack, but disabled bindings no longer route new work.