Keep Cloudinary asset follow-ups organized on a schedule
Have Notis revisit a defined set of assets and related issues on a schedule, then label issues that need review or follow-up.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Asset review backlogs can grow quietly, while GitHub issues lose visibility as teams move between launches.
- Surface follow-up work from a defined Cloudinary asset set.
- Keep issue status visible with GitHub labels.
- Avoid relying on memory to revisit an asset backlog.
Setup
Build it in a few focused steps.
- 1Connect Cloudinary and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Describe the review outcome in one instruction and provide the asset set or criteria and related issue references.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real asset and its GitHub issue.
Questions about this workflow
Does the schedule discover every asset that needs review automatically?
Only if your instruction defines how to identify them using available Cloudinary data. Supply any backlog or baseline that Cloudinary does not provide.
Can it label the related GitHub issue?
Yes. The GitHub action adds labels to a repository issue and creates labels that do not already exist.
What triggers the workflow?
A recurring Notis schedule starts it. Cloudinary does not provide trigger events in this package.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cloudinary to GitHub. A trigger fires from one place; an action lands in another.
Cloudinary triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Cloudinary and GitHub, 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 GitHub.