Status Log in

ReferenceProperties, status codes, operators and limits. For looking things up mid-task.

Send Message To Groups

Last updated 24 March 2026

The Send Message To Groups job sends a message template to one or more groups. If no explicit groups are connected, it can fall back to groups and units already present in the workflow context.

Properties

The properties for configuring the send are described below.

  • Message (optional)
    • Connected message template to send.
  • Groups (optional)
    • Explicit groups to receive the message.
  • Send only to active units (optional; default: false)
    • If enabled, only active units in the target groups are used as recipients.
    • Legacy behaviour and is not commonly used.
  • Use workflow context units (optional; default: false)
    • Include units already present in the workflow context.
  • Override message text (optional)
    • Replace the message template body with a custom value.
  • Override form template ID (optional)
    • Override the form template used in the message.
  • Message resource (optional)
    • Message resource to use instead of a directly connected message template.
  • Add files as metadata for app messages (optional; default: false)
    • Attach workflow files as metadata for app-message sends.
  • Ignore send if no receivers (optional; default: false)
    • Skip the send without raising an account error when no recipients are found.

Referencing syntax

Use workflow expressions when overriding message content dynamically.

  • Use Override message text for runtime-specific content.
  • Use Message resource when the message template was loaded or created earlier in the workflow.

Receiver selection

The job can gather recipients from several places.

  • Use explicitly connected groups when the audience is known in advance.
  • If no groups are connected, the job can default to workflow-context groups and the temporary group.
  • Enable Use workflow context units when units already loaded into workflow context, in the temporary group for example, should also be considered.

For app messages, the job also applies default app-message settings such as sender and inbox values from merged settings when needed.

Best practices and tips

  • Connect groups explicitly when the intended audience should be obvious from the workflow design.
  • Keep recipient selection deterministic. If the workflow can pull receivers from explicit groups, workflow-context groups, temporary groups, and workflow-context units, document which source is intended for that flow.
  • Use Ignore send if no receivers only when an empty recipient set is expected and should not be treated as an error.
  • Resolve the message from one primary source when possible, either a connected template or a message resource, so the send step is easy to reason about and troubleshoot.
  • Keep message selection clear: use either a connected message template or a message resource when possible, rather than mixing both patterns unnecessarily.
  • Message templates
  • Send Message To Units
  • Find Message Template As Resource

References

ReferenceAnswer Sender

The Answer Sender job replies to the originator of an incoming message or form answer. Use it when a workflow should answer the person who started the conversation without having to build the…

ReferenceFind Or Create Units

The Find Or Create Units job searches for units based on a workflow value and creates new units only if no matching units are found and creation is allowed. Use it when an incoming sender, email…

ReferenceFind Units By ID

The Find Units By ID job resolves one or more unit GUIDs into actual unit objects. Use it when you already know the unit IDs and want to load those units into the workflow context for later…

ReferenceGroup Operations

The Group Operations job is the main pipeline job for working with groups. It lets you find groups, optionally filter them, perform group-level operations, and then decide how the resulting groups…