Keep Basecamp bug reports and GitHub triage in sync
Set a predictable review rhythm for bug reports that need their existing GitHub issues labeled.
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
Bug reports can be easy to miss when triage only happens after someone remembers to check project discussions.
- Create a regular review point for Basecamp bug reports.
- Apply labels to existing GitHub issues using stated triage details.
- Send a report when information is missing or an issue cannot be matched.
Setup
Build it in a few focused steps.
- 1Connect Basecamp and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe in one instruction how to review recent Basecamp bug reports and apply explicitly requested labels to matching GitHub issues.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real bug report and its matching GitHub issue.
Questions about this workflow
Does the schedule create a GitHub issue for each report?
No. It applies labels to matching existing issues. A report without a clear issue reference should be surfaced in the run report.
Can the schedule infer the right labels?
Use labels stated in the Basecamp report or instructions. Supply any team-specific label rules in the automation prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Basecamp to GitHub. A trigger fires from one place; an action lands in another.
Basecamp 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.
Basecamp 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.