Skip to content
Notis

Keep DataRobot Projects Current with GitHub Issue Changes

When a tracked issue changes, Notis can summarize what moved and add the update to the DataRobot project you identify, helping the team stay aligned without another manual check.

Trigger

Issue State / Properties Changed

Triggers when a specific GitHub issue changes any of its tracked properties. Monitored properties: state (open/closed), state_reason, title, body, assignees, labels, milestone, lock status, active_lock_reason, comment count, and closed_at timestamp. When a change is detected, the payload includes the full current issue details, the list of changed field names, and their previous values.

Action

Create Comment

Tool to create a comment on a DataRobot entity (deployment, use case, model, catalog, etc.). Use when you need to add notes, feedback, or documentation to DataRobot objects.

Why this helps

Issue changes can affect model work, but keeping project context current often relies on someone remembering to copy updates.

  • Surface relevant issue changes alongside model work.
  • Reduce repeated checks across project trackers.
  • Keep a concise history of issue updates in DataRobot.

Setup

Build it in a few focused steps.

  • 1Connect GitHub and DataRobot once in the Notis portal.
  • 2Create an automation in Automations > New Automation, or describe your desired outcome to Notis in plain language.
  • 3Ask Notis to summarize relevant changes and comment on the DataRobot project you identify.
  • 4Pick Issue State / Properties Changed, choose where run reports go, and test with one real issue change.

Questions about this workflow

What changes can trigger this workflow?

The trigger monitors properties including state, title, body, assignees, labels, milestone, lock status, comment count, and closed timestamp.

Can I limit the note to certain types of issue changes?

State the relevant changes in your instruction. Notis can analyze the event data, but do not assume the trigger has a user-built field filter.

How is the right DataRobot project selected?

Specify it in your instruction or provide a reliable lookup rule. The GitHub issue event does not itself identify a DataRobot project.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link GitHub to Datarobot. A trigger fires from one place; an action lands in another.

GitHub triggers

Datarobot actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

New Workflow Artifact Created

Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.

TriggerPolling

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.

ActionInstant

Branch Changed

Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.

TriggerPolling

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.

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

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.

ActionInstant

Check Run Status / Conclusion Changed

Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.

TriggerPolling

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.

ActionInstant

Check Suite Status / Conclusion Changed

Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.

TriggerPolling

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.

ActionInstant

New Code Scanning Alert Created

Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.

TriggerPolling

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.

ActionInstant

Connect any two apps with Notis in the middle.

GitHub 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.