Enrich prospects after a GitHub README update
A clearer README can open a fresh adoption conversation. Notis prepares the research step without asking you to switch contexts.
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
Start Bulk Enrichment
Tool to start a bulk enrichment job. Use when you have up to 100 contacts prepared and need batch enrichment. Use after confirming contact data.
Why this helps
Documentation improvements can create outreach opportunities that get forgotten once the writing work is done.
- Turns documentation work into a growth cue
- Keeps outreach ideas actionable
- Avoids manual prospect research after writing
Setup
Build it in a few focused steps.
- 1Connect GitHub and Fullenrich in Notis.
- 2Go to Automations and choose New Automation.
- 3Describe which prospects to enrich after relevant README updates.
- 4Select GitHub Repository README Changed and a report channel.
- 5Test after updating the README in your selected repository.
Questions about this workflow
Can this watch a specific README?
Yes. Choose the repository directory and reference when setting up the GitHub trigger.
Does it rewrite the README?
No. It uses the README change only as the workflow trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Fullenrich. A trigger fires from one place; an action lands in another.
GitHub triggers
Fullenrich actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Contact Data List
Tool to create a list of contact data entries. Use when preparing the 'datas' payload for bulk enrichment; validates each contact's composition and returns a JSON-ready list.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Bulk Enrichment Result
Tool to retrieve results of a bulk enrichment by enrichment ID. Use after confirming the job has been submitted to fetch status and enriched data.
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 current credit balance
Tool to retrieve current workspace credit balance. Use after authenticating your API key.
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.
Start Bulk Enrichment
Tool to start a bulk enrichment job. Use when you have up to 100 contacts prepared and need batch enrichment. Use after confirming contact data.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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 Fullenrich, 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 Fullenrich.