export-pipeline-reference

Export Pipeline — Request Processor Reference

This skill provides the complete configuration reference for the Request Processor, Rossum's multi-stage export pipeline engine. It replaces the legacy multi-hook pipeline with a single serverless function that executes complex API workflows from pure JSON settings — no code required.

For the full configuration guide, field reference, patterns, and examples, see reference.md.

IMPORTANT — hook setup: The Request Processor runs as a single serverless function hook. Install it from the Store ("Request Processor"), or create the hook via the Rossum API (or prd2) from that hook template, then configure the settings JSON. The template (id 50) is shown only to organization groups with the ps_eng_export_pipeline visibility tag, which only Rossum can add; without it the organization cannot see the template (GET /hook_templates/50 → 404). Because it is a function hook, a copy of an existing hook's config.code (or a prd2 deploy) works without the template — prd2 then creates it with a plain POST /hooks (see rossum-reference → Store templates and visibility, prd-reference → Hooks created from Store templates). To read the exact engine behaviour for a given deployment, pull config.code off the deployed hook — that is the authoritative version for that org.

Use this knowledge when:

• Building a new export pipeline that sends data to external APIs (Coupa, SAP, NetSuite, custom REST)
• Configuring SFTP/S3 file export via the file-storage-export service
• Writing the settings JSON for a Request Processor hook (stages, auth, requests, response handlers)
• Using variable templating ({field.*}, {payload.*}, {property.*}, {token}, {sequence})
• Setting up OAuth authentication with token caching
• Configuring conditional stage execution (evaluate phase with MongoDB-style filters)
• Fetching document relations or explicit data in get_content phase
• Extracting values from API responses using JMESPath, XPath, or regex
• Iterating over line items or lists of related documents
• Uploading files (PDF scans, email EML, attachments) via multipart or files content types
• Migrating from the legacy Pipeline v1 (multi-hook chain) to the Request Processor (single hook)
• Debugging export pipeline issues (URL not fetching, token caching, handler conditions)
• Understanding the difference between document_relation and document_relation_content sources
• Diagnosing prerequisite/setup failures: TCP timeouts to external hosts, missing rossum_authorization_token, Schema sideloading must be enabled errors, generic "Some exception occurred" export failures

Note: The rossum-reference skill covers the legacy 6-step export pipeline chain (Custom Format Templating, REST API Export, Data Value Extractor, Export Evaluator, SFTP Export). This skill covers the Request Processor, which is the modern replacement that consolidates all steps into a single configurable hook.