Keep deployment assets ready for release
A deployment should not send you hunting through folders for the asset it depends on.
Trigger
New Deployment Created
Triggers when a new deployment is created in a GitHub repository. Fires an event for each newly created deployment detected in the configured repository. Deployments can optionally be filtered by target environment. The payload includes the deployment ID, commit SHA, ref, task, environment, creator details, and timestamps.
Action
Get Resource by Asset ID
Get resource by asset id
Why this helps
Release work gets stalled when the right image, video, or build asset is hard to locate.
- Find the relevant asset immediately after deployment creation
- Reduce release-day tab switching
- Keep asset details available for a quick sanity check
Setup
Build it in a few focused steps.
- 1Connect GitHub and Cloudinary to Notis once through the portal.
- 2In Automations, create an automation with a plain-language instruction to retrieve the Cloudinary asset associated with each new GitHub deployment.
- 3Select the GitHub new deployment trigger, choose a channel for run reports, and test with one deployment.
Questions about this workflow
What does Notis retrieve?
Notis uses the deployment context to find and return the relevant Cloudinary resource details.
Can I use this for staging deployments?
Yes. Set the GitHub trigger to the repository and environment you want to monitor.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Cloudinary. A trigger fires from one place; an action lands in another.
GitHub triggers
Cloudinary actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Create Folder
Tool to create a new asset folder. use when you need to organize assets into nested directories. use after confirming the folder path does not already exist.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Create Metadata Field
Tool to create a new metadata field definition. use when extending your metadata schema with new fields.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Trigger
Tool to create a new webhook trigger for a specified event type. use after configuring your webhook endpoint and choosing the event type. example: "create a trigger for uploads to https://example.com/hooks/cloudinary"
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Create Upload Mapping
Tool to create a new upload mapping folder and url template. use when you need to dynamically map external url prefixes to a cloudinary asset folder before uploading files.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Create Upload Preset
Tool to create a new upload preset. use when defining centralized upload options (tags, formats, transformations, etc.) before asset uploads.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Delete Derived Resources
Tool to delete derived assets. use when you need to remove specific derived assets by their ids. example: "delete derived assets with ids [id1, id2]".
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Delete Metadata Field Datasource Entries
Tool to delete datasource entries for a specified metadata field. use when you need to soft-delete (inactivate) specific entries in a field's datasource. example prompt: "delete entries ['color1','color2'] from metadata field 'color id'"
Commit Event
Triggered when a new commit is pushed to a repository.
Delete Folder
Tool to delete an empty asset folder. use when the folder is confirmed empty and you need to remove it.
Connect any two apps with Notis in the middle.
Not just GitHub and Cloudinary. Any 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 Cloudinary.