Turn recurring risk reviews into DataRobot monitoring setup
Use a scheduled check-in to keep deployment monitoring setup connected to ongoing risk review.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Create Batch Monitoring Job Definition
Tool to create a Batch Monitoring job definition for tracking deployment performance and data drift. Use when you need to set up scheduled or manual monitoring jobs for a DataRobot deployment.
Why this helps
Monitoring setup can lag when teams review risk regularly but configure model monitoring separately.
- Create monitoring setup from a recurring review routine.
- Keep the deployment and monitoring rationale together in the request.
- Reduce the chance of forgetting to configure batch monitoring.
Setup
Build it in a few focused steps.
- 1Connect 21risk and DataRobot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for recurring deployment monitoring setup.
- 3Tell Notis to use the supplied risk review context to create a DataRobot batch monitoring job definition for the identified deployment.
- 4Choose a recurring schedule trigger and choose where run reports should go.
- 5Test with one real deployment and confirm the definition details are appropriate.
Questions about this workflow
Does this schedule monitor the deployment by itself?
It creates a batch monitoring job definition. The request should specify the relevant deployment and intended monitoring details; this action does not itself promise ongoing execution.
Can the workflow invent a baseline for comparison?
No. Supply any baseline or comparison details needed; the source description does not promise those values are available automatically.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 21risk to Datarobot. A trigger fires from one place; an action lands in another.
21risk triggers
Datarobot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Users to Group
Tool to add one or more users to a DataRobot user group by groupId. Use when you have a valid groupId and want to add existing usernames. Limit 100 users per request.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add User to Organization
Tool to add a user to an existing organization. Use when you have an organizationId and wish to add or create a user within it.
Analyze Dataset Definition
Tool to analyze a dataset definition by ID. Use when you need to trigger an analysis job that retrieves dataset metadata, schema, and statistics.
Archive Model Package
Tool to archive a DataRobot model package. Use when you need to archive a model package that is no longer actively used.
Build Java Scoring Code Package
Initiates an asynchronous build of a Java JAR package containing DataRobot Scoring Code for a deployment. The JAR can be executed locally for predictions or used as a library in Java applications. Use after confirming the deployment is active and supports scoring code. Poll the returned statusId or location URL to track build progress.
Cancel Notebook Job
Tool to cancel a running or pending notebook job execution. Use when you need to stop a notebook job that is currently executing or queued. The cancellation is immediate and cannot be undone.
Cancel Project Job
Tool to cancel a pending job for a project. Use when you need to stop a queued or running job after confirming its ID.
Check Project Status
Tool to check the status of a DataRobot project. Use after creating or loading a project to monitor its stage and Autopilot completion.
Connect any two apps with Notis in the middle.
21risk and Datarobot, 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 Datarobot.