To email Qlik Sense reports automatically, you need a tool that opens the app with the right selections, renders the objects, builds the email and attachments, and sends it on a schedule or after a reload. On client-managed Qlik Sense this has traditionally meant Qlik NPrinting; on Qlik Cloud there is Qlik Reporting Service; and dedicated tools such as KPImailer cover both.
This guide walks through the decisions and a typical setup.
1. Decide what people should receive
Before choosing a tool, write down for each report:
- Who receives it, and whether each person should only see their own data.
- What they need to see without opening anything: two or three KPIs, a trend, an exception list.
- Which files they actually use: Excel for analysts, PDF for management, PowerPoint for meetings.
- When it should arrive: a fixed time, or as soon as the data reload finishes.
The answers decide whether you need bursting, templates and reload triggers, which is most of the difference between tools.
2. Choose where the report is designed
There are two common approaches:
- Attachment-first. The email is a short cover note and the report is a PDF or Excel file. Simple, but many readers never open the attachment.
- Email-first. The KPIs and charts are in the email body, with files attached for people who need the detail. This is what KPImailer’s designer is built for.
3. Build the report
With KPImailer the steps are:
- Connect Qlik Sense client-managed (a client certificate and a service user) or Qlik Cloud (an OAuth machine-to-machine client).
- Create a report and pick the Qlik app.
- Drag objects from any sheet onto the email canvas. Add text with tokens for dates, measures and dimensions.
- Set filters and a date range such as month to date or the previous week.
- Add attachments: formatted Excel, raw data, an Excel or PowerPoint template, PDF, paginated PDF or CSV.
- Preview the exact email and send a test to yourself.
4. Personalise with bursting
If each manager should only see their region, turn on bursting on the Region field and take recipients from a field that holds each manager’s address. One design then produces a tailored email per region, and values with no data are skipped.
5. Schedule it, or trigger it on reload
A fixed time is fine for many reports, but reports that depend on an overnight reload are safer on a reload trigger: the report fires when the Qlik task succeeds, so nobody gets yesterday’s numbers because the reload ran late. Add an alert for when the reload fails.
6. Monitor
Check the execution history after the first runs: which steps ran, how long each took and how many emails went out. Set up alerts for failed runs, and review report health from time to time.
Common pitfalls
- Sending everything to everyone. Use bursting and send rules so people only get what is relevant.
- Fixed times after variable reloads. Use reload triggers.
- Screenshots in emails. They go stale and cannot be filtered. Render live objects instead.
Want to try it on your own app? Start a free trial or book a demo.