# Reporting and exports

Source: /docs/raptor-mcp/reporting

How Raptor Gateway supports Qlik Cloud sheet PDF reports and distinguishes report generation from analytics, notification delivery and NPrinting.

## Choose the output you need

The report_action tool wraps the Qlik Cloud Reporting API. Its convenience workflow creates a PDF from a specified app and sheet; advanced requests can supply a Reporting API payload. The convenience builder supports PDF, page size and orientation, output lifetime and selection settings.

Use a Qlik Cloud connection whose identity can access the app and the required Reporting API operations. Your Qlik subscription, tenant settings, Raptor role and available tools determine whether the request can run. Discover the tool in the connected Cloud endpoint before planning an automated reporting process.

## Create, poll and retrieve

Report generation is asynchronous. A request ID confirms submission; completion and a downloadable output require separate checks. Keep the returned report ID so the assistant follows the original request rather than creating another report while waiting.

1. Confirm the app, sheet, intended selections, page size and orientation.
2. Create the report and retain its report ID.
3. Poll that report's status until Qlik reports a terminal outcome.
4. Inspect the report's outputs and select the required output ID.
5. Download the completed output, then open it and check the numbers, filters and page layout.

- State selections explicitly; a conversation's current analysis context is not automatically a Reporting API selection payload.
- Report outputs have a configured lifetime. Retrieve them before the output expires.
- The download tool limits content returned through the client. Large reports may require an approved transfer path rather than embedding the file in a tool response.

## Analytics, notifications and NPrinting

For a quick chart in an AI conversation, use the analytical chart workflow. For scheduled messages based on Qlik evidence, use InsightOps with an administrator-configured channel. These workflows have different outputs and delivery checks from a Reporting API PDF.

This Gateway's report_action implementation is Cloud-only. It does not provide Qlik NPrinting administration or turn a Qlik Sense on Windows connection into a Cloud Reporting connection. Existing NPrinting reports, templates, recipients and delivery schedules remain part of that separately configured service. Plan any NPrinting migration separately; this workflow does not replace its reports or schedules.

## Related Links

- [Qlik connections](/docs/raptor-mcp/qlik-connections)
- [Analytics and app development](/docs/raptor-mcp/analytics-and-app-development)
- [InsightOps](/docs/raptor-mcp/insightops)
- [Troubleshooting](/docs/raptor-mcp/troubleshooting)