Pair a shared engineering document with Codacy project context
Sharing a document often means someone needs to get oriented. Have Notis surface your accessible Codacy projects in the run report so relevant codebases are easier to spot.
Trigger
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
Action
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.
Why this helps
New collaborators may need project context, while the person sharing the document has to repeatedly explain where related repositories live.
- Make project context easier to find after a document is shared.
- Reduce repeated repository discovery for collaborators.
- Keep the report grounded in projects accessible to the connected Codacy account.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Codacy once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Describe that Notis should list accessible Codacy projects when an engineering document is shared and summarize likely project context for the report.
- 4Choose the Google Drive File Shared trigger and select where run reports should go.
- 5Test with one real shared engineering document and review the report.
Questions about this workflow
Does the workflow notify the new collaborator?
The listed Codacy action only retrieves projects. The workflow can send its run report to the report channel you choose, but it does not add a Drive comment or message the collaborator.
What if the shared file is unrelated to engineering?
Notis should say that no clear project relevance was found when the file context does not indicate an engineering document.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Codacy. A trigger fires from one place; an action lands in another.
Google Drive 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.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Get Account Details
Tool to retrieve details of the authenticated user's account. use when confirming authentication before user-level operations.
File Created
Triggers when a new file is created in Google Drive.
Get Organization Repositories
Tool to list all repositories under a specific organization and provider. use when you need to enumerate organization-scoped repositories.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Get User Organizations
Tool to list all organizations the authenticated user belongs to. use after authenticating and need to discover accessible organizations.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
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.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Connect any two apps with Notis in the middle.
Google Drive 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.