Document new automation workflows from day one
When a GitHub Actions workflow is added, Notis creates a Docupilot folder for its runbook material.
Trigger
New GitHub Actions Workflow Added
Triggers when a new GitHub Actions workflow is added to a repository. Monitors a repository's GitHub Actions workflows and fires an event for each newly added workflow. The payload includes the workflow's name, file path, state, creation and update timestamps, and URLs for the API, web interface, and status badge.
Action
Create Docupilot Folder
Tool to create a new folder. use when organizing documents into custom workspace folders after confirming workspace context.
Why this helps
New automation can become opaque when its operational notes are never collected.
- Starts a workflow runbook space
- Makes ownership context easier to find
- Prevents undocumented automation drift
Setup
Build it in a few focused steps.
- 1Connect GitHub and Docupilot to Notis once.
- 2Open New Automation in the portal.
- 3Describe creating a Docupilot documentation folder when a GitHub Actions workflow is added.
- 4Choose New GitHub Actions Workflow Added and a reports channel.
- 5Add or test a workflow and confirm the result.
Questions about this workflow
Can the folder hold a runbook later?
Yes. This automation creates the organized home; add your preferred documentation outcome in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Docupilot. A trigger fires from one place; an action lands in another.
GitHub triggers
Docupilot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Docupilot Folder
Tool to create a new folder. use when organizing documents into custom workspace folders after confirming workspace context.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Docupilot Folder
Tool to create a new folder. use when organizing documents into custom workspace folders after confirming workspace context.
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.
List all folders
Tool to list all folders. use after authentication to fetch available workspace folders.
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.
Get Authenticated User
Tool to retrieve information about the authenticated user. use after authentication to confirm identity and fetch user account details.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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.
Connect any two apps with Notis in the middle.
GitHub and Docupilot, 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 Docupilot.