Keep Appdrag records current with Jira issue updates
When a Jira ticket changes, let Notis pass the update to an Appdrag function that maintains its related record.
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
Execute Cloud Backend function via PUT (default)
Tool to execute a Cloud Backend API function via PUT on the default environment. Use when you need to call a function with PUT parameters and optional APIKey.
Why this helps
Manually revisiting backend records after Jira changes adds follow-up work and leaves stale information behind.
- Send issue changes to a backend endpoint without manual checks.
- Use an Appdrag PUT function designed to update an existing record.
- Reduce gaps between Jira ticket state and backend operational data.
Setup
Build it in a few focused steps.
- 1Connect Jira and Appdrag once in the Notis portal.
- 2Create an automation in Automations, New Automation, and enter its name and prompt.
- 3Tell Notis to send Jira issue updates to the Appdrag PUT function that updates the related record.
- 4Pick the Jira Updated Issue trigger and select a channel for run reports.
- 5Test with one real issue update and verify the function's result.
Questions about this workflow
What changes can start this automation?
The event fires when an existing issue in the configured Jira project changes, including status, assignee, or another issue field. Comment activity does not trigger it.
Will the workflow choose the correct Appdrag record?
Notis can pass available event details to the selected function, but your Appdrag function needs to identify and update the intended record.
What does the Appdrag action do?
It calls a Cloud Backend function via PUT on the default environment. The function defines the update behavior.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Appdrag. A trigger fires from one place; an action lands in another.
Jira triggers
Appdrag actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Execute Cloud Backend function via DELETE
Tool to execute a Cloud Backend API function via DELETE on the default environment. Use when you need to call a function with DELETE parameters and optional APIKey.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Execute Preprod Function (DELETE)
Tool to execute the pre-production version of a Cloud Backend API function via DELETE. Use when you need to test or validate delete operations in the preprod environment before production deployment.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Execute PROD API Function (GET)
Tool to execute a production Cloud Backend API function via GET. Includes robust URL handling and fallbacks to accommodate management base URLs.
New Project
Triggered when a new project is added in Jira
Execute Dev Function (PATCH)
Tool to execute the development version of a Cloud Backend API function via PATCH. Use after deploying or updating your function to the dev environment.
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.
Execute Cloud Backend function via POST
Tool to execute a Cloud Backend API function via POST on the default environment. Use when you need to call a function with POST parameters and optional APIKey.
Execute Function POST (Preprod Env)
Tool to execute a Cloud Backend API function via POST on the preprod environment. Use when you need to test a function in the preprod environment before releasing to production. Include apiKey if your function requires APIKey security.
Execute Cloud Backend function via PUT (default)
Tool to execute a Cloud Backend API function via PUT on the default environment. Use when you need to call a function with PUT parameters and optional APIKey.
Execute Cloud Backend function via PUT (preprod)
Tool to execute a Cloud Backend API function via PUT on the preprod environment. Use when you need to call a function with PUT parameters and optional APIKey in preprod.
Connect any two apps with Notis in the middle.
Jira and Appdrag, 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 Appdrag.