Turn new Jira issues into Appdrag intake records
New Jira work can reach your Appdrag backend as it appears, without another inbox to monitor.
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
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.
Why this helps
New issues can get buried while you switch between Jira and the systems that support your product.
- Capture new project issues in an Appdrag endpoint promptly.
- Reduce manual copying between Jira and backend operations.
- Keep intake handling close to your existing Appdrag workflows.
Setup
Build it in a few focused steps.
- 1Connect Jira and Appdrag once in the Notis portal.
- 2Create an automation from Automations, New Automation, then give it a name and prompt.
- 3Tell Notis to send each new Jira issue to the Appdrag function that records your intake.
- 4Pick the Jira New Issue trigger and choose where run reports should go.
- 5Test with one real issue and confirm the Appdrag function responds as expected.
Questions about this workflow
Which Jira issues trigger this workflow?
Only new issues created in the Jira project configured for the event trigger it.
Does this create an Appdrag database row by itself?
The selected action calls an Appdrag Cloud Backend function with POST. That function must implement the record creation you want.
Can I decide what details Notis includes?
Yes. Describe the outcome in the automation instruction. The connected Jira event and Appdrag function determine which details are available and accepted.
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.