Refresh NocoDB schema context when a README changes
Make documentation updates easier to validate against the system they describe.
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
Get Table Schema
Tool to retrieve complete schema information for a specific table. Use when you need to understand table structure, field definitions, or available views.
Why this helps
Data documentation can drift because checking the live table feels like one more task.
- Supports accurate docs
- Creates a quick verification cue
- Reduces drift
Setup
Build it in a few focused steps.
- 1Connect GitHub and NocoDB in the Notis portal.
- 2Create an automation from the Automations page.
- 3Write an instruction to retrieve the relevant NocoDB schema after README changes.
- 4Choose the README changed trigger and a reporting channel.
- 5Update a test README section to verify the result.
Questions about this workflow
Can this monitor a README in a subdirectory?
Choose the trigger configuration for the directory containing that README.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to NocoDB. A trigger fires from one place; an action lands in another.
GitHub triggers
NocoDB 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.
Get User Info
Tool to get authenticated user information including email, name, roles, and profile details. Use when you need to verify user authentication or retrieve the current user's profile information.
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.
Forgot Password
Tool to initiate password reset process by sending a reset email to the user. Use when a user has forgotten their password and needs to receive a password reset link via email.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Sign Out User
Tool to sign out the authenticated user and clear their refresh token from the database and cookie. Use when you need to invalidate a user's authentication session and log them out of the NocoDB application.
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 Sort Metadata
Tool to retrieve sort configuration by ID from NocoDB. Use when you need to get details about how data is ordered in a specific view.
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.
Update View Column
Tool to update a column configuration in a view. Use when you need to change column visibility, order, or width in a specific view.
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.
Delete View
Tool to delete a view from a NocoDB table. Use when you need to permanently remove a view. This action cannot be undone.
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.
Delete Table View Row
Tool to delete a specific row from a table view in NocoDB. Use when you need to remove a single record from a view.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Integration Info
Tool to retrieve metadata for a specific NocoDB integration by type and subtype. Use when you need to get integration configuration schema, display information, or available capabilities for an integration.
Connect any two apps with Notis in the middle.
Not just GitHub and NocoDB. 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 NocoDB.