Step 2: Connect Jira and Define the Project Scope

Configure your project key and Jira queries to collect today’s tickets.

1. In Define Project Identifier, set the Project Key value to SUP.
2. Open Retrieve Project Tickets and set the JQL in Options → JQL to =project = {{ $json['Project Key'] }} AND created >= startOfDay().
3. Credential Required: Connect your jiraSoftwareCloudApi credentials in Retrieve Project Tickets.
4. In Fetch Ticket Comments, set Issue Key to ={{ $json.key }} and keep Resource as issueComment with Operation getAll.
5. Credential Required: Connect your jiraSoftwareCloudApi credentials in Fetch Ticket Comments.
6. Optional utilities: Utility: Fetch Today Tickets uses JQL =project = SUP AND created >= startOfDay() and Utility: Retrieve Tickets Raw uses JQL =project = {{ $json["Project Key"] }} for debugging or comparisons.
7. Credential Required: Connect your jiraSoftwareCloudApi credentials in both Utility: Fetch Today Tickets and Utility: Retrieve Tickets Raw if you plan to use them.

Step 3: Split and Batch Ticket Data

Prepare each ticket for AI summarization and control processing flow.

1. In Extract Ticket Fields, set Field to Split Out to key and Fields to Include to fields.description, fields.summary.
2. Use Iterate Ticket Batches to process tickets in manageable chunks (defaults are OK for smaller volumes).
3. Iterate Ticket Batches outputs to both Compile Summaries and Fetch Ticket Comments in parallel, enabling aggregation and comment retrieval at the same time.

Step 4: Set Up the AI Summarization Flow

Combine ticket details and comments, then generate structured summaries with OpenAI.

1. In Combine Ticket Context, keep Mode as combine and Combine By as combineAll.
2. Open AI Ticket Digest and set Text to the full prompt expression: =Ticket Title:\n{{ $json['fields.summary'] }}\n\nTicket Description:\n{{ $json['fields.description'] }}\n\nTicket Comments:\n{{ JSON.stringify($json.body.content) }}\n\nSummarize all the ticket information, the comments, also the solution found\n\nOutput using this json format:\n{\n "Ticket Summary": "Write a professional and concise summary that combines all relevant tickets into a single narrative. Include the core issue reported in each ticket, key findings from the comments or conversations (such as user feedback, internal investigation, and developer notes), and the progress or troubleshooting steps taken. Ensure the summary reads fluently like a report, highlights patterns across tickets if any, and avoids repeating ticket IDs unless necessary. Use clear language for stakeholders who may not be technical.",\n "Proposed Solution": "Step-by-step explanation or resolution applied."\n}.
3. In OpenAI Chat Engine, select the Model gpt-5.
4. Credential Required: Connect your openAiApi credentials in OpenAI Chat Engine.
5. Keep Structured Result Parser attached as the output parser to AI Ticket Digest using the provided JSON schema example. Add credentials to OpenAI Chat Engine (the parent), not the parser.
6. In Merge Summaries Stream, keep Mode as combine and Combine By as combineAll.

Step 5: Assemble and Format the Summary Output

Aggregate all summaries and generate a clean email-ready payload.

1. In Compile Summaries, aggregate the output field (already set in Fields to Aggregate).
2. In Assemble Output Payload, set JSON Output to ={\n "output": {\n "Ticket Summary": {{ JSON.stringify($json.output['Ticket Summary']) }},\n "Proposed Solution": {{ JSON.stringify($json.output['Proposed Solution']) }},\n "Key": {{ JSON.stringify($json.key) }},\n "Title": {{ JSON.stringify($json['fields.summary']) }},\n "Description": {{ JSON.stringify($json['fields.description']) }}\n }\n}.
3. In Compose Email Body, keep the provided JavaScript Code to format the ticket summaries into formattedOutput.

Step 6: Configure Email Delivery

Send the formatted summaries to your stakeholders via Gmail.

1. In Dispatch Summary Email, set Send To to [YOUR_EMAIL].
2. Set Message to ={{ $json.formattedOutput }}.
3. Set Subject to =Daily Ticket Summaries – {{ $now.format('dd MMM yyyy') }} and keep Email Type as text.
4. Credential Required: Connect your gmailOAuth2 credentials in Dispatch Summary Email.

Step 7: Test and Activate Your Workflow

Validate the workflow end-to-end before enabling scheduled execution.

1. Click Execute Workflow from Manual Execution Start to run a test.
2. Confirm Dispatch Summary Email sends an email with the formatted ticket summaries and links.
3. Review the AI output in AI Ticket Digest to ensure the JSON fields Ticket Summary and Proposed Solution are populated.
4. When satisfied, activate the workflow and let Scheduled Automation Trigger run it daily.