Integrations / Infrastructure
Tailscale
Put Murmurator on your tailnet, so workflows can reach services on your devices and home network without opening them to the internet, or send a workflow's requests out from one of your devices. Only what your tailnet's access rules allow is reachable.
Tools
tailscale.devices
List the devices on the tailnet, with their names, Tailscale addresses, whether they are online, and the subnet routes they advertise.
tailscale.get
Send a GET request to an address on the tailnet, such as http://nas:8080/api/status or http://192.168.1.20/ behind a subnet router, and return the response, parsed when it is JSON. Nothing outside the tailnet is reachable. For a service that needs a key, make an HTTP connection with this one as its tailnet.
Connect
- In the Tailscale admin console, open Settings → Keys and generate an auth key. A reusable key with a tag such as tag:murmurator lets you write access rules for it.
- Limit what the tag can reach in your access controls, e.g. only the devices and ports your workflows need.
- To reach a home network behind a subnet router, approve the router's routes; this machine accepts them.
- To send workflows' requests out from one of your devices, run tailscale set --advertise-exit-node on it, approve it as an exit node in the admin console, let the tag use it (a grant to autogroup:internet), and name it below as the exit node.
- Paste the key below and test the connection. Murmurator shows up as a machine with the name you choose.
Credentials
Examples
Bedtime house check — Every night, the house is checked, tidied up and reported on before you go to sleep.
Turn one person's AI process into the company's.
Murmurator is invite-only. Already invited? Sign in and build something real.