Channel automations

What it is

Channel automations are the automation pipeline that runs over the messages coming into Omniscio from your connected messaging channels — Gmail, SMS, Slack, Telegram, incoming webhooks and similar. When a message arrives, Omniscio tests it against your rules; a matching rule runs its actions in order, and those actions can reply, label or archive, summarize with AI, forward, send an outbound request, or start a new AI session.

This page is the map of that area. It points you to the pages that own each part: the rule pipeline itself (its conditions and its action chain), the template variables you can drop into an action, the ways you author a rule — including describing it in plain English or starting from a preset — the limits that keep a noisy trigger from flooding a channel, and the log that records what each run did.

Where to find it

• The Automations surface — a virtual project in the left sidebar, next to Quick Replies, holding your Rules and Auto-replies in two collapsible sections with a + New rule button; each rule is edited inline in its list row.
• The Automation group — a collapsible sidebar group that nests Automation Helper, Cron Jobs, Recipes, Automations, Quick Replies and Scheduled Messages together.
• Team Chat — right-click a channel and choose Session Bot to configure a per-channel bot for that one channel.
• The Marketplace — the Automations tab, where automations can be shared and imported.
• Settings — the Automation Builder and the Automation Credentials manager are each reached from their own entry.

How it behaves

Each part of the area is owned by its own page:

• The pipeline and the rule editor — conditions (with operators and AND/OR logic), an ordered chain of up to ten actions, four trigger types, rule scoping, backtest and AI reply review: Automations & Auto-replies (auto-respond to messages).
• Template variables — an action can interpolate the incoming message's {{sender}}, {{body}}, {{channel}} and {{subject}} into its prompt or payload: Automations & Auto-replies (auto-respond to messages).
• The run record — the per-step activity log a run leaves behind, and the badge taxonomy that names which automated path produced a message: Automations & Auto-replies (auto-respond to messages) (part 2).
• The lightweight half — rules that watch a session's own finished output and fire a single action, rather than reacting to a channel message: Auto-replies (auto-respond to a session's own output).
• Plain-English authoring and presets — the in-app assistant that interviews you and then builds, schedules and registers a real automation: Automation Builder.
• The secrets the actions use — stored API tokens, webhook URLs, service-account keys and SMTP passwords that actions resolve at run time: Automation Credentials (saved secrets for v2 actions).
• Sharing rules — exporting an automation as copy-paste code or publishing it to the shared catalog: Share automations (the automation marketplace).
• A per-channel bot inside Team Chat — the keyword-driven Session Starter Bot, with its own target project and daily rate limit: Session Starter Bot.
• Where the pieces sit in the sidebar — Automation group (sidebar).

Related

• Automations & Auto-replies (auto-respond to messages) — the rule pipeline over channel messages, its conditions and its action chain.
• Automations & Auto-replies (auto-respond to messages) (part 2) — the activity log and the auto-response badge taxonomy.
• Auto-replies (auto-respond to a session's own output) — the single-action rules that watch a session's output.
• Session Starter Bot — the per-channel Team Chat bot that spawns sessions from keywords.
• Automation Builder — building an automation by describing it in plain English.
• Automation Credentials (saved secrets for v2 actions) — the saved secrets the v2 actions resolve at run time.
• Share automations (the automation marketplace) — sharing and importing automations.
• Automation group (sidebar) — the sidebar group that holds the automation features.