Overview
Prerequisites
- JSON file with your documents
- Understanding of your data structure
Configuration
Required Fields
Optional Fields
Setup Steps
- Navigate to Knowledge → Sources
- Click Create Source
- Select JSON as the source type
- Configure field mappings:
- Set the title field
- Set content field(s)
- Set ID field (optional)
- Click Save
- Upload your JSON file via the sync interface
JSON Format
Basic Format
Array of objects with consistent structure:Multiple Content Fields
Combine multiple fields into document content:Custom Field Names
Map any field structure:Uploading Files
Via Admin Interface
- Go to the JSON source in Admin > Knowledge > Sources
- Click Import > Upload File
- Select your JSON file
- Monitor import progress
Via API
Content Field Combination
When multiple content fields are specified, they are combined in order: Configuration:Best Practices
Data Preparation
- Ensure all objects have the same structure
- Use consistent field names
- Clean HTML or convert to Markdown before import
- Validate JSON syntax before upload
Field Mapping
- Choose descriptive titles (not IDs or codes)
- Include all relevant content fields
- Use a unique ID field for updates
Large Files
- For large datasets, consider splitting into smaller files
- Upload sequentially to avoid timeouts
- Monitor sync history for errors
Migration Use Cases
From Other Knowledge Bases
- Export data from source system as JSON
- Map fields to AGO’s expected structure
- Upload and verify import
From Spreadsheets
- Export spreadsheet to CSV
- Convert CSV to JSON (many tools available)
- Upload JSON to AGO
From Databases
- Export database query results as JSON
- Transform field names if needed
- Upload to AGO
Troubleshooting
Invalid JSON
Invalid JSON
- Validate JSON syntax (use online validators)
- Check for trailing commas
- Ensure proper quoting of strings
Missing Content
Missing Content
- Verify
content_fieldsincludes all needed fields - Check field names match exactly (case-sensitive)
- Review for null or empty values
Duplicate Documents
Duplicate Documents
- Use unique values in
id_field - Re-importing updates existing documents by ID
- Clear source before re-importing for fresh start
Encoding Issues
Encoding Issues
- Use UTF-8 encoding
- Handle special characters properly
- Convert from other encodings if needed
Related Documentation
- Public API v1 Reference - Complete API documentation
- Knowledge Connectors - All available connectors
- Knowledge Source Management - Source configuration
- Knowledge AI Ingestion - AI-powered import
