Retrieve Apilio strings after repository content changes
Keep a configuration edit from becoming a scattered search for the related operational context.
Trigger
Repository Content Changed
Triggers when the content of a file or directory in a GitHub repository changes. Monitors a specified path within a repository on a given branch or tag. For a single file, fires ``content_changed`` when the file is modified. For a directory, fires ``content_changed``, ``content_added``, or ``content_removed`` for modified, new, or deleted entries respectively. content.
Action
Get String Variables
Tool to fetch all string variables. use after authenticating the apilio api.
Why this helps
Changes to files or directories can interrupt your flow with uncertainty about the settings and labels around them.
- Pairs file changes with readable context
- Creates a reliable configuration-review cue
Setup
Build it in a few focused steps.
- 1Connect GitHub and Apilio to Notis once.
- 2Create an automation for monitored content changes.
- 3Write a plain-language instruction to retrieve Apilio string variables when that content changes.
- 4Select the GitHub repository-content trigger and a reporting channel.
- 5Test by making a real change in the monitored path.
Questions about this workflow
Can it watch a directory?
Yes. The GitHub trigger can monitor a configured file or directory path.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Apilio. A trigger fires from one place; an action lands in another.
GitHub triggers
Apilio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Boolean Variables
Tool to fetch all boolean variables. use when you need the full list of boolean variables and their current states.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Conditions
Tool to fetch all evaluatable conditions. use when you need to list available conditions.
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.
Get Logicblocks
Tool to fetch all logicblocks of a user. use after authenticating with apilio api when you need to list available logicblocks.
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 Numeric Variables
Tool to fetch all numeric variables. use after authenticating the apilio api.
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 String Variables
Tool to fetch all string variables. use after authenticating the apilio api.
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 Apilio, 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 Apilio.