Skip to main content

ancoreShare reports

With the connector ancoreMate ancoreShare Reports your flows work together with ancoreShare report buttons in Qlik Cloud:

  • When an ancoreShare report is finished starts a flow every time a report button has created its report – clicked by a user or started automatically. The flow gets the report files and can send or store them anywhere.
  • Run ancoreShare report starts a report from a flow.
  • List ancoreShare reports, Get report usage and List automated report runs give an overview of the report buttons and their use.

React to finished reports​

  1. Enable the ancoreMate event in the report button

    In Qlik Cloud, edit the sheet with the ancoreShare report button. In the properties of the button, turn on Enable ancoreMate Event. The button creates an ancoreMate key – copy it. Optionally add parameters (name and value, values may be Qlik expressions), for example the recipient of the report.

  2. Allow ancoreMate in the Content Security Policy

    The button reports the finished report from the browser directly to ancoreMate. In the Qlik Cloud Administration → Content Security Policy, add the origin https://ancorecloud.com with the directive connect-src. Without this entry the browser blocks the call.

  3. Create the flow

    Create a flow with the trigger When an ancoreShare report is finished and enter the ancoreMate key. App and Report are optional filters.

  4. Use the files

    With Include the report files (default: on) the trigger brings the files along:

    • Power Automate: in Send an email (V2), open Attachments, select Switch to input entire array and choose Attachments from the trigger. To save the files, use Apply to each over Files with Download report file.
    • n8n: the node ancoreMate Trigger with the event When an ancoreShare report is finished returns one item per file, with the file as binary data in the field data, ready for Gmail, Send Email, Google Drive or OneDrive.

The trigger also returns the parameters of the button, the Report title, the User ID of the user who ran the report and, for automated runs, the Task ID.

Good to know​

  • The key protects the event. Whoever knows the key can send events to your flows. Treat it like a password. If it became known, create a new key in the button – all triggers with the old key then stop receiving events and need the new key.
  • Same tenant only. A trigger only receives reports from apps in the tenant of its own Qlik Cloud connection. Copies of the app in other tenants (for example a test tenant) do not start it, even with the same key.
  • At most 20 triggers can use the same key.
  • Links are valid for 12 hours. Download the files within that time.
  • Large reports: files are included up to 50 MB together. If they are larger, the event arrives without attachments and with the reason in File error; download the files with Download report files and the File links. n8n accepts at most 16 MB per call by default; larger files arrive without binary data.

Run a report from a flow​

Run ancoreShare report starts a report of an ancoreShare report button from a flow – for example every Monday, after a reload, or once per region. ancoreShare queues the report and sends the files to the targets configured in the button. To get the files into a flow, turn on the ancoreMate event of the button and use the trigger described above.

The action runs the report with the credentials of an ancoreShare execution link. You create this link once in the report button; the action takes its values.

Before you begin​

  • ancoreShare remote execution in Qlik Cloud requires a specific license or service level. See Remote execution in Qlik Cloud.
  • A Qlik Cloud user for the report runs – ideally a dedicated report user instead of a personal account.
  • An ancoreMate connection whose Qlik Cloud user can open the app with the report button.

Steps​

  1. Create the execution link in ancoreShare

    In Qlik Cloud, open the sheet with the report button and select the button with the link symbol in the ancoreShare action bar. In the window:

    1. Credentials: choose how the link signs in (Qlik login and password, or JWT), how long it is valid (Credentials Expires) and whether it may run only this report or all reports (Credentials Usage).
    2. Verification: enter the code that ancoreShare sends to the e-mail address of the Qlik login.
    3. Options: choose the bookmark, selections, export type and notification for the run.
    4. Execution Link: copy the link.

    The steps in detail: Remote execution in Qlik Cloud.

  2. Take the values from the link

    The link looks like https://api.ancoresoft.com/reports/ExportReport?... and contains the values as parameters (name=value, separated by &). Copy them into the inputs of Run ancoreShare report:

    In the linkInput of the action
    accountIDAccount ID required – your ancoreShare account (customer number)
    executionTokenExecution token required
    appIDApp required – choose the app from the list
    reportIDReport required – choose the report button from the list
    exportTypeExport type – see Export types; leave empty for the export type configured in the button
    bookmarkBookmark
    selectSelections – see Selections below
    notificationNotification – none (no notification, the default), error (errors only) or success (success and errors)
    notificationEmailNotification mail – the address for the notification

    Values in the link are URL-encoded: replace %20 with a space and %2C with a comma when you copy single values, for example Region%20Name → Region Name.

    Selections​

    • One field: enter the field and its values without select=, for example Region,North,South.
    • Several fields: copy only the select=… parts of the execution link, as they are, for example select=Region,North&select=Year,2026. URL-encoded values work here. ancoreMate passes each field on to ancoreShare.

    Do not paste the whole execution link, and do not include other parts of it such as bookmark=…: the bookmark, the export type and the other values have inputs of their own. Otherwise the action fails and names the part that is not a selection.

    A webhook parameter of the link is not used by the action. The files go to the targets configured in the report button, for example the ancoreMate event.

  3. Add the action to the flow

    Add ancoreMate ancoreShare Reports → Run ancoreShare report (n8n: node ancoreMate, resource ancoreShare Report, operation Run) and enter the values. To vary the run, fill Selections from a previous step – for example the current value of an Apply to each over the regions.

Verify the result​

The action answers at once with the Task ID of the run, together with the app and the report; the report itself is created in the background by ancoreShare. List automated report runs with the same Account ID shows the run with its result and error. If the ancoreMate event of the button is turned on, the trigger When an ancoreShare report is finished receives the files when the report is ready.

Good to know​

  • The execution token is a password. Whoever has it can run reports as its Qlik Cloud user. Do not share it in plain text; in Power Automate, turn on Secure inputs in the settings of the action.
  • The token expires as chosen in Credentials Expires. Then create a new execution link and enter the new token in your flows.
  • Restricted tokens: a token created with Restrict Credentials to this Report Only runs only that report button. For several reports, create a token that allows all reports, or one link per report.
  • Changed options in ancoreShare do not change your flow: the inputs of the action decide the bookmark, selections, export type and notification of each run.

Export types​

Export typeLabel in ancoreShare
defaultReport default – the export type configured in the button
pdfAdobe - PDF
pptxPowerPoint - PPTX
dataexportData Exports (XLSX, CSV)
pdf.wordPDF to Word - DOCX
pdf.pptxPDF to PowerPoint - PPTX
pdf.htmlPDF to Web PNG - HTML
pdf.pngPDF to Image - PNG

The export types starting with pdf. require a specific ancoreShare license. See Export formats.