Seamlessly automate your private asset management by integrating RAILGUN Privacy Wallet with Telegram Bot via B3OS. Orchestrate shielded transfers and private gas funding through secure, automated messaging workflows directly from your favorite chat interface.
This workflow monitors the assets in your wallet, identified the top-performing tokens and then scans Twitter for any breaking/interesting news regarding those tokens. A recap is then sent to you via Telegram. This allows you to monitor you portfolio and be notified if a specific asset you hold has any pertinent news come out on Twitter for you to be aware of without having to monitor and scan Twitter yourself ### Quick Setup: 1. Select the wallet you want monitored 2. Select how often/when and what time you want a recap set to you 3. Select the Telegram channel you want the recap sent to 4. Test and Publish!
Send Telegram Message
ActionSend a text message to a Telegram chat using a bot token. Supports Markdown formatting (bold, italic, code, links). Uses the same bot token configured for receiving Telegram messages. Ideal for: chat replies, alerts, notifications, automated responses to Telegram triggers.
Telegram Chat Message
TriggerTriggers when a new message is posted in a Telegram chat or group. Connect your Telegram bot, then add the bot to your chat.
Railgun Relayer Unshield
ActionGasless unshield ERC20 tokens from Railgun private balance to any public address. B3OS relayer pays gas; fee deducted from token amount. No ETH required on recipient. Ideal for: anonymous gas funding, fresh wallet funding, privacy-preserving distributions.
RAILGUN Query Balance
ActionQuery private token balances in a RAILGUN wallet. Returns all ERC20 token balances or a specific token balance. Ideal for: pre-flight validation, UI display, balance verification, unshield planning.
Telegram: Button Click / Interaction
TriggerTriggers when a user clicks an inline keyboard button in a Telegram message. Useful for building approval workflows and interactive automations via Telegram bots. NOTE: Currently designed for wait nodes only (not as a root trigger). Frontend has no dedicated trigger config UI for this type yet.
