Control Automations From Your Phone

Automation from Anywhere

Pause, start, or check automations from your phone with a simple Telegram message. For a desktop automation tool, the desk can feel like a limitation. A workflow may need to start while you are at a client site, stop when a data source changes, or deliver a completion message while you are traveling. Remote execution removes that limitation.

RTILA X provides multiple remote control paths, from direct API triggers to message-based Telegram commands. All execution stays on your machine; only the control signal travels remotely.

API Triggers

The remote execution API lets external applications start, stop, or query an active workflow. You can send an HTTP request with authentication to trigger a run, check its status, or pause execution. This makes RTILA X easy to integrate into other software or internal dashboards.

For example, a spreadsheet script could start an automation when a new row is added. A monitoring system could check whether a scheduled run completed and then raise an alert if no data arrived. The API gives you programmatic access without exposing your local project files.

Webhook Integration

Webhooks flip the direction of control. Instead of calling RTILA X from an external tool, you configure a webhook URL that other systems can call when events occur. When the webhook receives a valid request, RTILA X starts the corresponding workflow.

This is useful for event-driven automations. A payment processor can notify RTILA X when a customer subscribes, a CRM can fire a webhook when a new lead is created, or a form service can trigger a data enrichment workflow on a schedule-free basis.

Cloudflared Tunnels

Cloudflared tunnels create a secure connection from your local RTILA X installation to a Cloudflare-managed endpoint. This allows remote access without exposing your machine directly to the public internet or requiring a cloud-hosted RTILA X worker.

The tunnel protects your local setup while still allowing external triggers and status checks. This pattern is popular with Agency and Enterprise users who want remote control without sacrificing local-first privacy.

Telegram Bot Daemon

The Telegram Bot Daemon gives RTILA X a conversational remote control. You configure a Telegram bot that you own, link it to your local installation, and use chat messages to start, stop, pause, resume, and check workflows.

You can send a command from your phone, receive a completion report in the same chat, and even ask the bot for the status of a scheduled run. The interaction feels natural because it happens inside a messaging app you already use.

The daemon runs locally, so Telegram is only used as the messaging layer. Your automation data is not uploaded to Telegram. The bot receives only the messages you configure, such as success summaries or error notifications.

Security Considerations

Remote execution expands convenience, so authentication matters. API triggers and webhooks should use secure tokens, and the Telegram bot should be protected by its own bot token and chat restrictions. RTILA X keeps control of these settings local, so you decide which remote channels are allowed.

Because the underlying automation remains on your machine, remote control does not expose project files or scraped datasets to a third-party server. The remote layer only carries commands and status messages, not the full workflow content.

Still Local-First

Your data and execution stay on your machine. Telegram acts only as your remote control channel. Remote execution extends control without moving your automation or your data to the cloud.