Inputs
Outputs
None. The Broadcast message block sends a notification and returns no values for later blocks to use. A later block sometimes needs the same data the popup showed. Reference the upstream block that produced it, such as{{ steps.find_records.records }}. Do not reference the broadcast.
Behavior
The block delivers the popup to every user inTarget who is signed in to Attio when the workflow runs. The popup appears in the Attio app, not by email or Slack. A targeted user who is offline never sees the notification.
The block does not queue or resend the popup, and it writes nothing to a record. Once the popup dismisses, there is no durable trace of it.
Style is presentation only. A Warning or Error style changes the popup’s color and icon. It does not stop the run or signal a failure to the engine. The run continues to the next block whatever style you pick.
Duration governs only how long the popup stays visible. A longer duration keeps the message on screen for longer. It does not change who receives the popup or whether it is delivered.
Gotchas
- Offline users miss the message. The popup only renders inside the Attio app for users who are signed in when the workflow runs. A targeted user who is offline gets nothing, and there is no record of the attempt. When the recipient must see the event later, follow the broadcast with a durable channel. Use a Slack post or a Create task block.
- Over-broadcasting trains people to dismiss popups. The block interrupts humans in real time. Firing it on routine events teaches the team to swipe popups away without reading them. Reserve broadcasts for high-signal moments, and route everyday updates to a quieter channel.
- The block leaves no audit trail. A broadcast notifies and then disappears. It is the wrong tool when you need a lasting record of who was alerted. When accountability matters, pair it with a Create task block or a write to a record.
Examples
Alerting the owner about a high-priority inbound lead
A territory-routing workflow assigns a hot inbound lead. It then broadcasts a warning-styled popup to the new owner so they pick it up immediately.
When the run reaches this block, the assigned owner sees an orange popup naming the lead. The run continues to the next block without cost.
Confirming a successful nightly sync to admins
A scheduled maintenance workflow finishes its work. It then broadcasts a success-styled popup to the two workspace admins so they know the overnight job completed.
The admins who are signed in see a green confirmation popup. Any admin who is offline when the workflow runs sees nothing, so a critical job should also write its result somewhere durable.