Warudo: Trigger Action
Published 11 Sept 2026
Fires an On WebSocket Action node in a Warudo blueprint, so anything you can build in Warudo can be set off by a tip, a sub or a chat command.
Warudo needs no plugin, no restart and no account in TipLink. There is nothing under Platforms to connect. Add this action to an alert and it works.
What You Need
- Warudo, running on the same PC as TipLink, or reachable on your network
- One On WebSocket Action node in a blueprint, set up as below
Set Up the Node in Warudo
- In Warudo, open a blueprint. In the Palette on the right, search for
websocketand click On WebSocket Action, under External Integration. - Set that node's Action to
TipLinkAlert. - Connect the node's Exit to whatever you want to happen.
That is the whole setup. The node is first-party, so there is no Workshop plugin to install.
Warudo does nothing at all when the Action name does not match, and reports no error. If your alert seems to do nothing, check the node's Action against the Action Name in TipLink, character for character.
Each distinct action name needs its own node in Warudo. Give each one a name you will recognise later, such as Tip_Small and Tip_Big.
Configuration Options
| Option | What it does | Default |
|---|---|---|
| Action Name | Must match the Action on an On WebSocket Action node in Warudo, exactly. Accepts placeholders. | TipLinkAlert |
| Host | Only change this if Warudo is on another computer. | 127.0.0.1 |
| Port | The port Warudo listens on. Leave it unless you changed it in Warudo. | 19190 |
The default Action Name matches the node the steps above walk you through, so a brand new alert works straight away.
Leaving Port blank means "use the default", not an error.
Pick a node from event data
Action Name accepts placeholders, so one action can choose its node at runtime:
Tip_{{ platform }}
That fires Tip_twitch, Tip_fansly and so on, letting one alert drive a different blueprint branch per platform. Each of those names still needs its own node in Warudo.
Testing It
There is no test button, because there is no connection to test. Verify it by running the alert the action belongs to, using Test Actions from the alert's ⋮ menu. A send that fails surfaces as a normal action failure.
Troubleshooting
Nothing happens in Warudo. Almost always a name mismatch. Check the node's Action against Action Name. Both are case-sensitive.
It worked, then stopped. Check Warudo is still running, and that the blueprint holding your node is the active one.
Warudo is on another PC.
Set Host to that machine's address. Make sure port 19190 is reachable through its firewall.
What Is Not Sent
TipLink sends the action name and nothing else. Warudo's node has a Data Type dropdown that adds an output port for a value, but the JSON key that would carry that value is not documented, so TipLink does not guess at it. Your node fires either way; it just will not receive a value alongside the trigger.
To pass data in, use the alert to compute what you need and put it in the action name, or drive the rest from within the blueprint.