agent-action-handshake

Empty output in Friday workflow agent steps usually stems from mismatches between FSM action authoring and agent prompt expectations, specifically missing outputTo mappings or complete tool requirements in the runtime handshake contract.

You configure outputTo and inputFrom mappings in your FSM action definitions to chain agent outputs across multi-step state machine workflows, ensuring the runtime auto-injection contract passes documents correctly between sequential agent steps.

The FSM-agent handshake contract defines how auto-injected platform tools, the complete tool, and input/output document chaining rules govern communication between FSM actions and agent prompts to ensure consistent workflow execution.

Friday workflows support four invocation kinds—inline LLM, agent-to-LLM, agent-to-atlas, and agent-to-user—each with unique runtime handling rules that dictate how agent prompts receive inputs and return outputs to the state machine.

You should check the handshake contract when debugging multi-step Friday workflows that chain agent outputs, especially when an agent step is not returning expected results or you suspect a misdiagnosed platform bug in the FSM runtime.

No, the Friday runtime handles auto-injection of platform tools based on the invocation kind, but your FSM action configuration and agent prompts must align with the defined output contract to prevent output failures and communication mismatches.