Invite new GitHub collaborators to Workable
When a collaborator is added to your hiring repository, Notis can invite them to Workable so access does not become another task to remember.
Trigger
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.
Action
Invite Member
Tool to invite a member to your workable account. use when sending an invitation email.
Why this helps
Founders often grant engineering access first and postpone the HR invitation until it is forgotten.
- Reduces duplicate onboarding chores
- Keeps recruiting collaborators reachable
- Reports each invitation
Setup
Build it in a few focused steps.
- 1Connect GitHub and Workable to Notis once in the portal.
- 2Open Automations and choose New Automation.
- 3Write a prompt to invite approved new repository collaborators to Workable.
- 4Pick the GitHub New Repository Collaborator Added trigger and a report channel.
- 5Add one real collaborator to a test repository and review the run.
Questions about this workflow
Will this invite every collaborator?
Describe your approval rule in the prompt so Notis only invites the people you intend.
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.