team-files-vs-confluence-1
Confluence Smart Links Explained
See how they work, where they fail with external files, and more secure, consistent management alternatives.
Read more: Confluence Smart Links Explained
untitled_Flux 2 Pro_2026-03-26_21-41-00
Jira SharePoint Integration
Discover how to sync files, automate folders, and enhance collaboration in Jira Cloud and Data Center.
Read more: Jira SharePoint Integration
Porto-pic
About us
From the start, our goal has been to remove the hidden friction that prevents teammates from collaborating easily on the files that matter most. We believe productivity is not about adding more tools but making the ones you already use work together seamlessly. Based in Porto, ikuTeam builds the invisible layer for the Atlassian ecosystem to dissolve file silos and help over a million users stay focused and move faster.
Read more: About us
team-files-vs-confluence-1

Confluence Smart Links Explained

See how they work, where they fail with external files, and more secure, consistent management alternatives.
Read more: Confluence Smart Links Explained
untitled_Flux 2 Pro_2026-03-26_21-41-00

Jira SharePoint Integration

Discover how to sync files, automate folders, and enhance collaboration in Jira Cloud and Data Center.
Read more: Jira SharePoint Integration

About us

From the start, our goal has been to remove the hidden friction that prevents teammates from collaborating easily on the files that matter most. We believe productivity is not about adding more tools but making the ones you already use work together seamlessly. Based in Porto, ikuTeam builds the invisible layer for the Atlassian ecosystem to dissolve file silos and help over a million users stay focused and move faster.
Read more: About us
Porto-pic
Product Documentation

Nov 19, 2026

4.10 Check documents at a workflow transition with the ikuTeam Files agent

Objective: Use document content to guide a workflow transition

This use case shows how to add the ikuTeam Files Agent to a Jira Automation flow that runs when a work item changes status. The agent reads a document attached to the work item with ikuTeam Files (for example, a design spec in Google Drive or a security audit in SharePoint) and gives the next person in the workflow exactly the context they need.

The agent returns its answer in the {{agentResponse}} smart value, so you can post it as a comment, write it to a field or use it in a condition. You need the Advanced Edition of ikuTeam Files for Jira and Atlassian Rovo on your site (see 5. Rovo agent).

Workflow-based capabilities

  • Automated handover summaries: Generates a concise summary of a document attached with ikuTeam Files the moment a work item changes status, so the next person in the chain has instant context.

  • Dynamic field updates: Injects specific data points from a SharePoint or Google Drive file directly into Jira custom fields using the {{agentResponse}} value.

  • Conditional branching: Uses the agent's analysis to decide the next path in a workflow, such as flagging a work item for "High Risk" if the agent detects specific keywords in a project charter.

  • Any connected storage: Reads files from SharePoint, OneDrive, Google Drive, Box, Dropbox and Egnyte, wherever the work item's files live. It reads files attached with ikuTeam Files or found by name in the folders connected to the work item or its space, not links pasted in the description.

The output is as powerful as your prompt

The utility of a workflow-based agent depends on the precision of your instructions. Because the agent understands natural language, you should experiment with prompts that match the specific stage of your workflow:

  • For QA handover: "List all functional requirements mentioned in this spec that are marked as 'High Priority'."

  • For legal review: "Identify any clauses in this contract that mention 'indemnity' or 'liability' and summarize them."

  • For release management: "Check this release note for the sections Summary, New features, Fixes and Known issues, and list any that are missing."

Use case: the smart QA transition

Instead of a developer just moving a work item to "Ready for Test," the automation flow reads the technical spec and tells the QA engineer exactly what to focus on.

How to build it:

  1. Trigger: Work item Transitioned to "Ready for Test."

  2. Action: Add Atlassian's Rovo agent action and select ikuTeam Files Agent.

  3. Prompt: "Read the file Design doc attached to {{issue.key}} and list the three most complex edge cases described in the 'Testing' section." Include the work item key so the agent can find the files, and name the file, because if several files are attached and your prompt doesn't say which one, the agent may reply with a question instead.

  4. Follow-up action: Add comment to the work item.

  5. Output: Use {{agentResponse}} to provide the QA engineer with a targeted testing focus.

Screenshot: How to integrate ikuTeam Files agent: Workflow
Screenshot: How to integrate ikuTeam Files agent: Workflow

Why this matters for admins

  • Standardized context: You ensure that every team member, regardless of their familiarity with the cloud storage structure, gets the same high-quality summary.

  • Files stay in your cloud storage: Your team reads the key points of a document in a Jira comment or field, without downloading the file and uploading it again as a Jira attachment.

  • Audit-ready insights: The agent's summaries are captured in the Jira history, providing a clear record of what information was used to make decisions at each workflow stage.

  • Secure data handling: The agent reads a file only when you ask, and we never store your files' content. It follows ikuTeam Files permissions: with Mirror Storage Permissions ON it uses each user's own storage access, and with Mirror Storage Permissions OFF it uses the folder owner's account and the app's permissions.

The end state

  • Workflows are driven by the actual content of your documents, not just manual status changes.

  • Jira work items become one place to see everything, summarizing external cloud data as work progresses.

  • Handovers between teams are faster and less prone to information gaps.

  • Admins can enforce data-driven transitions based on document analysis.

Want to go further? See 4.9 Summarize attached documents with the ikuTeam Files agent and the 4.1 ikuTeam Files Automation Actions.