How to Reconcile, Export, and Hand Off Email Account Task Results
Manage completed or partial MailMaker tasks using task IDs, result counts, API JSON, CSV exports, secure handoff, replacement decisions, and retention controls.
Reconcile requested, successful, and failed counts before exporting. Keep the task ID with API JSON or CSV output, release credentials only to the named owner, and create a replacement task only for the approved unresolved quantity.
What you will leave with
- The task ID is the link between cost, status, result, and support history
- MailMaker exposes task data as JSON and downloadable results as CSV
- Partial output should be preserved and reconciled before replacement
- Credentials belong in an access-controlled destination, not normal logs
Reconcile the task before downloading or distributing results
A completed download is not the first checkpoint. Read the task status, requested quantity, successful count, failed count, credits charged, and credits refunded together. These values explain what the task produced and what it cost.
Completed means the task finished without failed items; partial means it produced usable results and unresolved items; failed means no requested result completed. Keep the task ID with the decision so support and the receiving team can refer to the same record.
| Status | What to preserve | Next decision |
|---|---|---|
| Completed | Task ID, counts, final credit use, result owner | Accept or reject the downstream workflow |
| Partial | Successful output, failed count, refunded credits | Investigate and replace only unresolved quantity |
| Failed | Task ID, failure evidence, refunded credits | Correct, stop, or submit a newly approved task |
Use API JSON for systems and CSV for controlled handoff
The task detail API returns structured JSON with provider, status, counts, credit values, and account result data. The dashboard and API also support CSV export for an individual task, while a separate CSV export can collect completed and partial task results for the workspace.
Choose the smallest format the receiving workflow needs. A service can consume JSON without creating an extra credential file. An operator can use CSV when the destination requires a reviewable tabular handoff. MailMaker does not currently provide a TXT export, so documentation and runbooks should not depend on one.
Move credentials without turning the export into a second database
Export directly into the approved access-controlled destination. Do not attach raw credentials to tickets, paste them into chat, write them to application logs, or leave duplicate downloads in personal folders.
The handoff record can preserve task ID, provider, counts, owner, destination reference, acceptance time, and retention date without copying passwords. Grant the narrowest access that lets the receiving owner complete the approved work.
- Named result owner
- Restricted destination
- No credentials in logs or tickets
- Acceptance recorded by task ID
- Review and deletion date
Handle partial results without duplicating successful work
A partial task contains both usable output and unresolved quantity. Preserve the successful accounts, confirm the credits returned for failed items, and identify whether the original requirement still needs replacements.
If replacements are approved, submit only the unresolved quantity as a new named task. Do not repeat the original full quantity. The current API does not expose a server-side idempotency key, so an uncertain creation response should be reviewed before another request is submitted automatically.
A repeatable result-management procedure
Use the same procedure for every provider so the handoff remains auditable even when credit rates and acceptance tests differ. Provider-specific evidence belongs beside the common task record, not in place of it.
- Read the authoritative taskRetrieve the final status, counts, credits, and result from the task ID.
- Reconcile the ledgerCompare estimated credits, charged credits, and refunds for failed items.
- Select JSON or CSVUse API JSON for system consumption or CSV for an approved operator handoff.
- Release to the named ownerMove the output directly to restricted storage and record acceptance.
- Close or replaceRetire the task or approve a new task only for the unresolved requirement.
Questions about this workflow
Which result formats does MailMaker support?
Task details are available as structured JSON, and account results can be downloaded as CSV. The current product does not provide a TXT export.
Can I export results from several tasks?
Yes. MailMaker has a CSV export for completed and partial task results across the workspace, in addition to individual-task CSV export.
Should I retry the full quantity after a partial task?
No. Preserve successful output and create a new task only for the approved unresolved quantity after the original task is reconciled.
What should logs contain?
Logs can retain task IDs, provider, status, counts, duration, and error categories. Keep passwords, recovery data, and raw account exports out of normal logs.
Sources used in this guide
Provider rules and product behavior can change. These first-party references are the starting point for checking the current requirements.
- MailMaker: Account creation API ↗
Product overview for task creation, status retrieval, and result reconciliation.
- MailMaker: Credits and result FAQ ↗
Product policy for successful, partial, and failed task credit treatment.
Run the workflow in MailMaker.
Start in the dashboard with your provider selected, or connect the same task lifecycle to your application through the API.