The Scenario
You are an ecommerce operations lead. Last week your team ran three large batch imports — contacts, products, and orders — as part of a platform migration. Each job touched hundreds or thousands of records.
You need an Excel workbook showing each batch job's status, total item count, success count, and failure count before your Monday morning meeting with the CTO. She wants to confirm the migration data is clean before the new platform goes live.
The bad version of this weekend:
- You log into Omnisend and look for a batch job history view
- Find a jobs section but it shows limited detail and has no export button
- Open each batch job manually, read the numbers, type them into Excel
- Realize you also need to check error details for each failed item
- Walk into Monday's meeting with a half-filled spreadsheet and "I still need to check the error details."
The fast version is one prompt and the audit table is in the workbook before Sunday night.
The Easy Way: One Prompt in SheetXAI
SheetXAI reads the Omnisend batch jobs API and writes the status data into the workbook, so you do not have to open job records one at a time.
Open the SheetXAI sidebar and type:
List all Omnisend batch jobs and write batch ID, type, status, total item count, completed count, and error count into this workbook for all batches from the past 7 days.
SheetXAI calls the Omnisend batch jobs endpoint, extracts the fields you named, and writes the audit table into the workbook. All three batch jobs, one row each.
What You Get
An audit table with one row per batch job from the past week:
- Batch ID — for reference if you need to dig into specific job details
- Type — contacts, products, or orders
- Status — completed, processing, or failed
- Total item count — how many records were in the job
- Completed count — how many succeeded
- Error count — how many failed
The error count is the number the CTO is asking about. Zero across all three means the migration is clean. Anything above zero tells you which job type to investigate before Monday.
For any job with errors, ask SheetXAI to pull the error details into a separate tab with the specific record and the reason it failed.
What If the Data Is Not Quite Ready
Batch audits get complicated when there are many jobs or partial failures.
When you need error details for failed items
The summary counts show failures but you need to know which records failed and why.
For each batch job in this workbook where the error count is greater than zero, fetch the error details from Omnisend and write them into a new tab called "Errors" with batch ID, item reference, and error message.
When you need to look up specific batch IDs from last week
You saved the batch IDs when you ran the imports. You want the current status for each.
Fetch details for each batch ID listed in column A of this workbook and write job status, total items, success count, and failed count into columns B through E.
When you want to calculate the success rate for each job
The CTO wants percentages, not just counts.
After writing the batch job table, add a column G with success rate calculated as (completed / total) × 100, formatted as a percentage. Flag any row where the rate is below 95 percent.
When you want the full audit including error detail in one shot
You want the job summary and the error detail for every failed record, all in one pass.
List all Omnisend batch jobs from the past 7 days and write the summary (batch ID, type, status, total, completed, errors, success rate) into the Audit Summary tab. For every job with errors, fetch the error detail records and write them into tabs named Contacts Errors, Products Errors, or Orders Errors as appropriate. Write the total cross-job error count into cell H1 of the Audit Summary tab.
The pattern: summary and detail in one pass. You walk into Monday's meeting with the full picture, not a promise to follow up.
Try It
Get the 7-day free trial of SheetXAI and open any Excel workbook, then ask it to pull your Omnisend batch job history. The Omnisend integration is included in every SheetXAI plan. For related workflows, see how to backfill historical orders into Omnisend from Excel or the Omnisend in Excel overview.