Node: Publish to Team

The Publish to Team node sends an automatic message to a Team Space (Omnifox's Slack-like internal communication module) when a workflow runs. It's the bridge between Inbox automations (SLA breaches, VIP contacts, closed conversations, low CSAT, etc.) and internal team communication: instead of an agent having to flag it manually, the workflow posts the alert itself.

When to use it

• To alert the team about an important Inbox event without relying on someone noticing it: a broken SLA, a VIP contact writing in, a negative CSAT score, a reopened conversation, and so on.
• When you want the alert to land in a shared channel (the Team Space) instead of an individual notification.

Requirements

• The destination Team Space must exist in the same organization and must not be archived; if it was deleted or archived after the workflow was configured, the node skips with a logged error (it doesn't break the rest of the flow).
• Some user must be resolvable to attribute the message to (usually whoever created the workflow, otherwise an organization owner).

Configuration

• Destination Space (space_id, required): the Team Space to post into. Private spaces are marked with 🔒 in the picker; you can still post to them even if the workflow's creator isn't a member.
• Message (message): the post body. Supports trigger-context variables like {{contact.first_name}} or {{conversation.id}}.
• Include conversation card (include_card, on by default): if the trigger has a conversation in context, attaches the card with a direct link into the Inbox (the same card the "Discuss in Team" button produces). Triggers without a conversation (e.g. tag.added or contact.created) just post the text, with no card.

Example

A workflow fires when the first-response SLA is breached. The Publish to Team node targets the "Support — Alerts" Space with the message "🔥 SLA breached on {{contact.first_name}}'s conversation" and include_card on, so the team sees the alert and can jump straight into the conversation from the card.

Tips

• The message is stamped with the workflow's ⚡ badge, so the team can tell it came from an automation.
• If you need to post later rather than right now, use the Schedule Team Message node instead.

Troubleshooting

• "Team space not found" or "is archived": the configured Space no longer exists or was archived — pick a different one from the node's inspector.
• "No organization context": the workflow had no resolvable organization at run time; contact support if this keeps recurring.
• Conversation card missing: check that the trigger that fired the workflow actually had a conversation attached — some triggers (tags, contacts) don't.