Make transformation history part of a low-effort review
A scheduled version-history check can surface how event handling has changed before you need to investigate a specific issue.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Transformation Versions
Tool to list all transformation versions (revisions) for a given transformation ID. Use when you need to retrieve the version history of a specific transformation.
Why this helps
Transformation history is easy to ignore until a confusing result requires reconstructing what changed and when.
- Keep revision history visible as part of routine maintenance.
- Build context about how event processing evolves.
- Reduce last-minute investigation when a past change becomes relevant.
Setup
Build it in a few focused steps.
- 1Connect Copyleaks and RudderStack Transformation to Notis once through the portal.
- 2Create an automation in the portal or tell Notis to review a relevant transformation on a monthly schedule.
- 3Write one instruction asking Notis to list revisions for the transformation supporting your Copyleaks workflow.
- 4Choose a recurring monthly trigger and select a channel for run reports.
- 5Review the first history list and confirm it covers the transformation you intended.
Questions about this workflow
Does this automatically select every transformation?
The action lists versions for a given transformation, so your instruction should identify the relevant one.
Can this schedule publish or modify revisions?
No. Listing revisions is a read action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Copyleaks to RudderStack Transformation. A trigger fires from one place; an action lands in another.
Copyleaks triggers
RudderStack Transformation actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Library
Tool to create a library in RudderStack Transformation. Use when you need to create reusable JavaScript or Python code that can be imported in transformations. Libraries enable code reusability and version maintenance.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Transformation
Tool to create a RudderStack transformation. When publish=false (default), creates an unpublished transformation not available to event traffic. When publish=true, publishes the transformation making it live for incoming events and connectable to destinations.
Delete Transformation
Delete a published transformation by ID. Note that RudderStack never deletes a transformation revision. Use this when you need to remove a transformation from the system.
Get library by ID
Retrieves a single published library by its unique identifier. Use when you need to fetch details of a specific library.
Get Library Version
Tool to retrieve a single library version by library ID and version ID. Use when you need to fetch details of a specific library revision in RudderStack transformations.
Get Transformation
Tool to retrieve a published transformation by its ID from RudderStack. Use when you need to fetch details about a specific transformation including its code, version, and associated destinations.
Get Transformation Version
Retrieve a single transformation revision by transformation ID and version ID. Use when you need to get details about a specific version of a RudderStack transformation.
List All Libraries
Tool to retrieve all published libraries for a workspace. Use when you need to list available libraries for transformations.
Connect any two apps with Notis in the middle.
Copyleaks and RudderStack Transformation, 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 RudderStack Transformation.