Configuration Blocks

Configuration blocks for connecting agents and avatars to workflows

Configuration Blocks#

Configuration blocks provide settings and credentials to other nodes in your workflow. Unlike source, transform, and output blocks, configuration blocks do not process messages directly. Instead, they inject context data — like platform credentials — into the workflow.

Avatar Selector#

The Avatar Selector connects your local agent's platform accounts to the workflow, allowing source blocks to collect data using your authenticated sessions.

How It Works#

  1. You select one of your registered BYOD Agents
  2. You choose an avatar (platform account) from that agent
  3. The node outputs avatar data — platform, identity, and available channels
  4. Downstream source nodes (LinkedIn, X/Twitter, Telegram in agent mode) receive this data

The Avatar Selector outputs an avatar data type (shown as an orange connection line), which is distinct from the messages data type used by other nodes.

Configuration#

FieldDescriptionRequired
Select AgentDropdown of your registered agentsYes
Select AvatarDropdown of avatars from the selected agentYes

The avatar dropdown is filtered by the selected agent — changing the agent refreshes the avatar list.

Output Data#

The Avatar Selector provides the following data to connected nodes:

FieldDescription
platformThe platform name (telegram, x, linkedin)
idThe avatar's platform identifier
nameDisplay name of the avatar
channelsAvailable channels/sources for the avatar

Used By#

Source NodeRequired?
LinkedInYes (mandatory)
X (Twitter)Yes (mandatory)
Telegram (Agent Mode)Optional

Note: RSS and Reddit sources do not use the Avatar Selector — they collect data directly without agent authentication.

Setup Prerequisites#

Before using the Avatar Selector, you need:

  1. A deployed agent — see Deploy Your Agent
  2. At least one authenticated avatar on that agent
  3. The agent must be connected to your HubFeed account

Next Steps#