Actions15
- Video Actions
- Audio Actions
- Subtitle & Text Actions
- Transition Effects Actions
- Image Actions
- Font Management Actions
Overview
The node provides media processing capabilities focused on video, audio, images, subtitles, transitions, and fonts using FFmpeg. Specifically for the Font Management resource with the Upload Font operation, it allows users to upload custom fonts either from binary data within the workflow or from a local file path. This is useful when you want to add personalized fonts for use in video subtitles, text overlays, or other media transformations that require custom typography.
Typical scenarios include:
- Uploading a new font to be used later for adding subtitles or text overlays on videos.
- Managing project-specific fonts without relying on system-installed fonts.
- Automating font uploads as part of a larger media processing workflow.
Example: Upload a corporate brand font from a binary file attached earlier in the workflow, then use it to add branded subtitles to marketing videos.
Properties
| Name | Meaning |
|---|---|
| Font Source | Choose the source of the font data: - Binary Data: Upload font from binary data in the workflow. - File Path: Upload font from a local file path on disk. |
| 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). Required. |
| Font Name | Display name for the font (optional). |
| Description | Optional description for the font. |
Output
The output JSON contains a success flag, the operation name, and a data object describing the uploaded font details such as its key, name, description, and filename.
If the font upload is done via binary or file path, the node returns confirmation and metadata about the saved font.
No binary output is produced by this operation.
Example output JSON structure:
{
"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 fonts via file path.
- Uses internal utility functions to save and manage user fonts.
- No external API keys or services are required for font upload.
- The node depends on FFmpeg for broader media processing but not specifically for font upload.
Troubleshooting
Error: No binary data found in property 'X'
Occurs if the specified binary property does not exist or is empty in the input item.
Resolution: Ensure the binary data is correctly attached and the property name matches exactly.Error: Font file not found at path: /path/to/font.ttf
Happens if the file path provided does not exist or is inaccessible.
Resolution: Verify the file path is correct and accessible by n8n.Error: Font key validation failed
If the font key does not meet requirements (length or allowed characters).
Resolution: Use a font key between 3 and 50 characters, only alphanumeric, hyphens, or underscores.General file permission issues may prevent reading font files from disk.
If the operation does not produce output, ensure all required parameters are set and valid.
Links and References
- FFmpeg Official Site – underlying media processing tool used by the node.
- n8n Documentation – for general guidance on creating workflows and handling binary data.
- Font File Formats – background on common font file types like TTF, OTF.
This summary focuses exclusively on the Font Management - Upload Font operation extracted from the provided source code and property definitions.