Automatically Grant GitHub Codespaces Access to New Team Members
New developers should be able to code immediately in Codespaces. When a team member joins in Hubspot, Notis automatically grants them Codespaces access.
Trigger
Contact Created Trigger
Contact Created Trigger
Action
Add users to codespaces access for an organization
Sets or replaces the list of organization members granted codespaces access billed to the organization; ensure the organization's billing settings allow access for selected members.
Why this helps
New developers sit waiting for Codespaces access. Managers manually configure it, or new hires have to ask, adding friction to onboarding.
- New developers have Codespaces access immediately upon joining
- No manual Codespaces configuration required
- Developers can start coding in cloud environments right away
- Reduces onboarding friction and dev environment setup time
Setup
Build it in a few focused steps.
- 1Connect Hubspot and GitHub to Notis.
- 2Ask Notis: 'When a new team member is created in Hubspot, grant them Codespaces access for the organization.'
- 3Set Contact Created as your trigger.
- 4Choose your notification channel.
- 5Test by creating a team member in Hubspot and confirming they appear in GitHub Codespaces settings.
Questions about this workflow
Do they get access to all repositories?
Yes, Codespaces access is org-wide. If you need per-repo restrictions, you can set that in GitHub settings separately.
Does this charge the organization?
Codespaces usage is billed per organization. Granting access just allows the developer to use it; actual charges depend on their usage.
Can I revoke access automatically?
Yes, set up another automation for when team members leave, or tell Notis to revoke access based on a specific Hubspot event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Hubspot to GitHub. A trigger fires from one place; an action lands in another.
Hubspot triggers
GitHub actions
Contact Created Trigger
Contact Created Trigger
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Not just Hubspot and GitHub. 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 GitHub.