Process receipts documented in project READMEs
Project documentation can double as a lightweight expense intake channel.
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
Process Receipt via URL
Tool to process a receipt or invoice from its public image url. use when you have a hosted image or pdf link and need basic data extraction. call after ensuring the url is accessible and points to a supported image or pdf.
Why this helps
Founder-led projects often document purchases in READMEs, but those links rarely make it into a finance workflow.
- Connects project documentation with expense processing.
- Captures purchase details without requiring a separate form.
- Helps preserve why a purchase was made.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Taggun to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to process public receipt and invoice URLs added to the monitored README with Taggun.
- 3Pick the GitHub Repository README Changed trigger and choose a channel for run reports.
- 4Test by adding one supported receipt URL to the README.
Questions about this workflow
Is this only for public repositories?
The document URL itself must be accessible to Taggun, regardless of where the README is hosted.
What is the best use case?
It works well for project-specific tools, hardware, services, or research purchases documented alongside the project.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Taggun. A trigger fires from one place; an action lands in another.
GitHub triggers
Taggun actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Export Known Merchants
Tool to export the current list of known merchants. use when you need a full merchant registry (e.g. sync or audit).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Generate Merchants CSV
Tool to generate a csv file of mock merchants for import known merchants testing. use when sample merchant csv is needed before bulk import. returns a path to a temporary csv file ready for upload.
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.
Process Receipt via URL
Tool to process a receipt or invoice from its public image url. use when you have a hosted image or pdf link and need basic data extraction. call after ensuring the url is accessible and points to a supported image or pdf.
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.
URL Validation
Tool to validate a receipt image by url against campaign settings. use after obtaining the receipt url to confirm validity.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
URL Verbose
Tool to process a receipt or invoice from a url for detailed data extraction. use when you have a publicly accessible receipt or invoice url and require comprehensive output including line items, merchant details, and confidence metrics. call after verifying the url is reachable.
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 Taggun, 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 Taggun.