Review company visits after a README update
Pair public documentation improvements with a quick look at visitor activity.
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 All Visits
Tool to retrieve all visits for a specific lead. use when you need detailed visit history for a lead, optionally filtered by date range.
Why this helps
Documentation updates are important but rarely get a follow-up routine.
- Makes docs work more visible
- Encourages focused customer research
Setup
Build it in a few focused steps.
- 1Connect GitHub and Leadfeeder once in Notis.
- 2Create a new automation in the portal.
- 3Ask Notis to review relevant company visits after README changes.
- 4Choose the README-changed trigger and a reporting channel.
- 5Edit the README once to test it.
Questions about this workflow
Can this monitor a repository directory?
The GitHub trigger can be configured for the README location you need.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Leadfeeder. A trigger fires from one place; an action lands in another.
GitHub triggers
Leadfeeder 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 Accounts
Tool to retrieve a list of accounts the user has access to. use when you need to discover all available leadfeeder accounts after authentication.
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 All Visits
Tool to retrieve all visits for a specific lead. use when you need detailed visit history for a lead, optionally filtered by date range.
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 Info by IP
Tool to retrieve company information based on an ip address. use when you need to enrich an ip and obtain its company profile. returns 404 if no match is found.
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 Custom Feeds
Tool to retrieve a list of custom feeds for a specific account. use after confirming the account id to list all its custom feed configurations.
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.
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.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Leadfeeder. 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 Leadfeeder.