Give Census data quality concerns a clear owner
Send a data quality concern into Notis and put the related GitHub follow-up in the right person's queue.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Data quality concerns can sit in GitHub without an owner who knows which Census result needs review.
- Attach responsibility to the issue as soon as a concern is raised.
- Keep the affected Census geography and measure in the review context.
- Reduce handoffs between data review and engineering tracking.
Setup
Build it in a few focused steps.
- 1Connect Census bureau and GitHub once in the Notis portal.
- 2Create an automation in Automations, then choose New Automation.
- 3Tell Notis to use the incoming Census concern and your ownership rule to assign the specified existing GitHub issue.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real concern and an existing issue reference.
Questions about this workflow
What must the webhook identify?
It should identify the Census measure and geography, explain the concern, and include the GitHub repository and issue number.
Can the automation decide who owns the concern?
Yes, if you provide an ownership rule or named reviewer in the instruction. Census bureau does not include your team's assignment rules.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Census bureau to GitHub. A trigger fires from one place; an action lands in another.
Census bureau 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.
Census bureau 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.