Skip to main content

Transformation Template

Use this template to adapt request/response shape between client and upstream systems.

Default pattern​

http_trigger -> proxy_node/http_request_node -> set_node -> response_node

Configure​

  1. Keep client-facing schema in proxy contract.
  2. Map request fields for upstream format.
  3. Map upstream response back to client-safe schema.
  4. Add conditional branches for version/partner-specific mappings.

Verify​

  • V1 and v2 request samples return expected schema versions
  • Unsupported mapping path returns controlled error

XML templates​

The product ships template starters for XML → JSON (parse incoming XML from the HTTP trigger body) and JSON → XML (return an XML body with Content-Type: application/xml). Both use the XML node. Pick them from the workflow template gallery when creating a proxy workflow.