Keep Beaconstac campaign end dates from slipping by
Turn campaign timing into visible follow-up so the team can close, renew, or review campaigns on time.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Campaigns that need to end or renew can be forgotten when timing lives in a separate analytics tool.
- Make campaign timing follow-up visible
- Reduce forgotten renewals or closures
- Keep operational tasks in GitHub
Setup
Build it in a few focused steps.
- 1Connect Beaconstac and GitHub once in the Notis portal.
- 2Create an automation by telling Notis to review available campaign end date information and create GitHub issues for campaigns meeting your stated timing rule.
- 3Pick a recurring schedule and choose where run reports should go.
- 4Test with one real campaign record that includes relevant timing information.
Questions about this workflow
Are campaign end dates guaranteed to be available?
The source description does not specify campaign date fields. This works only if Beaconstac data available to Notis includes the dates, or you supply them.
Can Notis decide when an issue should be created?
State the timing rule, such as how far ahead of an end date to create a follow-up.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Beaconstac to GitHub. A trigger fires from one place; an action lands in another.
Beaconstac 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.
Beaconstac 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.