Workflow node: Agent is on team

What it does

This is a condition node that answers one specific question: does the evaluated agent belong to a team (or to one specific team)? Depending on the answer, the workflow continues down the Yes branch or the No branch.

When to use it

Use it to branch an automation based on which team owns the agent a conversation is assigned to. For example, apply different rules when the assigned agent is on "Support Tier 2" versus any other team, or simply confirm a conversation landed with some team before moving on.

Configuration

• Agent to evaluate: defaults to the agent already assigned to the conversation (agent_source = assigned); you can also pin a specific agent by id (specific).
• Team mode: "any team" (any, default) returns Yes if the agent belongs to at least one team; "specific team" (specific) requires picking which one.
• If there's no assigned agent (an unassigned conversation), the node goes straight to the No branch.

Example

An escalation workflow: right after "Assign agent", an Agent is on team node in specific mode points at "Support Tier 2". If it's Yes, the workflow lets the conversation continue untouched; if it's No, it fires an Add internal note node flagging that it needs to be reassigned to that team.

Variables it exposes

The node makes variables like $agent_in_team, $agent_team_names, $agent_team_count, $matched_team_name, and $agent_team_members available, which are handy for messages or notes later in the same workflow.

Troubleshooting

If the node always returns No even though the agent is genuinely on that team, check you're evaluating the right workspace — teams are workspace-scoped, and an agent can belong to a same-named team in a different workspace that simply doesn't count here.