Create a BigML project from an incoming webhook
Turn incoming product signals into an organized workspace without copying details between systems.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Project
Tool to create a new project. use when you need to group related bigml resources into a project.
Why this helps
Requests from outside GitHub can require repetitive handoffs before model work even begins.
- Captures requests from your existing tools
- Reduces copy-paste handoffs
- Creates a clear place to begin
Setup
Build it in a few focused steps.
- 1Connect GitHub and BigML to Notis once.
- 2Create a new automation in the portal.
- 3Ask Notis to create a BigML project when your external system sends a model request.
- 4Select an incoming webhook and a report channel.
- 5Send one test webhook and review the run.
Questions about this workflow
Can any external tool start this?
Any tool or backend that can send the configured HTTP request can start the webhook workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Bigml. A trigger fires from one place; an action lands in another.
GitHub triggers
Bigml actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create External Connector
Tool to create a new external connector for data sources. use after configuring external databases or search indices.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Project
Tool to create a new project. use when you need to group related bigml resources into a project.
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.
Delete Project
Tool to delete an existing project. use when you need to permanently remove a project resource after confirming it is not in use by other resources.
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.
Get External Connector
Tool to retrieve details of an external connector. use after creating or listing external connectors to inspect its state.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Project
Tool to retrieve details of a project by id. use when you need to inspect project metadata before analysis.
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.
List Correlations
Tool to list correlation resources. use when you need to browse or paginate existing correlations for the authenticated user.
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.
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.
Connect any two apps with Notis in the middle.
GitHub and Bigml, 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 Bigml.