Get upcoming

Use this action to retrieve upcoming episodes from the calendar. Episodes are returned when their air date falls between today and today plus the number of days you specify.

This action returns its result in a response variable, which you can use in later steps of the same automation or script, for example to send yourself a weekly overview of what’s coming up.

Using this action from the user interface

If you prefer building automations and scripts visually, Home Assistant walks you through this action step by step. You pick what to target, tweak a few options, and save. No YAML knowledge required.

To get the upcoming episodes from an automation or a script:

  1. Go to Settings > Automations & scenes.
  2. Open an existing automation or script, or select Create automation > Create new automation.
  3. If you’re setting up a new automation, add a trigger in the When section. Scripts don’t need a trigger. They run when something else calls them.
  4. In the Then do section, select Add action.
  5. From the search box, search for and select Sonarr: Get upcoming.
  6. Select the Sonarr entry to query and optionally set the number of Days to look ahead.
  7. In the Response variable field, enter a name to store the data in, such as upcoming_data.
  8. Select Save.

This action does not support targets. In the UI, you are not prompted to choose an area, device, entity, or label.

Options in the UI

Sonarr entry (Required)

The Sonarr config entry to query.

Days (Optional)

The number of days to look ahead for upcoming episodes. The valid range is 1 to 30. The default is 1.

Using this action in YAML

If you work directly in YAML, or you want to know exactly what Home Assistant does under the hood, this section has the technical reference. It lists the field names you use in YAML, their types, and which ones are required.

In YAML, refer to this action as sonarr.get_upcoming. Store the result in a response variable so you can use it in later steps:

ActionActions are used in several places in Home Assistant. As part of a script or automation, actions define what is going to happen once a trigger is activated. In scripts, an action is called *sequence*. [Learn more]
action: sonarr.get_upcoming
data:
  entry_id: "01234567890abcdef1234567890abcde"
  days: 7
response_variable: upcoming_data

This fetches the episodes airing in the next 7 days.

Options in YAML

entry_id string Required

The Sonarr config entry to query.

days integer

The number of days to look ahead for upcoming episodes. The valid range is 1 to 30.

Response data

The response contains an episodes key with a mapping of upcoming episodes keyed by series title and episode identifier, for example Breaking Bad S01E01. Each episode includes the following fields:

  • id: Internal episode ID.
  • series_id: Internal Sonarr series ID.
  • season_number: Season number.
  • episode_number: Episode number.
  • episode_identifier: Formatted identifier, such as S01E01.
  • title: Episode title.
  • air_date: Air date in local time.
  • air_date_utc: Air date in UTC.
  • overview: Episode overview or description.
  • has_file: Whether the episode file exists.
  • monitored: Whether the episode is monitored.
  • runtime: Episode runtime in minutes.
  • finale_type: Finale type, if applicable, such as series or season.
  • series_title: Series title.
  • series_year: Series premiere year.
  • series_tvdb_id: Series TheTVDB ID.
  • series_imdb_id: Series IMDb ID.
  • series_status: Series status.
  • network: Network the series airs on.
  • images: Mapping of series image URLs by type, including poster, banner, fanart, and clearlogo.

A shortened example of the response looks like this:

episodes:
  "The Rookie S08E03":
    id: 2008
    series_id: 50
    season_number: 8
    episode_number: 3
    episode_identifier: "S08E03"
    title: "The Red Place"
    air_date: "2026-01-20 00:00:00"
    air_date_utc: "2026-01-21 03:00:00+00:00"
    overview: >-
      Nolan makes a quiet arrest, and Lucy and Celina race to rescue a
      kidnapping victim.
    has_file: false
    monitored: true
    runtime: 0
    series_title: "The Rookie"
    series_year: 2018
    series_status: "continuing"
    network: "ABC (US)"

Try it yourself

Ready to test this? Open Developer tools > Actions, search for this action, fill in the fields, and select Perform action. You see what happens on your actual entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] without writing a line of YAML.

Still stuck?

The Home Assistant community is quick to help: join Discord for real-time chat, post on the community forum with the action you’re calling and what you expected to happen, or share on our subreddit /r/homeassistant.

Tip

AI assistants like ChatGPT or Claude can also explain actions or suggest the right one when you describe what you want in plain language.

Related actions

These actions work well alongside this one:

  • Get series: Retrieves all series in your Sonarr library with their details and statistics.

  • Get episodes: Retrieves all episodes for a specific series in your Sonarr library.

  • Get wanted: Retrieves wanted (missing) episodes that Sonarr is searching for.