Skip to content
Notis

Check vendor details before granting repository access

A vendor access request arrives. Notis checks the supplied tax identifier with 44API, then invites the supplied GitHub user if the company details meet your instructions.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

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.

Why this helps

Vendor verification and repository invitations can become separate tasks, making it easy to grant access before the company details are checked.

  • Check the supplied VAT or tax identifier before acting on an access request.
  • Reduce repeated context switching between company verification and GitHub.
  • Keep the request and resulting invitation tied to one run report.

Setup

Build it in a few focused steps.

  • 1Connect 44API and GitHub once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a clear name and prompt.
  • 3In one instruction, ask Notis to validate the submitted tax identifier and, if it meets your criteria, invite the supplied GitHub username to the specified repository.
  • 4Choose a webhook trigger and select where run reports should go.
  • 5Test with one real vendor request, including the tax identifier, GitHub username, repository, and your validation criteria.

Questions about this workflow

What information must the webhook request include?

Include the tax identifier, the GitHub username, the repository, and enough context to apply your verification criteria. 44API provides company details for the identifier; it does not establish a relationship between a company and a GitHub username.

Does a valid tax identifier automatically grant access?

Your prompt should define what counts as a match and direct Notis to invite only when the returned company details satisfy that rule. Review the first real run before relying on it.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link 44API to GitHub. A trigger fires from one place; an action lands in another.

44API triggers

GitHub actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Accept a repository invitation

Accepts a pending repository invitation that has been issued to the authenticated user.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

List stargazers

Deprecated: lists users who have starred a repository; use `list stargazers` instead.

ActionInstant

Star a repository for the authenticated user

Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Connect any two apps with Notis in the middle.

44API 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.