Start Windmill flows from new listenings on a Funkwhale instance.
Set up in 2 steps
Create an application
In Funkwhale, open Settings, then Applications, and create a new one. Copy its access token.
Add the resource in Windmill
Open Resources, add a resource of type funkwhale, and fill baseUrl with your instance. The token is optional — leave it empty for public reads.
Scripts
Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.
Trigger flows from Funkwhale
Funkwhale is not only a destination. These inbound paths are supported today.
New listenings (scheduled poll)
The Watch for new listenings trigger script polls the listening history and returns the entries added since its last run. To run it, open a flow, add a trigger and choose Scheduled Poll, then pick the trigger script and an interval. The steps after it run once per new item, and each flow keeps its own cursor.
Resource type
The shape of the credential every script on this page expects.
funkwhale
View raw schema →| Field | Type | Required | What it is |
|---|---|---|---|
| baseUrl | string | Yes | |
| token | string | No | An access token to act as a logged-in user. You can create an application by visiting /settings. Leave this empty, if you want to perform unauthenticated requests. |
Questions
Why is the token optional?
Public listening history answers unauthenticated requests. History that is not public needs a token.
Is my token stored on the hub?
Never. It lives only in your own Windmill workspace, encrypted at rest.