The File slot type enables plugins to receive file attachments from users. It is resolved only when the user interacts with the dedicated “Upload file” button in the assistant interface.

File Object Structure

When a an attachment is added to the File slot, it generates this object structure:

1
{
2
  "file_name": string, // Name used when uploading to the external system's API
3
  "location": string,  // File location
4
	"content": string, // base-64 encoded
5
}

Supported file extensions (case-insensitive)

(case-insensitive)

.png, .jpg, .jpeg, .pdf, .txt, .csv, .xlsx, .xlsm, .xls, .xltx, .xltm

Upload Interface

Users must use the “Upload file” button.

Limitations

Workarounds

Use Case: Avoid Local File Download

Problem:

You do not want users to download files to their machine. Instead, you want users to paste a link (e.g., from Google Drive, OneDrive, or internal file server) directly into the assistant.

Limitation:

The platform cannot download files from external URLs on behalf of the user.

Solution:

Use a string slot named file_link instead of File.

Customer API responsibility:

Your API will need to handle the file download from the link passed by the user.

• Download file from file_url
• Validate content/type
• Process as needed