TxDownloaderPro (writeback sync)

TxDownloaderPro runs the opposite direction to CRMPro: it reads transactions out of the CRM and writes them back toward the customer’s source system. The txdownloaderpro_* admin tools cover the full setup surface — list and read processes (txdownloaderpro_list_processes, txdownloaderpro_get_process), create and update them, edit the field mapping and the Result Mapping, preview the generated XML, test a process query, check sync status and run the circular-sync check. Everything CRMPro’s section says about operation applies here too: the group is Admin-only, every call names the tenant (--profile from the CLI), and configuration edits land on the agent’s next run. Tools that replace or delete stored state — deleting a process, replacing a whole mapping — say so in their descriptions and require confirm: true. Four more read the transaction log rather than the setup: txdownloaderpro_error_log and txdownloaderpro_error_log_page group failures by business key (and show which of them later succeeded), txdownloaderpro_transaction_log is the attempt grid with a date window, status filter and search, and txdownloaderpro_transaction opens one attempt with its request and response payloads. These are logs, so their output is bounded — pages default to 25 rows and are capped, oversized payloads are clipped, and every answer says whether anything was left out; from the CLI they are dlake txdownloaderpro errors | transactions | transaction, with --out <file> to write a whole result set to disk. The deeper guide is the dlake-txdownloaderpro skill.