Marketing Architects icon

Marketing Architects

Consume Marketing Architects API
Join our community

Actions7

Overview

The node integrates with the Marketing Architects API to analyze videos from a given URL. It sends the video URL to the API, which performs an analysis and returns insights or metadata about the video content. This operation is useful for scenarios such as extracting key information from marketing videos, generating summaries, detecting objects or scenes, or gathering analytics data.

Practical examples include:

  • Automatically analyzing promotional videos to extract highlights or detect brand logos.
  • Processing user-uploaded videos to generate descriptive metadata for search indexing.
  • Monitoring video content for compliance or quality assurance by analyzing visual and audio elements.

Properties

Name Meaning
Video URL The URL of the video to analyze. Example: https://example.com/video.mp4

Output

The node outputs JSON data containing the results of the video analysis returned by the Marketing Architects API. This typically includes structured metadata, insights, or detected features extracted from the video.

If the API provides binary data (e.g., thumbnails or processed video clips), it would be included in the binary output fields, but this node primarily focuses on JSON response data describing the analysis.

Dependencies

  • Requires an active connection to the Marketing Architects API.
  • Needs an API authentication token configured in the node credentials to authorize requests.
  • The node makes HTTP POST requests to the endpoint /video/analyze of the Marketing Architects API base URL.

Troubleshooting

  • Common issues:

    • Invalid or inaccessible video URL: Ensure the provided URL is publicly accessible and points directly to a valid video file.
    • Authentication errors: Verify that the API token credential is correctly set up and has not expired.
    • Network connectivity problems: Confirm that the n8n instance can reach the Marketing Architects API endpoint.

  • Error messages:

    • Authorization failures usually indicate missing or invalid API tokens; reconfigure credentials.
    • HTTP 400 or 422 errors may mean the video URL is malformed or unsupported format.
    • Timeout or network errors suggest connectivity issues or slow API responses.

Resolving these typically involves checking input URLs, refreshing credentials, and ensuring stable internet access.

Links and References

Discussion