The External channel makes an agent available at a public URL — anyone with the link can chat with it, no Pinkfish account required. It’s the right choice for public-facing agents like a support assistant or a product Q&A bot.
“Users can interact with this agent without logging into Pinkfish. Ideal for public-facing agents.”
How it works
- The agent must have at least one Release. If you’re still on a pure draft, publish a release first.
- Toggle External on in the agent’s Channels tab.
- A public URL appears under the External card with a copy-to-clipboard button.
- Share the URL anywhere — it opens a full chat surface, not a widget snippet.
If you change External settings but haven’t saved, a yellow triangle appears next to the card with the tooltip “Save the agent to persist this external access change.” Click Save in the top bar to commit.
Enabling External on an agent that uses tools from Connections (Slack, Gmail, Salesforce, etc.) pops a warning: those tools are removed from the agent, because they depend on an authenticated user’s connection and can’t run anonymously. Tools from Embedded Services (code execution, artifacts, etc.) stay available.
What External is not
- It is not a widget embed. There’s no iframe snippet to drop into your site and no appearance customization today. If you want an embedded experience, link users to the public URL.
- It is not a programmatic API. External is a human chat surface. To call the agent from code, use the API channel or the Agent Management API.
