Node: Schedule Team Message
How to use the Schedule Team Message node to post an alert into an internal Space later on from a workflow.
The Schedule Team Message node queues a message to be posted later into a Team Space, instead of posting it right away. It's the "post later" counterpart to the Publish to Team node: same destination, different timing.
When to use it
- For internal reminders scheduled ahead of time ("alert the team if no one has picked up this case in 2 hours").
- To post a summary or alert to the Team at a specific time, rather than at the exact moment of the trigger.
Requirements
- The destination Team Space must exist in the same organization and must not be archived.
- Some user must be resolvable to attribute the message to (the workflow's creator, otherwise an organization owner).
- The message can't end up empty after variables are applied.
Configuration
- Destination Space (
space_id, required): the Team Space to post into. - Message (
message, required): the text to post.{{...}}variables are resolved at scheduling time, just like the Schedule Message node for contacts. - Send timing:
- Relative mode (
mode = relative): posts N minutes later (delay_minutes). - Absolute mode (
mode = absolute): posts at an exact date/time (at). If that time has already passed, it posts one minute after the node runs (it's never lost).
- Relative mode (
Example
A workflow fires when a conversation goes unassigned. The Schedule Team Message node is set to relative mode with delay_minutes = 120 targeting the "On-call" Space, with the message "⏰ {{contact.first_name}}'s conversation has been unassigned for 2 hours." If someone picks it up during that window, the alert still posts — so it's worth pairing this with an earlier condition that checks whether it's still unassigned before reaching this node.
Tips
- When the post should go out immediately, use Publish to Team instead — this node is only for deferring the send.
- The scheduled post is processed by the Team module's normal scheduled-message sweep, so it runs with the same broadcast, mentions, and unread behavior as a message typed by hand.
Troubleshooting
- "Team space X not found" or "is archived": the configured Space no longer exists or is archived.
- "Nothing to schedule (empty message)": the Message field was empty after variables were applied.
- "Invalid schedule time":
delay_minutesisn't set, oratisn't a valid future date.
Related articles
-
Build your first workflow
Omnifox workflows automate your operation: a trigger starts the automation and action nodes do the work. Build a welcome message in minutes.
-
Workflow triggers catalog
Learn which events can start a workflow automatically in Omnifox.
-
Action nodes available in workflows
Discover the actions a workflow can run automatically.
-
Conditions and branching (if/then) in a workflow
Make your flows take decisions and follow different paths based on each contact data.
-
Ready-to-use workflow templates
Start your automations in minutes from prebuilt flows you can customize.