Check which languages Codacy detects in a repository
Get a quick language and extension snapshot for the repository named in your document workflow.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Organizations Repositories Settings Languages
List programming languages detected and enabled for repository analysis.
Why this helps
Before reviewing repository analysis, you may need to check which languages are enabled and discover that context is buried in Codacy.
- See detected languages, extensions, and enabled status for a requested repository.
- Keep document processing context alongside the repository readiness result.
- Spot language setup questions before spending time reviewing analysis results.
Setup
Build it in a few focused steps.
- 1Connect Affinda and Codacy once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for repository language checks.
- 3Describe the outcome in one instruction: use the repository identifier supplied with the parsed document context to retrieve Codacy language settings and summarize enabled languages.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real document payload that includes a valid Codacy repository identifier.
Questions about this workflow
Does Affinda provide the repository identifier automatically?
Only if the document contains it and the parsed payload includes it. Otherwise include the repository identifier with the webhook request.
Can the workflow enable a language for analysis?
No. The available Codacy action retrieves language settings; it does not change them.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Affinda to Codacy. A trigger fires from one place; an action lands in another.
Affinda triggers
Codacy actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create API Token
Creates an account token with the account owner’s permissions.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete API Token
Deletes a token from the authenticated user’s account.
Get Account Details
Retrieves details for the authenticated user’s account.
Get Configuration Status
Retrieve the system’s configuration status.
Get User Organizations
Lists organizations the user belongs to for a connected Git provider.
Get Health
Check API health and availability.
List Projects
Lists projects the authenticated user can access.
Get Organizations Repositories Settings Languages
List programming languages detected and enabled for repository analysis.
Connect any two apps with Notis in the middle.
Affinda 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.