Media library

The media library is the file catalog the bot’s media nodes (Image, Video, Document, Audio) draw from. Every file uploaded here flows through the same production pipeline: stored in object storage, scanned by an anti-virus engine, and only made downloadable once the scan reports clean.

Uploading a file

1. Settings → Media Library → + Upload file.
2. Pick a file from your machine. The upload starts immediately.
3. The file appears at the top of the list in Pending state while the scan runs. Scans complete in a few seconds for small files; large files may take longer.
4. Once the scan finishes, the row’s status updates to Clean, Infected, or Error.

The list refreshes automatically every five seconds while any file is still pending. Once everything is in a terminal state, polling pauses.

Scan statuses

• Pending — the file is queued for or actively being scanned. Downloads are blocked.
• Clean — the scanner found nothing. The download link works and the file is available to bot media nodes.
• Infected — the scanner flagged the file. CraftBot deletes the file from object storage immediately; only the audit row remains. The file cannot be used in any recipe.
• Error — the scanner failed to evaluate the file (network glitch, malformed payload). Re-upload, or contact the platform owner if it persists.

Filter the list by status using the chip row above the table. The default view shows everything.

Where uploaded files are used

• Bot media nodes — the Image, Video, Document, and Audio nodes in the recipe canvas pick from this library. Only clean files appear in the picker.
• Smart Plug responses — when a plug response references a file by ID, the agent panel resolves it against this library before rendering.

Deleting a file

Deleting a file marks it removed from the library and detaches it from any future recipe selection. Historical references in past conversations are preserved (the file metadata stays for audit even though the binary is gone from storage).

Best practices

• Re-upload rather than rotate. Once a file is referenced by a published recipe, replacing the binary at the same row risks breaking outbound messages that already serialized the old URL. Upload a new file, point the recipe at it, then delete the old row.
• Watch the Infected chip filter weekly during ramp-up. A spike usually means someone is uploading from a compromised laptop, not that the scanner is over-sensitive.
• Keep the library tidy. Old PDFs, draft mockups, and abandoned versions accumulate fast. Delete what bot nodes no longer reference.