MediaFX icon

MediaFX

Process videos, audio, and media files with FFmpeg

Actions13

Overview

The node provides functionality to upload custom fonts into the MediaFX environment, allowing users to add personalized typography for video and media processing workflows. It supports uploading font files either from binary data within the workflow or from a local file path on the system.

This node is beneficial when you want to use specific fonts that are not included by default in MediaFX for tasks such as adding text overlays, subtitles, or other text-based effects in videos or images. For example, you might upload a corporate brand font to ensure consistent branding across all video content processed in your automation.

Properties

Name Meaning
Font Source Choose the source of the font file:
- Binary Data: Upload font from binary data in the workflow.
- File Path: Upload font from a local file path.
Binary Property (Shown if Font Source is Binary Data) The name of the binary property containing the font data. Default is "data".
File Path (Shown if Font Source is File Path) Local file path to the font file to upload, e.g., /path/to/font.ttf.
Font Key Unique identifier for the font (3-50 characters; alphanumeric, hyphens, underscores). This key is used to reference the font later. Required field.
Font Name Display name for the font, e.g., "My Custom Font". Optional descriptive name shown in UI.
Description Optional description for the font, e.g., "Custom font for special projects".

Output

The node outputs JSON data indicating the success of the upload operation along with details about the uploaded font. The output JSON includes:

  • success: Boolean indicating if the upload was successful.
  • operation: The operation performed, here always "upload".
  • data: An object containing information about the saved font, such as its key, name, description, and filename.

No binary data is output by this node during font upload.

Example output JSON:

{
  "success": true,
  "operation": "upload",
  "data": {
    "fontKey": "my-custom-font",
    "fontName": "My Custom Font",
    "description": "Custom font for special projects",
    "fileName": "font.ttf"
  }
}

Dependencies

  • Requires access to the local filesystem if uploading via file path.
  • Uses internal helper functions to save the font data persistently.
  • No external API keys or services are required for the upload operation.
  • The node depends on n8n's binary data handling capabilities when uploading from binary.

Troubleshooting

  • No binary data found in property 'X': Occurs if the specified binary property does not exist or contains no data when uploading from binary. Ensure the binary property name matches the actual binary data property in the input item.
  • Font file not found at path: /path/to/font.ttf: Happens if the provided file path does not exist or is inaccessible. Verify the path is correct and accessible by n8n.
  • Invalid font key: The font key must be unique, 3-50 characters long, and contain only alphanumeric characters, hyphens, or underscores. Use a valid key format.
  • If the node fails without clear error, check permissions for reading files or writing font data storage.

Links and References

Discussion