Get code scanning alerts where your team can act on them
Bring new code scanning findings into Backendless so security issues are easier to spot and follow up.
Trigger
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.
Action
Publish Message
Tool to publish a message to a specified messaging channel. use when you need to send notifications or events to subscribers after confirming channel and payload.
Why this helps
Security findings can be missed when they live in a separate GitHub view from your team's daily work.
- See new findings in a familiar Backendless channel.
- Keep alert details close to the team's follow-up work.
- Reduce the need to monitor GitHub manually.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Backendless in the Notis portal once.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Describe in one instruction how Notis should notify Backendless about each new code scanning alert.
- 4Pick the GitHub New Code Scanning Alert Created trigger and choose where run reports go.
- 5Test with one real alert and confirm the channel message includes useful details.
Questions about this workflow
Can I narrow which alerts trigger this automation?
The GitHub trigger supports filters such as reference, scanning tool, state, and severity. Pick the filters when selecting the trigger.
Where will the alert appear?
Notis publishes the alert details to the Backendless messaging channel named in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Backendless. A trigger fires from one place; an action lands in another.
GitHub triggers
Backendless actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Copy File
Tool to copy a file or directory within backendless file storage. use when duplicating files to a new location after verifying source and destination paths.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Directory
Tool to create a new directory at the specified path. use when you need to organize files under a new folder structure.
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.
Create Backendless Hive
Tool to create a new hive. use when you need to provision a new hive resource before performing hive operations. example: create a hive named 'grocerystore'.
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.
Create Backendless Timer
Tool to create a new timer with schedule and code. use when scheduling recurring or one-off tasks to run server-side logic after confirming parameters.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Directory
Tool to delete a directory at the specified path in backendless file storage. use when you need to remove folders after confirming the path.
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.
Delete File
Tool to delete a file at the specified path in backendless file storage. use after confirming the file's relative path and filename.
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.
Delete Backendless Timer
Tool to delete a backendless timer by name. use when you need to remove a scheduled timer after confirming its name.
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.
Directory Listing
Tool to retrieve a listing of files and directories at a given path. use when browsing or filtering file storage directories.
Connect any two apps with Notis in the middle.
GitHub and Backendless, 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 Backendless.