Review Cloudinary transformation naming
A recurring naming review can help your team find transformation definitions that do not follow the conventions you use.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Transformations
Tool to list all transformations (named and unnamed). use when you need to retrieve transformation definitions or paginate through transformation records.
Why this helps
Transformation names that vary by team or project make it harder to identify the right option during asset work.
- Compare available definitions with a naming standard you supply.
- Surface potential naming inconsistencies for follow-up.
- Make transformation lists easier to scan.
Setup
Build it in a few focused steps.
- 1Connect Cloudinary in the Notis portal and prepare the transformation naming rules to include in your instruction.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis to retrieve transformations, compare their names with your supplied rules, and summarize possible inconsistencies.
- 4Pick a recurring schedule and choose where run reports go.
- 5Test with one run and check that the naming rules are applied as intended.
Questions about this workflow
Will this rename a transformation?
No. It lists definitions and reports possible inconsistencies for review.
Can it check transformations that are not named?
The action can retrieve named and unnamed transformations. Tell Notis how you want unnamed definitions represented in the review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agent mail to Cloudinary. A trigger fires from one place; an action lands in another.
Agent mail triggers
Cloudinary actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Metadata Field
Tool to create a new metadata field definition. use when extending your metadata schema with new fields.
New Email Received
Trigger for new emails in an AgentMail inbox
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"
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.
Create Upload Preset
Tool to create a new upload preset. use when defining centralized upload options (tags, formats, transformations, etc.) before asset uploads.
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]".
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'"
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.
Agent mail and Cloudinary, 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 Cloudinary.