Review AlgoDocs folders when Jira work changes
Keep the document filing landscape close to the Jira work that is moving, so people can find the right place to continue.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
List folders
Tool to list folders. Use when you need to retrieve all folder IDs and their hierarchy. Must be called after obtaining an API key.
Why this helps
As issue ownership or status changes, document locations may be scattered across folders that the team has to look up separately.
- Bring AlgoDocs folder IDs and hierarchy into the report for an updated issue.
- Reduce repeated folder lookups during active Jira work.
- Make document location context easier to share with the people following the issue.
Setup
Build it in a few focused steps.
- 1Connect Jira and AlgoDocs once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis in plain language from any channel.
- 3In one instruction, ask Notis to retrieve and summarize the AlgoDocs folder hierarchy when a Jira issue changes.
- 4Pick Jira Updated Issue as the trigger and choose where run reports should go.
- 5Test with one real issue update in the configured Jira project.
Questions about this workflow
What Jira changes trigger it?
The Updated Issue event fires when an existing issue in the configured project changes, such as its status or assignee. It does not fire for comment activity.
Does the action move or create folders?
No. The available action retrieves folder IDs and their hierarchy; it does not change AlgoDocs folders.
Does it list folders for a specific Jira issue?
The action returns the account's folder list and hierarchy. It does not accept an issue-specific folder filter.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Algodocs. A trigger fires from one place; an action lands in another.
Jira triggers
Algodocs actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Current User
Tool to retrieve current user information. Use after authenticating with your API key to verify identity.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List document data extractors
Tool to list document data extractors. Use when you need identifiers and names of all extractors in your AlgoDocs account.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
List folders
Tool to list folders. Use when you need to retrieve all folder IDs and their hierarchy. Must be called after obtaining an API key.
New Project
Triggered when a new project is added in Jira
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Connect any two apps with Notis in the middle.
Jira and Algodocs, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Algodocs.