See accessible Codacy organizations when Jira adds a project
A new Jira project can mean a new team or workstream. Ask Notis to list the Codacy organizations available to you as part of the setup handoff.
Trigger
New Project
Triggered when a new project is added in Jira
Action
Get User Organizations
Tool to list all organizations the authenticated user belongs to. use after authenticating and need to discover accessible organizations.
Why this helps
New project setup can lose momentum when the team has to manually confirm which Codacy organizations are available.
- Makes the available Codacy organizations easier to find
- Adds a useful Codacy check to project setup
- Surfaces access limitations early
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 new project setup.
- 3Describe the outcome in one instruction: when Jira adds a project, list the organizations available to the authenticated Codacy user.
- 4Pick the Jira New Project trigger and choose where run reports should go.
- 5Test with one real Jira project creation and review the organization list in the report.
Questions about this workflow
Does this create a Codacy organization?
No. The available action only lists organizations the authenticated user belongs to.
Does this trigger run for existing Jira projects?
No. It fires when a new Jira project is added.
Can the workflow choose a Codacy organization for the project?
No. It can report the accessible organizations, but the listed Codacy actions do not create or configure projects.
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.