Keep documentation changes connected to relationships
A README update becomes a small, useful CRM note when it affects onboarding, positioning, or shared expectations.
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
Update Company
Tool to update an existing company in the workspace. use after confirming the company id; only provided fields are updated and list fields replace existing values.
Why this helps
Documentation changes can alter how customers or partners use the product without reaching the relationship record.
- Highlights changes that affect onboarding
- Keeps shared documentation history visible
- Reduces repetitive explanation later
Setup
Build it in a few focused steps.
- 1Connect GitHub and Folk to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it in plain language.
- 3Use this instruction: When the monitored GitHub README changes, update the relevant Folk company with a concise summary and explain whether customer or partner follow-up may be useful.
- 4Select the README changed trigger, choose a channel for run reports, and test with one real documentation change.
Questions about this workflow
Can this monitor one repository directory?
Yes. The trigger monitors a specific README path and branch, tag, or commit scope.
Will it rewrite the README?
No. It records context in Folk only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Folk. A trigger fires from one place; an action lands in another.
GitHub triggers
Folk actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Company
Tool to create a new company in the workspace. use after gathering all required company details and ensuring the name is unique.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Company
Tool to delete a company from the workspace (irreversible). use after confirming this company should be removed.
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 Person
Tool to delete an existing person in the workspace (irreversible). use after confirming this person should be permanently removed.
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.
List Companies
Tool to list companies in the workspace. use when you need a paginated overview of companies, optionally filtered.
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 Company
Tool to retrieve an existing company by its id. use after authentication has been verified.
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 Current Workspace User
Tool to get details of the current authenticated workspace user. use after authentication to retrieve the user's profile information.
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 Person
Tool to retrieve an existing person by their id. use when you need full profile details of a person by their unique identifier.
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 Group Custom Fields
Tool to list custom fields for a specific group and entity type. use after selecting a group and entity type to inspect available custom fields.
Connect any two apps with Notis in the middle.
GitHub and Folk, 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 Folk.