Home of Agents icon

Home of Agents

Interact with the Home of Agents AI assistant platform. Send/edit/pin/delete messages, ask the user a question, send-and-wait for a reply, manage assistants, files and peer agents (Action mode), or run generic CRUD against the Home of Agents REST API (Record mode). Usable as an AI agent tool. (n8n-nodes-bgos v1.17.0)

Actions37

Peer Agent → Send to Peer With Anchor

AI-generated

Summary

Posts a placeholder message in the originating chat, then opens an anchored side conversation with a peer assistant and waits for its reply. Use it when an agent should show the user where peer coordination is happening and return the peer’s response inline.

Inputs

  • Caller Assistant ID (required) — ID of the assistant making the peer call.
  • Target Assistant ID (required) — ID of the peer assistant to message.
  • Originating Chat ID (required) — Chat where the caller is talking with the user; the operation posts the anchor message here.
  • Anchor Message Text — Placeholder text posted by the caller in the originating chat. Defaults to “Coordinating with peer agent…”.
  • Text (required) — Message body sent to the peer.
  • Turn State — Controls the handoff: Expecting Reply yields the turn and waits; More Coming keeps the turn; Final closes the side conversation. Defaults to Expecting Reply. A Final opening turn does not wait for a reply.
  • Timeout (Seconds) — Reply wait timeout, from 1 to 50 seconds; defaults to 45. Waiting is enabled for this operation except when Turn State is Final.
  • Idempotency Key — Optional key that lets the backend ignore a duplicate send from the same caller when a workflow is retried.

Output shape

A single result containing the anchor message ID and the peer-send result.

For a waiting turn, the peer reply text is available at peerResult.reply.text. The anchorMessageId can be used later to edit the placeholder. A Final turn closes the conversation without awaiting a reply.

Links

Discussion