Skip to content
Notis

Keep Agenty research inputs in sync with Jira

When a research request changes in Jira, update the corresponding Agenty agent input from the latest issue details.

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

Update Input by Agent ID

Tool to update agent input by agent id. use when you need to modify an agent's input source (url, manual data, list, or agent) after verifying the agent id.

Why this helps

A changed URL or research scope in Jira can leave an agent working from stale input until someone notices and updates it.

  • Reduce stale agent inputs after a Jira request changes.
  • Use Jira as the place to maintain research scope and source details.
  • Send a run report when the automation has processed an update.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Agenty once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name and prompt.
  • 3Tell Notis to update the input for the specified existing Agenty agent using the changed Jira issue's relevant research details.
  • 4Pick the Jira Updated Issue trigger and choose where run reports go.
  • 5Test with one real Jira issue update that changes the research input.

Questions about this workflow

Does this start an agent job too?

No. This workflow updates the agent input. Starting a job is a separate Agenty action.

What details should the issue contain?

Keep the source URL or other input details in the issue and tell Notis which details should become the agent input.

Do Jira comments trigger this?

No. The Updated Issue event does not fire on comment activity; it fires when an issue field changes in the configured project.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Jira to Agenty. A trigger fires from one place; an action lands in another.

Jira triggers

Agenty actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Clone Agent by ID

Tool to clone an existing agent by its id. use when you need to duplicate an agent's configuration and optionally start the clone immediately.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Agent

Tool to create a new agent. use when you need to add an agent with configuration and optional auto-start.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Get Agent Templates

Tool to fetch all public agent templates and sample agents. use when listing available templates for users to select.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Delete Agent by ID

Tool to delete a single agent by its id. use when you need to permanently remove an agent after confirming it exists.

ActionInstant

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.

TriggerInstant

Fetch all agents

Tool to fetch all active agents under an account. use after authenticating when you need to list agents with pagination and sorting.

ActionInstant

Get Agent by ID

Tool to fetch details of a specific agent by its id. use when you need full agent configuration before taking further actions.

ActionInstant

Update Agent by ID

Tool to update an agent's configuration and settings by agent id. use when you need to modify an existing agent after retrieving its current settings. example: "update agent 123 with new name and tags."

ActionInstant

Create API Key

Tool to create a new api key. use when you need to provision access credentials for the api.

ActionInstant

Connect any two apps with Notis in the middle.

Jira and Agenty, 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 Agenty.