Track GitHub README changes in Segment
Keep documentation work visible even when it happens in small, easy-to-overlook edits.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
Segment Track Event
Tool to record a custom user event via Segment HTTP Tracking API. Use when sending events to Segment with valid identity.
Why this helps
Important docs updates can vanish from planning conversations because they look like minor commits.
- Makes documentation work visible
- Helps connect docs changes to launches
Setup
Build it in a few focused steps.
- 1Connect GitHub and Segment in the Notis portal.
- 2Create an automation with New Automation.
- 3Tell Notis to record README changes as documentation events in Segment.
- 4Choose the README changed trigger and a reporting channel.
- 5Edit a test README to verify it.
Questions about this workflow
Can it watch a README in a subfolder?
Yes. Choose the directory you want the GitHub trigger to monitor.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Segment. A trigger fires from one place; an action lands in another.
GitHub triggers
Segment actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Labels to Source
Tool to add existing labels to a Source. Use when you have the source ID and want to tag it with metadata labels.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Segment Alias
Tool to alias a previous user ID to a new user ID. Use when merging anonymous and known identities.
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.
Batch Segment Analytics Events
Tool to send multiple analytics calls in a single batch request. Use when you want to reduce HTTP overhead by batching Identify/Track/Page/Screen/Group calls into one request.
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 Source
Tool to delete a Segment Source. Use when you need to permanently remove a Source by its ID after confirmation.
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 Daily Per Source API Calls Usage
Tool to fetch daily API call counts per source for a given period. Use when you need daily breakdown of API usage by source after determining the reporting period.
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 Destination
Tool to retrieve a Destination by ID. Use when you need to fetch the full configuration of a Segment Destination instance by its unique identifier. Falls back US→EU public API and legacy app endpoint; returns minimal envelope on legacy HTML or parse errors.
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.
Segment Group
Tool to associate an identified user with a group via Segment HTTP Tracking API. Use when grouping users with traits.
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.
Segment Identify
Tool to identify a user and set/update traits via Segment HTTP Tracking API.
Connect any two apps with Notis in the middle.
GitHub and Segment, 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 Segment.