Bring Agiled's user directory into Jira intake
Keep a current list of Agiled users close to new Jira work when you need to decide who should follow up.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Get Users
Tool to retrieve a list of users from agiled. use when you need the full user directory for selection or validation.
Why this helps
Routing work across tools gets slower when you have to leave intake to look up who is available in Agiled.
- Reduce context switching during intake triage.
- See available Agiled users in the automation report.
- Support routing decisions with a current directory lookup.
Setup
Build it in a few focused steps.
- 1Connect Jira and Agiled once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Ask Notis to retrieve Agiled users when a new Jira issue arrives and summarize the directory for your review.
- 4Select the Jira New Issue trigger for the relevant project and choose where run reports go.
- 5Test with one real issue and review the returned user list.
Questions about this workflow
Does this assign an Agiled task?
No. This workflow retrieves the Agiled user directory. The selected action does not create or assign a task.
Can the report recommend an owner?
You can ask for a recommendation if the issue and returned user information support your rule. Supply any availability or role details that are not provided.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Agiled. A trigger fires from one place; an action lands in another.
Jira triggers
Agiled actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Expense
Tool to create a new expense in agiled. use after gathering expense details and authenticating with your api key.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Project
Tool to create a new project in agiled. use when you have collected all project details and need to set up the project before assigning tasks. example: "create a new project named website redesign with start date 2023-09-01 and status in progress."
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create Task
Tool to create a new task in agiled. use when you have all task details and want to add it to your project board. example: "create a task titled 'draft specs' for project 45, assigned to user 7, priority normal, due date 2025-11-05."
New Project
Triggered when a new project is added in Jira
Create Ticket
Tool to create a new support ticket in agiled. use after gathering all required ticket details (subject, message, priority, user id).
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.
Get Contacts
Tool to retrieve a list of all contacts. use after configuring the api key to fetch contacts with optional pagination or search filters.
Get Currencies
Tool to list currencies. use when you need to fetch available currency options after authentication.
Get Deals
Tool to retrieve a list of all deals. use after confirming your api key to list all deals for crm reporting.
Get Employees
Tool to retrieve a list of all employees. use when you need up-to-date employee directory from agiled.
Connect any two apps with Notis in the middle.
Jira and Agiled, 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 Agiled.