Weekly executive analytics digest from Qlik Cloud

Build me an agent workflow that emails my leadership team a weekly executive analytics digest, written as a narrative brief from our Qlik Cloud dashboards.

Trigger: cron, every Monday at 7:00am in America/New_York. Make the timezone configurable.

Integrations: Qlik Cloud (to read the dashboards) and Gmail (to send the email).

At the top of the prompt, expose a clearly labeled configuration section the user can edit. It should let them define:

1) A list of sections in the digest. The default sections are Revenue, Pipeline, Customer Health, Support Load, and Product Usage, but the user can add, remove, or rename sections.

2) For each section, the Qlik app id, the sheet (by id or title), and the specific chart or KPI object ids that feed it. Make it explicit that the agent should use the Qlik Cloud List Apps operation to help the user discover their app id on first run if it is not yet filled in, and List Sheets in App / List App Objects to discover sheet and object ids.

3) The recipient list (To, Cc, Bcc) for the Gmail send, plus the From label and a subject line template such as 'Weekly exec digest, week of {date}'.

4) A writing style setting with these options: formal board update, terse executive bullets, or warm analyst voice. Default to warm analyst voice.

5) A target length (default: roughly 400 to 600 words for the full digest, not per section).

Each Monday at 7am, the agent should:

Step 1. For every configured section, call Qlik Cloud Get Visualization Data on each configured chart or KPI object to pull the current values. Where the visualization supports it, also pull the prior period values so the agent can compute week over week movement. If a chart has not refreshed since the last digest, note that the data is stale.

Step 2. Draft a narrative digest, not a raw data dump. Use a short headline at the top, then one section per configured business area with its own subhead. For each section, write two to four sentences that cover: the headline number, the week over week change, what is driving the move, and any risk worth flagging. Do not paste tables. Numbers should appear inline in sentences, with deltas in parentheses.

Step 3. End the digest with a short paragraph titled 'What to watch this week' that names the top one or two items leadership should pay attention to over the coming week, based on the movement across sections.

Step 4. Use the Gmail Send a Message operation to send the digest. The email body should contain the digest as readable HTML (clear headings per section, no embedded images, no attachments). The subject line should follow the configured template.

Quality rules for the writing: never invent numbers, only use values returned by Qlik. If a section has no usable data, include the section header and a one line note that the source did not return data this week, rather than skipping silently. Keep the voice consistent with the configured style. No marketing fluff, no emoji, no exclamation marks.

Failure handling: if Qlik returns an error or a configured object id is no longer valid, still send the email, but include a short 'Issues this week' note at the bottom listing which sections failed and why, so the user knows to update the configuration.