Check repository star status during a request
Quickly check a specific GitHub repository's star status when the question arrives through ActiveCampaign.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check if repo starred by auth user
Use to determine if the authenticated user has starred a specific github repository, which is confirmed by an http 204 status (resulting in an empty dictionary in the response data); the action fails (e.g., http 404) if the repository is not starred or does not exist.
Why this helps
Small repository checks can interrupt focused work when they require a manual GitHub lookup.
- Handle a repository check without switching contexts
- Send the result to a selected report channel
Setup
Build it in a few focused steps.
- 1Connect ActiveCampaign and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, ask Notis to check whether the authenticated GitHub account starred the repository in the webhook request.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real request that includes a repository owner and name.
Questions about this workflow
Whose star status does this check?
It checks the GitHub account connected to Notis, not another user's account.
What if the repository is not starred?
The check can return an error such as not found for an unstarred or nonexistent repository. Review the run report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Active campaign to GitHub. A trigger fires from one place; an action lands in another.
Active campaign 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.
Active campaign 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.