Make.com: Common issues#

When working with JSON2Video and Make.com, you might encounter a few common issues. Here's a guide to help you troubleshoot them:

1. "Source URL is required for video element in Scene #, Element #" Error#

• Cause: This error typically arises when creating video or image elements without providing a value for the src property.
• Solution:
  • Ensure that the src property is included in your JSON and that it contains a valid URL for your media file.
  • Double-check your Make.com variable mappings. If you're using a variable to populate the src property, confirm that the variable is resolving correctly and that the mapped value exists at runtime. If a variable mapping fails, the src property may be sent as an empty string to JSON2Video, triggering this error.

2. Movie duration cannot be zero#

• Cause: The total duration of the video can't be less than 1 second. The different reasons for this to happen are:
  • You have one or multiple images in a scene and any of them have an explicit duration, AND the scene or movie does not have a duration
  • The elements or scenes in the movie are too short (less than a second)
  • The movie has no elements or scenes
• Solution:
  • If you are using one or multiple images, add the property "duration" to the scene or movie.
  • Confirm that the duration of the video is more than 1 second

3. The URL provided is not a [video/audio/image] file and cannot be used as a source for a [video/audio/image] element#

• Cause: You are using the wrong type of resource or the wrong file extention.
• Solution:
  • Video element can use "h264", "hevc", "mpeg4", "wmv3", "vp8", "vp9", "mpeg2video", "av1", "theora"
  • Audio element can use "aac", "flac", "mp3", "opus", "vorbis", "h264", "mpeg4", "wmv3", "vp8", "vp9", "mpeg2video", "av1", "theora"
  • Image element can use "png", "jpg", "jpeg", "gif", "mjpeg", "bmp", "tiff", "webp"

4. Incorrect JSON Structure#

• Cause: Make.com transfers data as a string. If your JSON structure includes unescaped characters, or the data is not correctly serialized it may result in errors.
• Solution:
  • Ensure that your JSON structure is valid and properly formatted.
  • Use Make.com's parseJson() function to ensure your string data is parsed into correct JSON.

5. API Key Issues#

• Cause: Invalid or missing API key.
• Solution: Double-check that you've correctly entered your JSON2Video API key in the Make.com connection settings. Ensure you are using the correct API key associated with your JSON2Video account.

6. Rate Limiting#

• Cause: Exceeding the API request limit.
• Solution: Be mindful of the API rate limits. Implement error handling and retry mechanisms to gracefully handle rate limit responses. If you consistently require a higher rate limit, contact JSON2Video support to discuss options.

7. Webhook issues#

• Cause: The webhook endpoint MUST BE HOSTED PUBLICLY on your server and have a valid SSL certificate.
• Solution: Check that your webhook is hosted in a public URL and has a valid SSL certificate

8. Make.com variable mapping issues#

• Cause: Make.com variable mapping is not correctly configured.
• Solution: Check that all the JSON2Video module attributes are correctly mapped.

Debugging Tips#

• Examine Make.com Execution History: Use the execution history in Make.com to inspect the data being sent to the JSON2Video API. This can help you identify incorrect values or formatting problems.
• Use the JSON2Video API Tester: Test your JSON payloads directly with the JSON2Video API to isolate any issues with your JSON structure or data.
• Consult the JSON2Video API Documentation: Refer to the JSON2Video API documentation (and especially the list of API Errors) for detailed information on request parameters and expected responses.

By systematically addressing these common issues, you can ensure a smoother workflow between Make.com and the JSON2Video API.