Give every issue a clear starting point
New requests should arrive with enough context to make a decision.
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
Create Note
Tool to create a note from markdown or HTML content with optional template. Use when you need to create a new note in Slite with specified content and title.
Why this helps
Issue queues grow faster than a founder can read, interpret, and organize them.
- Reduces first-pass triage effort
- Makes ambiguous requests easier to clarify
- Creates a searchable intake history
Setup
Build it in a few focused steps.
- 1Connect GitHub and Slite to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Use the instruction: “When a new GitHub issue is created, create a Slite intake brief with the request, user impact, urgency clues, open questions, and recommended next action.”
- 4Select the new-issue trigger, choose a run-report channel, and test with one real issue.
Questions about this workflow
Can it handle vague issues?
Yes. Ask Notis to identify missing information and list the smallest useful clarification.
Can the note link back to GitHub?
Yes. Include the issue URL in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Slite. A trigger fires from one place; an action lands in another.
GitHub triggers
Slite 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.
Ask Question
Tool to ask a question to your Slite notes in natural language. Use when you need to query or search information across your notes. Supports optional filters to narrow results by parent note or specific assistant.
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.
Create Note
Tool to create a note from markdown or HTML content with optional template. Use when you need to create a new note in Slite with specified content and title.
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 Note By ID
Tool to permanently delete a note and all its children by ID. Use when you need to remove a note irreversibly. This operation cannot be undone.
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.
Flag Note as Outdated
Tool to set Outdated status on a note with a reason. Use when you need to flag a note as containing outdated information.
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 authenticated user
Retrieves information about the currently authenticated user. Use this to get user details including email, display name, and organization information.
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 Note By ID
Tool to retrieve a complete note by its ID including content in Markdown or HTML format. Use when you need to fetch the full details and content of a specific note.
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 Note Children
Tool to retrieve note children by parent note ID. Use when you need to fetch child notes beneath a specified parent note. Supports pagination for notes with more than 50 children using cursor-based navigation.
Commit Event
Triggered when a new commit is pushed to a repository.
List Notes
Tool to list notes from Slite with optional filtering by owner. Use when you need to retrieve notes, optionally filtered by a specific user. Supports cursor-based pagination via the cursor parameter.
Connect any two apps with Notis in the middle.
Not just GitHub and Slite. 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 Slite.