Get Movie
AI-generatedOverview
The node integrates with The Movie Database (TMDb) API to retrieve detailed information about movies, collections, companies, persons, TV shows, and movie lists. It is useful for workflows that require enriching data with movie-related metadata, such as building entertainment apps, content recommendation systems, or media cataloging tools.
Specifically, the "Get Movie" operation fetches detailed information about a specific movie by its ID, optionally including additional related data specified via the "Append to Response" parameter. This allows users to obtain comprehensive movie details in a single request.
Practical Examples
- Fetching detailed movie information to display on a website or app.
- Retrieving movie metadata for cataloging or archival purposes.
- Enriching user profiles with favorite movie details.
- Integrating movie data into chatbots or recommendation engines.
Properties
| Name | Meaning |
|---|---|
| Language | The language code (e.g., "en") to localize the returned movie information. |
| Movie ID | The unique identifier of the movie to retrieve. |
| Append to Response | Additional related data to include in the response, such as credits, images, or similar info. |
Output
The node outputs JSON data containing detailed information about the requested movie. This includes standard movie metadata such as title, release date, overview, genres, cast, crew, ratings, and any additional appended data specified by the user.
If the "Append to Response" property is used, the output JSON will also include those extra fields as defined by TMDb's API (e.g., credits, videos, images).
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating requests to The Movie Database (TMDb) API.
- No other external dependencies are needed.
- The node expects proper configuration of this API key within n8n credentials.
Troubleshooting
Common Issues:
- Invalid or missing Movie ID: The node requires a valid numeric movie ID; otherwise, the API call will fail.
- Incorrect API key or authentication failure: Ensure the API key credential is correctly set up.
- Network or API rate limiting errors from TMDb.
Error Messages:
- Errors thrown by the node will include context about the item index causing the failure.
- If "Continue On Fail" is disabled, the workflow execution stops on error.
- To resolve errors, verify input parameters, ensure valid IDs, and check API key validity.