Keep your workflow. Add the report.

PandaRender uses standard HTTP modules, not a marketplace app. These are configuration instructions; imports into live Make or n8n accounts have not been verified.

Make: HTTP → Make a request

  1. Add HTTP → Make a request after the step producing inspection JSON.
  2. Set method to POST and URL to https://YOUR-HOST/api/public/v1/reports/inspection.
  3. Add Authorization: Bearer YOUR_API_KEY, using your private connection or protected scenario value. Do not put a key in a shared blueprint.
  4. Set body type to Raw, content type to application/json. Map the complete inspection object, including inline base64 photo data.
  5. Turn response parsing off for PDF output. If your HTTP module version offers a response type, choose file/binary rather than JSON.
  6. Map the returned PDF binary data to your next storage upload or email attachment step. Use the filename inspection.pdf.
  7. Handle non-2xx responses in an error route; their bodies contain structured JSON, not a PDF.

n8n: Manual Trigger → HTTP Request

  1. Start with a Manual Trigger. Add an Edit Fields (Set) node to provide the inspection payload, or map an existing upstream JSON item.
  2. Add HTTP Request. Method: POST. URL: https://YOUR-HOST/api/public/v1/reports/inspection.
  3. Use a private Header Auth credential with name Authorization and value Bearer YOUR_API_KEY.
  4. Enable Send Body. Choose JSON. Use expression {{ $json }} when the incoming item is the complete report.
  5. Under Options → Response, choose Response Format: File. Set the binary property name to data.
  6. Connect a storage upload, email attachment or self-hosted Read/Write Files from Disk node. Use binary property data.
  7. For a no-key smoke test, point the HTTP node to /api/public/demo/inspection and send {}.

Keep the response binary

The successful response is application/pdf, starting with %PDF. Do not parse it as JSON, wrap it in a text field, or base64-encode it unless your next service explicitly requires that.

Before you run

  • Use inline JPEG/PNG/WebP evidence. Remote URLs are not enabled.
  • All finding photo IDs must exist in the photos array.
  • Validate structure first if your source data is variable.
  • Do not automatically retry failed generation; attempt quotas apply, and idempotency is not yet supported.
  • Use the repository’s exact benchmark payload for the full 30-photo local test.
API schema, limits & errors