Check Workable account context after a code alert
When GitHub raises a code scanning alert, Notis can retrieve Workable account context and report it as part of a deliberate response checklist.
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
Get Account
Tool to return the specified account. use when you need account metadata by subdomain after listing available accounts.
Why this helps
Security response pulls attention in many directions, so account context checks get lost.
- Creates a repeatable cue
- Avoids another dashboard hop
- Keeps response context together
Setup
Build it in a few focused steps.
- 1Connect GitHub and Workable once.
- 2Create a New Automation in the portal.
- 3Write a prompt to retrieve the relevant Workable account context after a code scanning alert.
- 4Select New Code Scanning Alert Created and a secure report channel.
- 5Create a safe test alert and inspect the report.
Questions about this workflow
Does this remediate the code alert?
No. It adds recruiting account context to your review workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Workable. A trigger fires from one place; an action lands in another.
GitHub triggers
Workable actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Department
Tool to delete a department. use when removing an obsolete or restructured department after confirming dependent resources.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account
Tool to return the specified account. use when you need account metadata by subdomain after listing available accounts.
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.
Get Accounts
Tool to retrieve a collection of all accounts you have access to. use when you need to list your workable accounts after authentication.
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 Background Check Packages
Tool to retrieve a list of available background check packages from a specified provider. use after identifying the provider to view available package options.
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 Background Check Providers
Tool to retrieve a list of available background check providers. use after confirming valid authentication to list integrated background check services.
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.
Get Candidates
Tool to retrieve a list of all candidates across jobs. use when you need to aggregate candidate data across your organization.
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.
Get Events
Tool to retrieve a collection of events scheduled in the account. use when you need to list all upcoming or past calls, interviews, or meetings.
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.
Get Jobs
Tool to retrieve a list of jobs from your workable account. use after validating account authentication before managing job postings.
Connect any two apps with Notis in the middle.
GitHub and Workable, 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 Workable.