Appearance
Assets
TL;DR:
- Upload reusable images, videos, audio, and files once at the workspace level.
- Use the same asset across message cards, scenarios, and template installs.
- You cannot delete an asset while it is still used by a published scenario.
Who this is for
- Bot builders who need reusable media inside message flows.
- Workspace admins tracking storage usage and clean file naming.
- Teams installing templates that depend on shared assets.
What you will learn
- Which file types the platform accepts.
- How uploads, previews, and deletion rules work.
- How asset storage connects to billing limits.
Overview
The Assets area is your shared media library for the workspace. Instead of uploading the same image or PDF every time you edit a scenario, you upload it once and reuse it anywhere it is needed.
Assets are stored at the workspace level, not inside a single bot. That makes them easier to reuse across multiple scenarios and keeps template installs more predictable.
Key concepts
- Asset - A reusable uploaded file such as an image, video, audio file, or document.
- Kind - The media category the platform assigns after validating the file.
- Usage - Whether the asset is currently referenced by published scenarios.
- Storage limit - The total asset storage allowed by your billing plan.
How it works
- Open Assets and upload a file or drag it onto the page.
- The platform validates the file type, extension, size, and basic integrity before storing it.
- The uploaded asset becomes available for reuse in supported nodes and template installs.
- If the asset is referenced by a published scenario, deletion is blocked until you remove it from the live flow.
TIP
Use clear file names before upload so teammates can identify assets quickly.
WARNING
Removing an asset from a draft is not enough. If the published scenario still references it, the asset stays protected from deletion.
In the UI
The Assets page gives you both library management and quick visibility into storage usage.
- Location: Assets in the main workspace navigation.
- Main controls:
- Upload - Add new files manually.
- Drag and drop - Drop one or more files directly onto the page.
- Grid / Table view - Switch between a visual card layout and a denser list.
- Preview - Inspect the selected file before reuse.
- Usage - See which published scenarios depend on an asset.
Supported file kinds and limits
| Kind | Typical use | Default max size | Allowed formats |
|---|---|---|---|
| Image | Message cards, visual content | 20 MB | jpg, jpeg, png, webp, gif |
| Video | Rich media cards | 100 MB | mp4, webm, mov |
| Audio | Voice or music content | 50 MB | mp3, m4a, ogg, wav, webm |
| File | Documents and downloads | 50 MB | pdf, zip, txt, md, json, csv, docx, xlsx, pptx |
The upload validator also blocks risky file types such as executable files, HTML, SVG, shell scripts, and JavaScript payloads.
Examples
Example 1 - Reuse one image in multiple scenarios
Goal: Show the same product banner in a welcome flow and a promotional broadcast.
Setup: Upload the banner once in Assets, then select that asset in both message cards.
Result: Updating the flow no longer requires duplicate uploads, and the team can find the file in one place.
Example 2 - Install a template that needs media
Goal: Start from a scenario template that includes example assets.
Setup: Install the template and review the generated asset dependencies in the pre-install preview.
Result: The scenario is created faster, and you can swap placeholder media before publishing.
Troubleshooting
Symptom: Upload fails immediately
Cause: The file type, extension, or size does not pass validation.
Fix: Check the allowed formats and size caps for the asset kind, then retry with a supported file.
Prevention: Export media in one of the supported formats before uploading.
Symptom: Asset cannot be deleted
Cause: One or more published scenarios still reference the asset.
Fix: Open the asset usage list, remove the asset from the published flows, publish the updated scenarios, and try again.
Prevention: Review usage before cleaning up old media.
Symptom: Storage limit reached
Cause: Your workspace has used the available asset storage for its current plan.
Fix: Delete unused assets or upgrade to a plan with more storage.
Prevention: Reuse shared assets instead of uploading duplicates and review storage stats regularly.
FAQ
Q: Are assets shared across bots in the same workspace?
A: Yes. Assets are owned by the workspace, so they can be reused across different bots and scenarios inside that workspace.Q: Does deleting an asset break old drafts?
A: Deletion is blocked when the asset is still used by a published scenario. Drafts should still be reviewed carefully before cleanup.Q: Where do storage limits come from?
A: Asset storage is controlled by your billing plan. Check the current limit on the billing page.