Skip to content

Attachments Configuration

Attachments are reference files permanently attached to an Agent, automatically included in every conversation.

When to Use

  • Agent needs to permanently reference certain documents
  • Small data not suitable for knowledge base
  • Content that Agent should prioritize referencing

Attachments vs Knowledge Base

Attachments Knowledge Base
Capacity Maximum 5 files Can connect large amounts of data
Usage Method Automatically included in every conversation Agent decides whether to query
Suitable Content Core rules, key information Large reference materials

Usage Recommendations:

  • Attachments: Place core rules the Agent must know
  • Knowledge Base: Place detailed data that needs to be queried

Configuration Steps

Step 1: Find Attachments Area

In the advanced settings area (gray background) of the left panel in Agent Editor, find the "Attachments" block.

Step 2: Upload Files

Click "Add Attachment" or the paperclip button to open the upload dialog, where you can:

  • Local Upload: Click "Choose File" button or drag files to the upload area
  • Select from Cloud: Choose files from connected data sources (like GitHub, Notion, Google Drive, etc.)

Supported File Types:

  • Documents: PDF, Word (.doc, .docx), Text files (.txt)
  • Presentations: PowerPoint (.pptx)
  • Markup Languages: Markdown (.md), HTML (.html)
  • Images: JPEG (.jpg, .jpeg), PNG (.png), GIF (.gif), WEBP (.webp)

File Size Limit:

  • Single file maximum 50 MB
  • Files exceeding the limit cannot be uploaded

Step 3: Manage Attachments

After uploading, you can:

  • View list of uploaded files
  • View remaining quota for uploaded attachments
  • Delete unnecessary attachments

Quantity Limit

  • Maximum 5 attachments
  • This limit ensures the Agent can effectively process content

File Size Limit

  • Single file maximum 50 MB
  • This limit ensures efficient uploading and processing
  • If files are too large, consider:
  • Splitting files into multiple smaller files
  • Streamlining content before uploading
  • Using the knowledge base to store large data

Usage Scenario Examples

Core Product Specifications

Attachment: product-specs.pdf
Content: Complete product specification sheet

Core Instructions coordination:
"When answering product specification questions, prioritize the specification
sheet in the attachments"

Response Guidelines Manual

Attachment: response-guidelines.md
Content: Standard response format, terminology guidelines, prohibited terms

Core Instructions coordination:
"All responses must follow the response guidelines manual in the attachments"

FAQ List

Attachment: faq.md or faq.txt
Content: Structured Q&A reference table (using Markdown or plain text format)

Core Instructions coordination:
"When receiving common questions, directly quote standard answers from
the FAQ attachment"

Best Practices

Keep Content Concise

Attachments are processed in every conversation; overly large files will:

  • Increase processing time
  • Consume more resources
  • May exceed model processing limits

Recommendation: Place large data in the knowledge base; attachments should only contain core essentials.

File Size Recommendations:

  • Individual attachments should be kept under 10 MB to ensure processing speed
  • Files over 10 MB can be uploaded (up to 50 MB limit) but may affect response speed
  • If content is extensive, consider:
  • Splitting files into multiple attachments (maximum 5)
  • Moving detailed content to knowledge base, keeping only summaries or key information in attachments

Mention Attachments in Core Instructions and File Purposes

Let the Agent know about attachments' existence and purpose:

## Reference Materials
You have the following attachments to reference:
- product-specs.pdf: Product specification sheet
- response-guidelines.md: Response rules

When answering product questions, please consult the specification sheet first.
All responses must comply with response rules.

Regular Updates

While attachments are suitable for less frequently updated content, ensure content remains correct:

  • Update when product specifications change
  • Update when policies adjust
  • Immediately fix when errors are discovered

FAQ

Can attachments and knowledge base be used together?

Yes! This is the recommended approach:

  • Attachments: Core rules, essential knowledge
  • Knowledge Base: Detailed data, content that needs querying

The Agent can reference both simultaneously.

Do I need to re-save the Agent after updating attachments?

Yes, attachments are part of Agent configuration. After updating attachments, you must save for changes to take effect.

Can users see attachment content?

Users cannot directly download attachments, but the Agent may quote attachment content when responding. It's recommended to remove confidential information or limit quotation methods in Core Instructions.

What if I have more than 5 attachments?

Consider:

  1. Merge related files
  2. Move some content to knowledge base
  3. Streamline content, keeping only the most core information
What if file size exceeds 50 MB?

If files exceed the 50 MB limit, consider:

  1. Split Files: Divide large files into multiple smaller files (each not exceeding 50 MB)
  2. Streamline Content: Remove unnecessary content, keeping only core information
  3. Use Knowledge Base: Upload large files to knowledge base, keeping only summaries or indexes in attachments
  4. Compress Files: If image files, compress appropriately before uploading

Next Steps