Use a team or a workflow as a member

A member of a team does not have to be an agent. It can be another team, or a workflow. This lets you build large solutions from small parts that you have already tested.

• A team open in its editor. See Create a team of agents.
• Another team or a workflow in your workspace, published.

1. In the panel on the right, select the second tab, Add member. The list of members opens.
2. Select Teams or Workflows to see only those. The list is sorted by folder.
3. Drag the team or the workflow onto the canvas.
4. Select Publish.

The new member is drawn as a hexagon, like an agent. Its icon shows whether it is a team or a workflow.

A team chooses who does what from the roles of its members. This is true for a member that is a team or a workflow too.

1. Open the team or the workflow that you use as a member.

2. In its panel Info, fill in Role. For example, for a team Payment Reminders:

   Writes and reviews a payment reminder for one unpaid invoice.

3. Select Publish.

• A part of the work is a job in itself. Writing and reviewing a reminder is one job. Deciding which invoices need a reminder is another. Build each as its own team, test it alone, then put them together.
• Several larger teams need the same part. Build it once and use it as a member wherever it is needed.

• A part of the work must follow fixed steps. For example, a step where a person must approve, or a rule that must always give the same result. Put those steps in a workflow, and use the workflow as a member.

Whatever a member is, an agent, a team or a workflow, it gives its answer. It can also give named outputs, next to its answer:

What a member says to the next members, and to the manager, is its answer followed by its named outputs, each under its own name:

Plan ready.

Outputs:
- city: Porto

When the answer already holds them, as for an agent that answers in JSON, nothing is repeated. So the next members and the manager read the named outputs of a member, whatever it is.

What we saw: a team whose first member is a workflow that declares the output city, and whose answer, Plan ready., does not name the city. The second member is an agent, asked to write about the city chosen. It named the right city.

This is why a workflow used as a member should declare what it gives. What is not declared stays inside the workflow, and the other members do not see it.

A member that fails makes the team fail. The message says that the team failed, names the member, and says why. A team inside a team fails its parent in the same way, and so on up to the execution.

• A team inside a team makes more calls to the AI model for one request. Keep the levels few.
• Do not add a team to itself. The list of members shows every team of your workspace, including the one you are editing.
• Test each part alone before you put it in a larger team. A problem is easier to find in a small team.

• On the canvas, the team or the workflow is a hexagon among the other members.
• In the list of members, it has a check mark.

Run a team and read its work.