Label parsed support requests without manual sorting
Give every request a useful category before it reaches your next planning session.
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
Customer requests pile up without consistent labels, making prioritization mentally expensive.
- Creates a consistent visual filing system
- Speeds up feedback review
- Reduces decisions during planning
Setup
Build it in a few focused steps.
- 1Connect Docparser and GitHub to Notis once through the portal.
- 2Create a new automation in the portal or tell Notis what you want in plain language.
- 3Use one instruction: apply appropriate GitHub labels to each issue represented by a newly parsed support request.
- 4Select the incoming webhook trigger, choose the run-report channel, and test with one real request.
Questions about this workflow
Does this require predefined field mappings?
No. Describe the labeling rules in the automation prompt and Notis interprets the parsed content.
Can it handle different request categories?
Yes. Include categories such as bug, feature request, billing, or urgent customer issue in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Docparser to GitHub. A trigger fires from one place; an action lands in another.
Docparser 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 Docparser 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.