Turn Account Handoffs into GitHub Team Membership
Review account handoffs on a schedule and make the requested team membership update visible in GitHub.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add or update team membership for a user
Adds a github user to a team or updates their role (member or maintainer), inviting them to the organization if not already a member; idempotent, returning current details if no change is made.
Why this helps
A sold account or partner handoff may require team access, but that membership task can be lost among follow-up notes.
- Bring requested membership tasks into a regular review.
- Set the requested member or maintainer role for an existing team.
- See the outcome in the Notis run report.
Setup
Build it in a few focused steps.
- 1Connect Capsule CRM and GitHub once in the Notis portal.
- 2Create an automation in Automations > New Automation and name it for account access handoffs.
- 3In one instruction, tell Notis to find eligible handoffs and use the supplied GitHub organization, team slug, username, and requested role to update membership.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real handoff for a team that already exists.
Questions about this workflow
Does this create a GitHub team?
No. The action adds a user to a team or updates their role. The organization and team must already exist.
What if the person is not in the organization?
The action description says it invites the user to the organization if they are not already a member. Organization policy may still affect the result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Capsule crm to GitHub. A trigger fires from one place; an action lands in another.
Capsule crm triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
Capsule crm and GitHub, 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 GitHub.