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.3 Automation example 1: Create and connect a folder for new work items

Objective: Create a SharePoint or OneDrive folder and connect it to every new work item

This guide shows you how to set up a Jira Automation flow that creates a folder in SharePoint or OneDrive and connects it to each new Jira work item (previously called an issue) as soon as the work item is created.

Once it's set up, every new work item in your space gets its own folder, named after the work item key and summary. You build it with SharePoint Connector for Jira, which works with SharePoint, OneDrive for Business and OneDrive.

Key features

  • Automated folder creation: Every new work item gets a dedicated SharePoint or OneDrive folder the moment it's created.

  • Centralized file management: Keep work item documents in SharePoint or OneDrive while keeping full visibility in Jira.

  • Less IT overhead: No more creating and linking folders by hand, so your IT team can focus on higher-priority work.

Example use case

Your design team needs a dedicated folder for every new Design work item. It holds high-resolution mockups, Figma exports, and brand assets without cluttering Jira. With this flow, each new Design work item gets its own folder, ready before anyone uploads a file.

Prerequisites

  • SharePoint Connector for Jira is installed on your Jira site.

  • You have permission to create automation flows in the space (space admin) or globally (Jira admin).

  • You have access to a SharePoint or OneDrive account. You'll authenticate it while setting up the "SharePoint - Create folder" action.

  • The flow runs as the user set in Actor, in the flow's Settings panel. That person needs access to the app and permission on the folder. With Mirror Storage Permissions ON, they must also have signed in to the SharePoint or OneDrive account.

  • Your site has the Advanced Edition of SharePoint Connector for Jira. The automation actions are part of it.

Automation steps

Step 1: Set the trigger and condition

  • Create a new flow and set the trigger to "Work item created". The flow runs as soon as a new work item is created.

    Flow trigger set to Work item created
  • Add a "Work item fields condition" and set "Work type" to Design, so the flow only runs for design work items.

Step 2: Add the "Create folder" action

  • Add a new action, search for "SharePoint - Create folder", and select it.

    Action picker with the Create folder action
  • Click "Connect" and authenticate your SharePoint or OneDrive account.

    Create folder action with the Connect button
  • Choose the parent folder where the new folders will be created.

    Cloud storage folder picker with a parent folder selected

Step 3: Name the folder with smart values

  • In the "Folder name" field, enter smart values so each folder gets a unique, recognizable name, for example {{issue.key}} - {{issue.summary}}.

    Create folder action with smart values in the Folder name field
  • Type the smart values exactly as shown. They still say "issue", even though Jira now calls them work items.

  • Some work item summaries contain characters SharePoint and OneDrive don't allow in folder names, like / or :. When that happens, the action stops with a message that the folder name isn't valid. If your summaries often have these characters, use {{issue.key}} on its own.

  • Keep "Use the existing folder" selected under "If a folder with this name already exists", so the flow reuses the work item's folder instead of stopping if it's already there.

Step 4: Connect the folder to the work item

  • Add another action and search for "SharePoint - Connect a folder".

    Action picker with the Connect a folder action
  • Select "Use folder from previous step". The folder created in step 2 is connected to the work item that triggered the flow, so your team sees it on the work item right away.

    Connect a folder action with Use folder from previous step selected

Save and turn on the flow, and your automation is ready to create and connect a folder for every new work item.

Best practices and safety

  • Test first. Run new flows in a sandbox or staging environment before turning them on in production. It's the easiest way to confirm the folder structure fits your team's needs.

  • Check the audit log. If folders aren't appearing as expected, the flow's "Audit log" is the best place to find out why. It shows every time the flow ran, or failed to run.

  • Use the work item key in folder names. Keys are unique, so folders stay easy to tell apart even when work items have similar summaries.

Wrap up

With this flow in place, every new work item starts with its own folder, ready for your team's files. To see every action you can use, read 4.1 SharePoint Connector automation actions. If you need a hand, reach out on our support portal.