The Fork block splits an Automation Studio flow into multiple independent paths that all run at the same time, letting unrelated actions execute in parallel rather than one after another.
For example, a rule could send an immediate acknowledgement and assign a ticket to L1 support if priority is High, send an acknowledgement and assign to L2 if priority is Medium, and assign directly to L3 with no acknowledgement if priority is Low, with all three conditions handled independently as three paths inside a single fork block.
An electronics retailer sells three products, zPhone, zPad, and zWatch, and wants every support ticket acknowledged and routed to the correct product team. The flow triggers on Ticket Created, sends an acknowledgement email, and then forks into three paths, each with an If block checking the Product Name and an action assigning the ticket to that product's support team. Because the fork evaluates all three product conditions at the same time, only the matching path actually runs, and routing happens immediately regardless of which product the ticket relates to.
An organisation wants tickets from paid customers acknowledged and prioritised, while tickets from non-paid users go to a separate team. The flow triggers on Ticket Created and forks into two top-level paths: one for paid users, which checks the contact's field type, sends an acknowledgement, and then forks again into two further paths based on priority, assigning High priority tickets to L1 and everything else to L2; and one for non-paid users, which checks the same field type is not Paid User and assigns the ticket straight to L3. This nests a fork inside a fork, separated by If and Action blocks, showing how Fork and If blocks combine to build multi-level routing logic.