Know what event paths exist after a moderation review
A moderation result can be a cue to check the transformations already available for its follow-up data.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
List All Transformations
Tool to retrieve all published transformations for a workspace. Use when you need to list available transformations or find a specific transformation by name.
Why this helps
Moderation findings may need quick operational follow-up, but finding the right event path can become another task to remember.
- Locate available transformations after a moderation analysis completes.
- Support a consistent follow-up process for moderation events.
- Reduce the chance that a result sits without a clear data path.
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 ask Notis in plain language to respond to moderation completion notifications.
- 3In one instruction, ask Notis to list transformations for moderation event follow-up.
- 4Select an incoming webhook trigger and choose a run-report channel.
- 5Send one real moderation completion notification and review the transformation list.
Questions about this workflow
Does this workflow decide how to handle a moderation result?
No. It lists transformations to help you inspect available event-processing paths.
How is moderation completion detected?
A Copyleaks-connected backend or external tool sends the event to the Notis webhook.
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.