Confirm the Codacy account when a Jira issue changes
Issue details change as work moves along. Have Notis retrieve Codacy account details so the run report includes a quick connection context check.
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
Get Account Details
Tool to retrieve details of the authenticated user's account. use when confirming authentication before user-level operations.
Why this helps
Teams can lose time when it is unclear which Codacy account an automation is using during active issue work.
- Makes the connected Codacy account visible in a run report
- Adds a lightweight access check to ongoing issue work
- Helps catch account context confusion sooner
Setup
Build it in a few focused steps.
- 1Connect Jira and Codacy once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for account access checks.
- 3Describe the outcome in one instruction: when an issue changes, retrieve Codacy account details for the run report.
- 4Pick the Jira Updated Issue trigger and choose where run reports should go.
- 5Test with one real issue update and confirm the account details appear in the report.
Questions about this workflow
Does the workflow verify repository permissions?
No. The action retrieves account details; it does not test access to a specific repository.
Do Jira comments trigger this automation?
No. The Updated Issue event does not fire for comment activity.
Can it detect whether the issue's code has passed quality checks?
No. The available Codacy actions do not report analysis results or quality status.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Codacy. A trigger fires from one place; an action lands in another.
Jira triggers
Codacy actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create API Token
Tool to create a new api token for the authenticated user's account. use after authenticating when you need to generate a fresh token for integrations.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete API Token
Tool to delete a specific api token from the authenticated user's account. use after confirming the token id.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Get Account Details
Tool to retrieve details of the authenticated user's account. use when confirming authentication before user-level operations.
New Project
Triggered when a new project is added in Jira
Get Organization Repositories
Tool to list all repositories under a specific organization and provider. use when you need to enumerate organization-scoped repositories.
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 User Organizations
Tool to list all organizations the authenticated user belongs to. use after authenticating and need to discover accessible organizations.
List Projects
Tool to list all projects accessible to the authenticated user. use when you need a list of repositories after confirming api token validity.
Connect any two apps with Notis in the middle.
Jira and Codacy, 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 Codacy.