updates.humandnai.xyz
← Back

Run automations where the work is already happening

How-To

Run automations where the work is already happening
SUMMARY: Inline workflows turn chat into an operational control surface by letting users run, confirm, monitor, reload, save, and schedule automations without leaving the conversation, reducing friction and making repeatable work easier to manage. Built-in Telegram support closes the loop by delivering workflow outputs directly to users’ DMs or even triggering workflows from Telegram, creating a faster chat-to-action-to-delivery workflow.

Inline workflows make chat more useful for real operational work. Instead of leaving the conversation, opening the workflow builder, finding an existing automation, and running it from another screen, users can trigger workflows directly inside client chat.

This changes chat from a place that only generates content into a place that also runs actions.

Repeatable tasks should feel easy to start, easy to monitor, and easy to revisit. Inline workflows reduce friction for non-technical users, keep operational steps visible, and make it simpler to move from idea to action without breaking focus.

What inline workflows actually do

Inline workflows let users trigger operational automations directly from chat. The system detects a workflow command before normal chat processing begins, resolves the workflow by name or ID, and presents a confirmation step before execution.

From there, the workflow runs through the existing execution system, while chat shows a dedicated run-state experience designed for actions rather than generated prose.

Users can:

  • Run a workflow
  • Load a previous workflow result back into chat
  • Save workflow output to the Knowledge Base
  • Schedule a workflow with cron-style timing
  • Review workflow execution status without leaving chat

The result is a cleaner, more confident operational flow. Workflow activity stays visually distinct from ordinary assistant replies, so users can immediately tell what is being run, what is in progress, and what has completed.

Why this matters for everyday use

For teams already working in chat, every extra click adds drag. Inline workflows remove that drag.

They help users:

  • Launch repeatable tasks faster
  • Stay in one working context
  • Confirm actions before execution
  • Monitor progress without opening another tool
  • Reopen useful outputs directly in chat
  • Save valuable results into the Knowledge Base for reuse

This is especially helpful for operational and strategy work that happens often, such as reporting, monitoring, research, planning, and delivery workflows.

Instead of treating automation like a separate system, inline workflows make it feel like a natural extension of the conversation, while still preserving clear boundaries between chat replies and workflow actions.

How the inline workflow flow works

The experience is designed to be simple, visible, and easy to trust.

1. Start from chat

The user can either type a workflow command manually or choose a workflow from the inline Workflows picker.

For article-safe wording, commands can be described like this:

  • open bracket WORKFLOW RUN LinkedIn Strategy - Telegram close bracket
  • open bracket WORKFLOW RUN Weekly Brand Monitor close bracket
  • open bracket WORKFLOW RUN Daily Research Summary with topic AI agents and audience founders close bracket

2. Confirm before execution

Before anything runs, the chat surfaces a confirmation card. This creates an intentional pause, which helps users verify they are triggering the right workflow with the right target.

3. Watch progress inline

Once confirmed, the workflow executes through the existing system. Progress appears in chat inside a dedicated operational card, not as a normal assistant draft or generated reply.

Workflow actions should feel operational, not conversationally ambiguous.

4. Act on the result

When the run finishes, the user can choose what to do next.

They can:

  • Load the result into chat
  • Save the output to the Knowledge Base
  • Dismiss the completed workflow card

This keeps the workflow loop practical and lightweight, especially for work that needs review, follow-up, or reuse.

A better operational UX inside chat

Inline workflow commands are intentionally separate from the standard assistant response flow.

They do not behave like a normal AI content reply, and they do not rely on the usual draft-marker experience. Instead, the interface uses specialised operational UI components that are easier to scan and easier to trust.

The experience includes:

  • A confirmation card before execution
  • A live progress card during execution
  • Assistant or system follow-up messages for success, cancel, load, save, and schedule actions

This separation helps users understand what is happening at a glance. It reduces confusion, improves confidence, and makes workflow activity easier to monitor in busy chat threads.

What users can do inline, beyond running workflows

Running a workflow is only the start. Inline actions become much more useful when users can continue working with results immediately.

Load previous outputs back into chat

Users can reopen a completed run and continue from it without digging through another interface.

Example phrasing:

  • open bracket WORKFLOW LOAD Weekly Brand Monitor close bracket
  • open bracket WORKFLOW LOAD with executionId abc-123 close bracket

This supports faster review loops and makes prior workflow runs easier to build on.

Save useful outputs to the Knowledge Base

If a workflow produces something worth keeping, users can save it directly into the Knowledge Base.

Example phrasing:

  • open bracket WORKFLOW SAVE Weekly Brand Monitor close bracket
  • open bracket WORKFLOW SAVE with executionId abc-123 close bracket

This is especially useful for research summaries, monitoring digests, planning outputs, and reusable internal documents.

Schedule recurring workflow runs

Users can also schedule workflows inline for repeatable operational tasks.

Example phrasing:

  • open bracket WORKFLOW SCHEDULE Weekly Brand Monitor with cron 0 9 any any 1 and timezone America/New_York close bracket

This makes chat a practical entry point not just for one-off runs, but also for recurring automation setup.

Strong use cases for a how-to workflow flow

Inline workflows are most valuable when the work is repeated often enough to deserve less friction.

Strong examples include:

  • Running a weekly brand monitor from chat
  • Launching a daily research summary without opening the automations page
  • Saving a useful workflow result to the Knowledge Base after review
  • Reloading a previous workflow run into chat to continue working from it
  • Scheduling a recurring workflow for a fixed time each week
  • Using a chat-first workflow flow for repeatable strategy, reporting, and delivery tasks

These are practical jobs people already do. Inline workflows simply make them easier to start and easier to manage.

The standout example: LinkedIn Strategy - Telegram

One of the clearest examples is a workflow named LinkedIn Strategy - Telegram.

The user starts inside client chat and triggers it with a lightweight workflow command:

  • open bracket WORKFLOW RUN LinkedIn Strategy - Telegram close bracket

From there, the workflow can:

  • Take a strategy request
  • Generate LinkedIn positioning or post ideas
  • Structure the output through workflow steps
  • Send the final result directly to the user’s linked Telegram DM

This is a strong example because it shows both sides of the value.

Chat becomes the launch point, and Telegram becomes the delivery layer.

The user does not need to bounce between systems, copy outputs manually, or keep checking the dashboard. They can trigger the automation where they are already working, monitor it inline, and receive the result where they are likely to see it quickly.

Telegram is built in, not bolted on

Telegram support is especially powerful because it is built into the workflow system as a native platform capability.

It is not treated like a normal user-connected MCP service. It uses the shared platform Telegram bot and the user’s linked Telegram identity, so the user does not need to complete a separate Telegram OAuth flow through the MCP Services UI.

This makes Telegram much easier to use in workflow design and delivery.

Telegram can serve as both:

  • A workflow trigger source
  • A workflow delivery destination

That dual role makes it useful for both starting and finishing automations.

Telegram workflow nodes

Telegram support is handled through dedicated workflow nodes.

telegram_trigger

This node starts a workflow when an inbound Telegram DM arrives. It passes Telegram message context into the workflow, which makes it useful when Telegram itself should initiate the automation.

telegram_send

This node sends workflow-generated output to the workflow owner’s linked Telegram DM. It works well for final content, summaries, alerts, and updates. It can continue an existing thread or start a new one.

telegram_reset_thread

This node clears the current Telegram conversation link. The next Telegram message begins a fresh thread, mirroring the Telegram bot’s /new reset behaviour.

Together, these nodes make Telegram a practical part of the same workflow engine, not a separate workaround.

Why Telegram adds real value

Telegram extends inline workflows beyond the dashboard and into the places where people actually pay attention.

That matters for speed and adoption.

Telegram is especially valuable because it:

  • Makes outputs more immediate
  • Supports a low-friction, mobile-friendly workflow loop
  • Works well for summaries, digests, alerts, and strategy outputs
  • Allows workflows to start from a real inbound user message
  • Extends automation beyond the web app while using the same workflow engine

For many users, the fastest workflow is the one that reaches them without asking them to go looking for it.

Best use cases for Telegram delivery

Telegram fits especially well when the output is useful, timely, and easy to consume on mobile.

Good examples include:

  • LinkedIn strategy delivery
  • Daily briefs
  • Research summaries
  • Weekly monitoring digests
  • Internal alerts
  • Mobile-first review workflows
  • Lightweight executive updates
  • Content planning outputs sent straight to Telegram

These are all cases where convenience drives actual usage. When delivery is simple, workflows become part of the routine instead of another system people mean to check later.

A simple end-to-end Telegram workflow example

Here is the flow in practice:

Start in client chat

A user wants LinkedIn strategy support and triggers the LinkedIn Strategy - Telegram workflow from chat.

Confirm and monitor

The chat presents a confirmation card, then shows a live progress card while the workflow runs.

Deliver outside the dashboard

Instead of leaving the output inside the app, the workflow uses telegram_send to deliver the result directly to the user’s linked Telegram DM.

Continue if needed

If the user wants to keep working from the result, they can reopen it in chat, save it to the Knowledge Base, or rerun the workflow with a refined prompt.

This creates a faster and more practical loop from request to result.

The bigger shift: chat becomes a working layer for automation

The real value of inline workflows is not only convenience. It is clarity.

Users get a chat-first way to run operational tasks, while the product keeps those tasks visibly separate from normal assistant conversation. That balance matters. It makes the experience feel lighter without making it confusing.

Add Telegram to that model, and the workflow loop gets even stronger.

Users can:

  • Trigger from chat
  • Monitor in chat
  • Receive outputs in Telegram
  • Reopen or save results when needed

This supports a more natural workflow for modern teams, especially when the work includes repeatable strategy, reporting, delivery, and mobile review.

Final thought

Inline workflows reduce clicks and context switching. They make automation usable from the same chat surface where users already work. Telegram expands that experience from in-app execution to real-world delivery.

Together, inline workflows and Telegram create a faster loop for triggering, monitoring, and receiving automation results, with less friction, more clarity, and a much better fit for how people actually work.