- AI-Agent
- Ready to Run
Import JSON Batches
Import valid JSON records and report rejected entries
Use this Agent instantly or customize it - no programming needed
- a JSON batch filea JSON batch file
You place a JSON batch file containing business records in your chosen folder to start an import.
- Validation rulesValidation rules
You choose the ID field, required fields, and value checks for each batch.
- Existing document IDsExisting document IDs
Your collection's existing IDs identify entries that would duplicate a document.
Your shared import folder lets the Agent read new batches and save their result files.
Your document collection lets the Agent check IDs and create documents without replacing existing ones.
- Import summaryImport summary
Your summary shows the batch name, confirmed import count, rejection count, and completion status.
- Rejection fileRejection file
Your CSV lists each rejected entry's position, supplied ID, and specific reason.
- Imported documentsImported documents
Your collection gains documents that pass validation and use IDs not already present.
- Import summaryImport summary
Your summary shows the batch name, confirmed import count, rejection count, and completion status.
- Rejection fileRejection file
Your CSV lists each rejected entry's position, supplied ID, and specific reason.
This Agent starts when a JSON batch lands in your chosen import folder. It checks your required fields and duplicate IDs before adding valid documents. It saves an imported count and rejection file beside the batch.
Modify Agent
Customize this Agent to fit your needs using natural language.
Start Agent for Free
Enter your email address and we will send you a secure link to continue.
Google DriveUsed as:
- Shared import folder
Google Drive lets the Agent read new batches and save their result files.
monday.comUsed as:
- Document collection
monday.com lets the Agent check IDs and create documents without replacing existing ones.
Google ContactsUsed as:
- Shared import folder
Google Contacts lets the Agent read new batches and save their result files.
Microsoft Office 365Used as:
- Shared import folder
Microsoft Office 365 lets the Agent read new batches and save their result files.
Firebase / FirestoreUsed as:
- Document collection
Firebase / Firestore lets the Agent check IDs and create documents without replacing existing ones.
Superhuman DocsUsed as:
- Document collection
Superhuman Docs lets the Agent check IDs and create documents without replacing existing ones.
Made for your role
Import JSON Batches is made for people in these roles.
- Data Operations Manager
Report each batch's imported count and rejected entries for review.
Show all Agents for the Data Operations Manager role - Data Coordinator
Check incoming record batches and flag entries that need correction.
Show all Agents for the Data Coordinator role - Data Engineer
Load valid records into the collection without replacing existing IDs.
Show all Agents for the Data Engineer role
Made for your department
Import JSON Batches is made for people in these departments.
- Data Operations
Import valid business records and file errors beside each batch.
Show all Agents for the Data Operations department
How Import JSON Batches works
5 steps, in order, on every run.
-
Read the new JSON batchRead the file from your chosen import folder. Use its name to label the results.
-
Check records and IDsCheck each record against the fields and value rules you choose. Mark missing or repeated IDs for correction.
-
Check for existing documentsLook up candidate IDs in your collection. Mark any ID already there as a duplicate.
-
Import valid documentsCreate documents under their incoming IDs without replacing existing ones. Record write failures for the rejection file.
-
Save the import resultsSave the imported count and a CSV of rejected entries beside the source batch. Include entry numbers and reasons for correction.
How to Get Started
Connect the tools you already use, such as Google Drive, monday.com or Google Contacts.
6 tools
- Choose the import folder, the destination document collection, and the person who will review the result files.
- Specify that each batch is a JSON array of objects, which field supplies the document ID, and which fields are required and how their values should be checked.
- Choose names for the summary and rejection files so each can be tied to its source batch.
Use safe mode to approve every result before it goes out, or let the Agent run automatically.
FAQs
Frequently asked questions about the Import JSON Batches:
You choose the import folder, document collection, and person who reviews results. You also set the ID field and checks for required values.
No. The Agent rejects IDs already in your collection and records them as duplicates. It also records IDs that become occupied before creation.
If your file has invalid JSON or lacks an array of records, nothing imports. You get the file error in both result files.
It stops and asks you. The Agent does not guess when it reaches a decision you have not approved.
Yes. Every run creates a plain-language log that you can review and export. Logs are kept for twelve months.
The Agent stops at the end of the billing month and its tool connections are removed. Your run logs remain available for twelve months.
Agents related to Import JSON Batches
More ready-to-run Agents for connected work.
See the original approval path alongside a held duplicate card, so your coordinator can reconcile a revised supplier quote.
Your team sees when a bill may repeat a paid invoice number. A warning or review question shows what needs attention.
Your coordinator gets both revision links in chat when the task and current proof differ, with the task held for a human choice.
17 toolsYour bill review stays on hold when a supplier sends a corrected invoice, with both versions and the earlier decision linked for your reviewer.
6 tools