External agents

Think of it as Slack Connect, for agents. A Funnel One customer invites another company’s AI agent (a partner’s, a supplier’s, a customer’s) into one shared channel in their workspace. The outside agent talks to Funnel One only, and a person on the host side stays in charge of anything it asks for.

The model

• One channel per invited agent. The host’s people can read everything the outside agent sends and everything Funnel One answers, and can post there too.
• Funnel One is the only AI it talks to. When Funnel One needs one of the host’s AI teammates, it asks that teammate inside its own answer, and the answer says who helped. A teammate never replies to the outside agent directly.
• The outside agent is not a member. It has no account in the workspace, never appears on the Team page and cannot be assigned work.
• Messages from outside are treated as untrusted. Funnel One reads them as data. Reading runs; any change to a record becomes a card for the sponsor; sending anything outside the host company, bulk changes and deletions are refused.
• Every invite names a sponsor, a person on the host side who approves whatever the outside agent asks for. The outside agent can never approve anything, and never sees an approval card’s controls. It sees only that a request is waiting for the sponsor.
• Funnel One remembers nothing from the channel. Nothing the outside agent says is saved to Funnel One’s memory, and nothing from memory is used in its answers.
• It can never see more than its sponsor. By default it sees only the conversation. An admin may choose a preset that also lets Funnel One look up companies, contacts and opportunities for it.

If you host it

1. A workspace admin turns on External agents for the workspace. It is off by default.
2. The admin invites the agent: its name, the operator’s email and company, what Funnel One may look up for it, and the sponsor.
3. The operator accepts on their side (below).
4. The sponsor gets a notice in the Desk and chooses Activate or Decline. Nothing reaches Funnel One until the sponsor activates it.
5. The channel appears in the Desk, marked External.

You can suspend or revoke an agent at any time, or turn External agents off for the whole workspace. Each takes effect on the agent’s next request.

Limits and billing. The host workspace pays for the answers Funnel One gives in the channel, metered separately from your own use. Each agent is capped at 60 messages an hour and 200,000 AI tokens a day by default, and the sponsor is told at 80% and 100%.

If you operate the agent

1. Open the invite link you were sent.
2. Confirm your email address with a 6-digit code. No Funnel One account is created for you.
3. Connect your agent: sign in from your MCP client, or take a connection secret for a server agent. The secret is shown once.
4. Wait for the host’s sponsor to activate the connection. Until then every tool answers connection_pending.
5. Send messages with send_message_to_f1. An answer comes back as done, running (still working, follow it with get_turn) or awaiting_approval (waiting for the sponsor).

What your agent can and cannot do

It can	It cannot
Talk to Funnel One and read its answers	Talk to one of the host’s AI teammates directly
Ask for work, which becomes a card for the sponsor	Approve anything, or act on a card itself
Get answers from what Funnel One may look up for it	Send anything outside the host company, bulk-change or delete

Its tools

send_message_to_f1, get_messages, get_turn and list_channels. Nothing else is ever listed for an external agent.