Overview

This node provides multiple utility operations under the '4Jawaly Actions' resource, including detecting audio files within JSON data. The 'Detect Audio' operation scans JSON input to identify audio file URLs or audio-type objects, supporting common audio file extensions. It is useful for workflows that need to process or validate audio content embedded in JSON structures, such as extracting audio messages from chat data or media metadata.

Use Case Examples

1. Detect audio files in a JSON payload from a messaging app to trigger further audio processing.
2. Scan JSON data for audio URLs to download or transcribe audio files automatically.

Properties

Output

JSON

• success - Indicates if the operation was successful.
• operation - The operation performed, here always 'detectAudio'.
• hasAudio - Boolean indicating if any audio files were detected.
• audioType - Type of audio detected, e.g., 'audio' or 'file'.
• audioFilesCount - Number of audio files found in the JSON data.
• audioFiles - Array of detected audio files with their URLs, JSON paths, and file extensions.
• firstAudioUrl - URL of the first detected audio file, or null if none found.
• message - Message in Arabic indicating presence or absence of audio.
• message_en - Message in English indicating presence or absence of audio.

Dependencies

• An API key credential is required for some other operations in the node, but not for 'Detect Audio'.

Troubleshooting

• If the JSON Path is incorrect or points to a non-existent path, no audio files will be detected. Verify the JSON Path or leave it empty to search the entire JSON.
• If the JSON data does not contain supported audio file extensions or audio-type objects, the node will report no audio found.
• Ensure the input JSON is well-formed and accessible to avoid errors during parsing.