Let a reusable Group own a Persona, Brand, Product, or other Brain selection, map its fields to compatible nodes inside the Group, and switch the selected record without rebuilding the flow.
Where: Select a Group on the Flowgen canvas → right sidebar → Brain items; or choose the Group-owned record input on its card/wizard.
Before you start
- A Flowgen canvas with a Group containing the nodes that should consume the Brain fields.
- A Brain record type and record available in the current project or organization scope.
Key ideas
- The Group owns the selection: Add a typed Brain item input to the Group. Its selected record and field mappings are saved with that Group; the group runtime reads the current record again when the flow runs. This is not the legacy pattern of wiring a standalone Brain Read node’s record_in question.
- Map fields to internal node inputs: Choose a specific record field or “Any [type] field,” then an internal node and compatible input socket. “Any” selects a filled field of that type, allowing different records of the same type to use different field keys.
- Switching is record replacement, not graph rewiring: Changing the selected record refreshes the Group-owned snapshot. Stable field keys are preferred; a uniquely matching label or only compatible field can resolve a renamed field. Missing or ambiguous matches stay unresolved instead of silently choosing the wrong value.
- The source can be changed at the Group boundary: Pick the Brain item in the Group editor or in the Group-owned record selector shown on its card/wizard. Inside nodes can use the Group Brain source from their input/source picker; they do not need their own Brain Read node for this binding.
Steps
- Select the Group and open its right sidebar. In Brain items, choose the record kind and select Add Brain input.
- For the new input, choose Browse Brain and select the record. The record type filters the browser; use the clear control to unbind it.
- Under the selected item, use Choose a Brain field, Internal node, and Node input, then select Connect field. Repeat for each internal input that should receive Brain data.
- Alternatively, open an internal node’s input source picker and choose the compatible field under “Group Brain · [input name]”. This creates the same Group-owned mapping.
- If the Group is presented as a wizard, choose or replace the Brain record in the Group-owned record selector. The selected item remains owned by the Group input.
- Run the Group. It reloads the selected record before consuming mapped values; select a different compatible record and run again to reuse the same internal graph with new context.
Field matching and safety
- Exact field keys win. If a key changed, a unique same-label field or the sole remaining compatible field may be used.
- If multiple alternatives remain, the binding reports missing or ambiguous rather than guessing.
- “Any image field” and equivalent type choices take the first filled field of that type when switching records.
- Clearing or losing the selected record does not revive stale connected-text mirrors.
Keep the graph reusable
- Use Group Brain for record data that should be selected at the Group boundary and passed to internal nodes.
- Do not describe this as a Brain Read node with a record_in prompt; that is a different/legacy flow and does not provide the Group-owned hot-swap contract.
- Brain items are Group inputs; they do not imply that ordinary text inputs or unrelated project Brand links are replaced.
Tips
- Prefer specific fields when a Group needs predictable semantics such as Brand tone or Persona image. Use “Any [type] field” when interchangeable records legitimately store the needed value in different fields.
- Use a concise Group input label; it appears at the boundary and helps the internal source picker identify the correct Brain input.
Limitations and important notes
- The record must be readable in the active project/organization scope.
- Field mappings are type-compatible; an image field cannot be wired to an incompatible text-only socket.
- Ambiguous or absent fields require a corrected mapping or a different record; the system does not infer intent.
Troubleshooting
An internal node does not show the Group Brain option.
Confirm the node is a descendant of the Group, the Group has a Brain item input, and the destination socket is compatible with the field type.
Switching records leaves a field unresolved.
Open the Group Brain mapping, inspect the missing/ambiguous field warning, and choose the correct field explicitly. Renamed fields only resolve automatically when the match is unique.
The selected record is no longer available.
Browse Brain again in the Group input and select an accessible record. A failed or cleared selection is not treated as a valid source.