Create a Workable department from a GitHub workflow
When a new GitHub Actions workflow represents an approved team launch, Notis can create the matching Workable department and report it.
Trigger
New GitHub Actions Workflow Added
Triggers when a new GitHub Actions workflow is added to a repository. Monitors a repository's GitHub Actions workflows and fires an event for each newly added workflow. The payload includes the workflow's name, file path, state, creation and update timestamps, and URLs for the API, web interface, and status badge.
Action
Create Department
Tool to create a department in your account. use when you need to add a new department for organizing teams under your workable account.
Why this helps
New team structures are announced in engineering work, while HR organization updates get delayed.
- Captures a launch signal
- Reduces administrative follow-through
- Keeps team structure current
Setup
Build it in a few focused steps.
- 1Connect GitHub and Workable to Notis once.
- 2Create a New Automation in the portal.
- 3Write a prompt to create a department only for approved new team workflows.
- 4Select New GitHub Actions Workflow Added and a report channel.
- 5Add a clearly named test workflow and confirm the reported result.
Questions about this workflow
How do I prevent unwanted departments?
State a clear approval convention or naming rule in your plain-language prompt.
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
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 Department
Tool to delete a department. use when removing an obsolete or restructured department after confirming dependent 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 Account
Tool to return the specified account. use when you need account metadata by subdomain after listing available accounts.
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 Accounts
Tool to retrieve a collection of all accounts you have access to. use when you need to list your workable accounts after authentication.
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 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.
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 Background Check Providers
Tool to retrieve a list of available background check providers. use after confirming valid authentication to list integrated background check services.
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 Candidates
Tool to retrieve a list of all candidates across jobs. use when you need to aggregate candidate data across your organization.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
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.
Commit Event
Triggered when a new commit is pushed to a repository.
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.
Not just GitHub and Workable. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Workable.