Keep CommCare data issues visible in GitHub
Send a CommCare problem to Notis and keep the engineering follow-up easy to spot.
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
Data-quality concerns get mentioned in chat, then disappear before anyone investigates.
- Makes incoming data concerns visible in the engineering queue
- Creates a consistent triage signal for the team
- Reduces memory work after field operations
Setup
Build it in a few focused steps.
- 1Connect CommCare and GitHub to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to create one in plain language.
- 3Tell Notis to label the matching GitHub issue when a CommCare data concern arrives.
- 4Choose the webhook trigger and a channel for run reports.
- 5Test it with one real CommCare concern.
Questions about this workflow
Can the CommCare message include context?
Yes. Tell Notis to use the incoming context when identifying the matching GitHub issue and applying the label.
Do I need to create field mappings?
No. The automation uses one plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link CommCare to GitHub. A trigger fires from one place; an action lands in another.
CommCare triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just CommCare and GitHub. Any 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.