Upload files to Memory Brain
Upload supported business files as an atomic batch of pending Memory Brain revisions for normalization and review.
How this fits into Lead360Explore Ask360 memory and learningSee how reviewed business knowledge supports exact roles and client boundaries.- 01
How Lead360 helps
- 02
Before you begin
- 03
Complete the workflow
- 04
Understand the key controls
How Lead360 helps
Memory Brain file upload turns approved YAML, JSON, Markdown, text, CSV, and text-based PDF content into governed pending revisions. The batch validates together, rejects credentials, preserves file and source evidence, and prevents a partially accepted upload from leaving an unclear knowledge state.
When to use this workflow
Use file upload for stable business knowledge that is not available through a supported Lead360 sync and has an authorized source owner.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Remove passwords, tokens, API keys, payment credentials, and unnecessary personal data.
- Use a supported text-based format and clear file names.
- Confirm source ownership, accuracy, retention, and intended consumer scope.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open Memory Brain and choose file or folder upload.
- Select supported YAML, JSON, Markdown, text, CSV, or text-based PDF files.
- Review batch validation, detected credentials, normalization, and file count.
- Submit the valid batch to create pending revisions.
- Review each normalized revision before making any snapshot available.
Understand the key controls
Atomic batch
The batch is accepted as a unit. A validation failure prevents a partial upload that could hide missing context.
Credential rejection
Detected credentials are rejected because memory is not a secret store.
Text-based PDF
A PDF must contain extractable text. Scanned image-only documents require an approved text preparation process before upload.
Confirm the result
Do not rely on a success message alone. Confirm the saved state and any live effect in the product area that owns the final record.
- Confirm every intended file appears once as a pending revision.
- Compare normalized content with the source.
- Review checksum, evidence, and sensitive-data handling before approval.
Troubleshooting
The batch is rejected
Open the validation details and correct unsupported type, unreadable content, credential detection, duplicate path, size, or normalization errors.
A PDF produces little text
Confirm it contains a text layer. Prepare an accessible text or Markdown source rather than relying on an image-only scan.
Frequently asked questions
Which file types can Memory Brain accept?
The supported workflow accepts YAML, JSON, Markdown, plain text, CSV, and text-based PDF content.
Can I upload API keys in a private memory file?
No. Memory Brain rejects credentials and must not be used as a secret manager.
Continue with Lead360
Use this workflow in Lead360
Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.
Support