Review store apps alongside Jira changes
When store-related Jira work changes, have Notis retrieve the store's app metadata and bring it into the run report for quick review.
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 Apps
Tool to list all apps associated with a specific store. use when retrieving basic metadata of every app in that store.
Why this helps
Store app context can be hard to keep in view while following changes across Jira issues.
- Bring basic app metadata into issue follow-up.
- Cut down on separate store app lookups.
- Give reviewers a current inventory to inform next steps.
Setup
Build it in a few focused steps.
- 1Connect Jira and BTCPay Server once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to list apps for the store named in the updated issue and summarize the returned metadata.
- 4Pick the Jira Updated Issue trigger and choose where run reports should go.
- 5Test with one real updated issue containing a valid store ID.
Questions about this workflow
Does this install or update a store app?
No. The supported action lists apps associated with a store and returns basic metadata.
What if the issue does not include a store identifier?
The instruction must provide a valid store identifier from the issue or another detail you supply.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Btcpay server. A trigger fires from one place; an action lands in another.
Jira triggers
Btcpay server actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Payment Request
Tool to create a new payment request for a store. use after confirming store id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Store
Tool to create a new store in btcpay server. use when you need to provision a new store before processing transactions.
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 BTCPay Server User
Tool to create a new btcpay server user. use when you need to register a new user programmatically as an administrator.
New Project
Triggered when a new project is added in Jira
Register a Webhook
Tool to register a new webhook. use when you need to receive store event notifications.
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.
Delete API Key
Tool to revoke a specific api key. use when you need to remove an api key to immediately prevent its use. call after identifying the key to revoke.
Delete Payment Request
Tool to delete a specific payment request. use when you need to archive/remove an existing payment request for a store.
Delete Store Payout
Tool to delete a specific payout from a store. use when you need to cancel a payout no longer needed.
Get API Key
Tool to retrieve the current api key. use after authentication to get api key details.
Connect any two apps with Notis in the middle.
Jira and Btcpay server, 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 Btcpay server.