Coordinate collaborator changes with DataRobot group access
A Box role or status change can signal a need to review model workspace access. Notis can add a user to a group you specify when appropriate.
Trigger
Collaboration Details Changed
Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.
Action
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.
Why this helps
Access changes in shared files and modeling tools can drift apart when teams manage them in separate places.
- Tie access review activity to a meaningful Box collaboration change.
- Reduce the chance of forgetting a related DataRobot group addition.
- Keep group changes grounded in your team's access policy.
Setup
Build it in a few focused steps.
- 1Connect Box and DataRobot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis when a collaboration change should add the identified existing username to the specified DataRobot group.
- 4Pick the Box Collaboration Details Changed trigger and choose where run reports go.
- 5Test with one real collaboration change that meets your access policy and confirm the group update.
Questions about this workflow
Does the action remove users when Box access changes?
No. The listed action adds users to a group. It does not remove group members.
Can the workflow infer the right group from a Box role?
The event description does not define a mapping from Box roles to DataRobot groups. State the policy and group in your instruction.
Are there limits on users per request?
Yes. The action supports up to 100 users per request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Box to Datarobot. A trigger fires from one place; an action lands in another.
Box 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.
Collaboration Details Changed
Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.
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.
Comment Changed
Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.
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.
New File Comment Added
Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.
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.
File Metadata Changed
Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.
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.
File Shared Link Changed
Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.
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.
New File Version Uploaded
Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.
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.
Box 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.