Prioritize issues with customer context
New issues arrive with a quick view of the companies that may be affected or waiting for answers.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
Action
List Companies
Tool to list companies in the workspace. use when you need a paginated overview of companies, optionally filtered.
Why this helps
Issue queues hide customer impact, making prioritization dependent on memory and repeated searching.
- Makes customer impact easier to assess
- Reduces repeated CRM searches
- Supports faster prioritization
Setup
Build it in a few focused steps.
- 1Connect GitHub and Folk to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: When a new GitHub issue is created, list related Folk companies and provide a short prioritization brief based on the issue context.
- 4Pick the new issue trigger, choose a channel for run reports, and test with one real issue.
Questions about this workflow
Can this cover internal issues too?
Yes. Ask Notis to distinguish internal work from customer-related issues in the plain-language instruction.
Does it modify the issue?
No. It provides a Folk-based context brief for triage.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Folk. A trigger fires from one place; an action lands in another.
GitHub triggers
Folk actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Create Company
Tool to create a new company in the workspace. use after gathering all required company details and ensuring the name is unique.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Delete Company
Tool to delete a company from the workspace (irreversible). use after confirming this company should be removed.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Person
Tool to delete an existing person in the workspace (irreversible). use after confirming this person should be permanently removed.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
List Companies
Tool to list companies in the workspace. use when you need a paginated overview of companies, optionally filtered.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Get Company
Tool to retrieve an existing company by its id. use after authentication has been verified.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Get Current Workspace User
Tool to get details of the current authenticated workspace user. use after authentication to retrieve the user's profile information.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Get Person
Tool to retrieve an existing person by their id. use when you need full profile details of a person by their unique identifier.
Commit Event
Triggered when a new commit is pushed to a repository.
List Group Custom Fields
Tool to list custom fields for a specific group and entity type. use after selecting a group and entity type to inspect available custom fields.
Connect any two apps with Notis in the middle.
Not just GitHub and Folk. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Folk.