RowToDoc — Fixed Template DOCX Batch

Turn an approved fixed DOCX template and a table of records into 1–100 separate DOCX files. Map the fields explicitly, review the actual preview, approve its exact hash and confirm the empty skipped-row list, then get the complete ZIP with documents, an index, exception report and a verifiable receipt.

Validation scope: maintainer-account synthetic workflows establish specific technical results. Execution by non-owner accounts and platform cross-account storage ACLs remain unverified. Use the exact Actor/build pair in the matching client compatibility record. A successful preview or run is not complete delivery: download and verify the original ZIP and receipt.

Who it fits

Use RowToDoc when the same fixed letter or confirmation is repeated for many records and the mapping can be stated explicitly. Supply a DOCX template you may process, an XLSX workbook or UTF-8 CSV, and a mapping between columns and fixed text placeholders. Pin the exact template with its SHA256. Keep identifiers and displayed dates as text when their formatting matters.

The supported profile replaces fixed text placeholders in body paragraphs and simple top-level tables. It does not provide arbitrary Word layout adaptation, dynamic tables, header/footer replacement, image replacement or PDF output. Existing headers/footers may be preserved. Bespoke manual template work is outside the batch price.

Review before generation

The first operation is a preview. It reports the valid count, warnings, errors, planned files and exact skipped rows. Generation requires approval of that actual preview hash and entire skipped-row list. Changing the template, data, mapping, policy or build invalidates the earlier approval.

The generation profile requires reject policy, all-valid input and an empty skipped-row list. Nonempty skip subsets and invalid rows cannot generate. Any future broader subset handling needs separate implementation and acceptance. Up to 100 valid documents fit one batch; the service does not silently split a larger job into multiple charged batches. The default example is a preview-only three-record synthetic example, not a generation request or customer approval.

Price and charging

The product price is USD4.90 once per complete, verified batch made available, containing 1–100 DOCX files. One verified-batch event follows successful persistence and verification of the delivery. Previews, rejected requests and requests with no valid delivery do not create this product generation event.

Review the actual platform billing terms and your approved spending cap before generation. Platform account plans, API/storage terms and displayed platform fees are separate from this product event. Do not assume a preview is free of all platform costs. A USD1 cap cannot accommodate a USD4.90 generation event. The service does not authorize account upgrades, financial fallback or duplicate charge attempts.

A delivery made available on the platform can precede your local download. Download and verify the entire original ZIP through your Agent to finish your workflow. A confirmed product event does not by itself prove customer payment, developer revenue or settlement. Unknown charges must be investigated without automatically rerunning or charging again.

Agent workflow

The intended workflow runs in your own Agent using its existing authorized tools. The client needs Python 3.10+ with the standard library, local file access, a normally authenticated browser that can submit exact JSON, and binary download into the Agent workspace. These capabilities must be verified for the selected Agent; compatibility with every Agent is not claimed.

The client contains input preparation, exact preview approval and delivery verification. It contains no document-generation engine, EXE or credential transport and does not require a Windows software purchase. It does not authenticate for you. Do not send tokens in chat or save them in request files. The actual outer caller is verified against native metadata; the private worker remains owner-authorized.

The sequence is: prepare exact INPUT; submit preview once; review and approve its actual hash/subset/price; submit generation once; download original OUTPUT, ZIP and receipt; verify identities, request binding, hashes, ZIP members, DOCX/index structure and billing receipt. A successful run, preview or link alone is not complete Agent delivery. Unknown submission stops the route instead of launching a duplicate.

Privacy and retention

Your template and data are encoded into Apify INPUT and handled in the run and its storage. Your Agent also retains local requests and downloaded outputs. Platform and authorized maintainer access depend on actual account permissions. No zero-retention, automatic-deletion, exclusive-access or maintainer-invisibility promise has been established. Check the platform's current terms and your own processing authority before transferring sensitive data. Acceptance examples are synthetic; no customer data was used for the owner pilot.

Client license and support

The non-core client license permits internal reading, installation and adaptation for invoking this service, free of charge. It grants no redistribution/resale or engine rights and is not an open-source license. Install only the matching non-core Agent client and verify its SHA256 before use. The compatibility record pins the tested Actor/build pair.

Use the Issues entry shown on this Actor's page when available. No support email or SLA is promised. Report run/build IDs, error codes and hashes without uploading customer files or secrets. Supported-profile defects and bespoke manual adaptation are handled separately.

Evidence limits

A maintainer-account representative workflow and synthetic batch evidence establish specific technical results. They do not establish non-owner platform access, arbitrary-template compatibility, paid customer adoption, revenue, settlement or fixed processing time. Offline cross-caller rejection checks demonstrate code behavior, not actual cross-user platform ACLs. Preserve these distinctions when evaluating whether the service fits your data and Agent.