Make missed campaign targets visible in GitHub
When campaign results cross a threshold you set, put the follow-up label on the issue that owns the work.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
A campaign can miss its target while the issue tracking its fix stays unnoticed.
- Surface a missed target in the issue where work is tracked.
- Use a threshold you supply rather than an assumed benchmark.
- Keep campaign review tied to an existing GitHub issue.
Setup
Build it in a few focused steps.
- 1Connect Benchmark email and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis what result threshold to check, which existing GitHub issue to update, and which review label to add when the threshold is missed.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real webhook request containing campaign results.
Questions about this workflow
Where does the webhook data come from?
The Notis webhook starts the automation when it receives an HTTP request. Include the campaign results you want Notis to review.
What threshold should I use?
Choose a threshold that fits your campaign goals and include it in the instruction. Notis does not assume a target or baseline.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Benchmark email to GitHub. A trigger fires from one place; an action lands in another.
Benchmark email 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.
Benchmark email 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.