Loading...
Rundown Studio
This module uses the Rundown Studio API v1. Learn more about our API on our documentation.
You will need to enter your API Token. API tokens can be generated from within the Rundown Studio dashboard in the API Section. Only team admins can generate and regenerate these tokens, however anyone on your team can read and use the token.
You will also need the ID of your particular Rundown that you wish to use in this module. You can retrieve this ID by opening a rundown and looking at the URL of the page. For example: https://app.rundownstudio.app/rundown/<rundown_id>
If necessary, there is an Advanced Configuration area of the module which allows you to configure the following:
Normal operation does not require modification of these values and they should be left alone unless you have been instructed otherwise. The API Base URL serves both the REST endpoints and the live event stream, so pointing it at another environment moves the whole module there.
The following Actions are available:
The following Feedbacks are available:
The following Variables are available:
Dynamic variables are also created for each public column on the rundown. A column named AUDIO becomes currentcue_audio and holds the plain-text cell content of the active cue in that column. Column titles are lowercased and non-alphanumeric characters become underscores. If a name would collide with a built-in variable (e.g. a column called Title), a numeric suffix is added (currentcue_title_2).
The following Presets are available:
This version of the module talks to the Rundown Studio API v1. Existing configurations are migrated automatically when the module is upgraded:
https://api-v1.rundownstudio.app). A custom URL, such as a development environment, is left as you set it.Ended rundown state are switched to Stopped. The v1 API reports a single stopped state that covers both pre-show and post-show.