Make issue movement visible without checking GitHub
A quiet lifecycle log keeps decisions and follow-up from disappearing.
Trigger
New Issue Event
Triggers when a new issue event occurs in a GitHub repository. Covers all issue timeline events such as issues being closed, reopened, assigned, unassigned, labeled, unlabeled, milestoned, demilestoned, renamed, locked, or unlocked. Events can optionally be filtered by type. The payload includes the event type, timestamp, the actor who triggered the event, the affected issue details, and any associated commit references.
Action
Update Note
Tool to update a note's content with markdown and/or title. Use when you need to modify an existing note's content or metadata.
Why this helps
Important issue transitions happen asynchronously, making it hard to know what changed while you were elsewhere.
- Reduces status-checking
- Preserves why work moved
- Makes retrospectives easier
Setup
Build it in a few focused steps.
- 1Connect GitHub and Slite to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to set it up conversationally.
- 3Use the instruction: “When an important GitHub issue event occurs, update the project lifecycle log in Slite with the event, actor, issue link, and resulting next action.”
- 4Choose the issue-event trigger with the relevant event types, select a report channel, and test with one real event.
Questions about this workflow
Which events should be logged?
Common choices include closure, reopening, reassignment, milestone changes, and priority-label changes.
Can it summarize rather than copy activity?
Yes. Ask Notis to record only events that change ownership, priority, or delivery expectations.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 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.
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.
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.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get authenticated user
Retrieves information about the currently authenticated user. Use this to get user details including email, display name, and organization information.
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.
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.
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 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.
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.
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.
GitHub and Slite, 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 Slite.