Turn clearer documentation into community momentum
When the product story improves, invite the right people to see it.
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
Run Campaign
Tool to run a campaign and set its status to RUNNING. Use when you want to activate a configured campaign after final review.
Why this helps
Documentation updates often improve discoverability, but the founder may forget to tell interested users or partners about the change.
- Connects documentation work with audience development.
- Creates a repeatable promotion moment.
- Reduces the effort needed to share meaningful product improvements.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Woodpecker co to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to run a named community campaign after a qualifying README change.
- 3Select the GitHub README changed trigger and choose the channel for run reports.
- 4Test with one documentation update and verify the campaign is ready for the intended audience.
Questions about this workflow
Can only major README changes launch the campaign?
Yes. Describe the directory, branch, or type of update that should qualify.
Can the workflow only prepare a report?
Yes. Use the list campaigns action if you want a review step before running outreach.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Woodpecker co. A trigger fires from one place; an action lands in another.
GitHub triggers
Woodpecker co actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add prospects to a campaign (v1)
Tool to add one or multiple prospects to a campaign. Use when you need to import prospects into a campaign's contact list.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Campaign Step
Tool to delete a non-initial campaign step that hasn't processed any prospects. Use when the campaign is in DRAFT or EDITED status and the step is unused.
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 Prospects in Campaigns (v1)
Tool to retrieve prospects enrolled in specified campaigns. Use when you need to list prospects for given campaign IDs.
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 Available Webhook Events
Tool to list all webhook event names supported by Woodpecker. Use before subscribing to ensure valid 'event' values (static catalog from docs).
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
List Campaigns V1
Tool to list campaigns. Use when you need to fetch campaigns with optional status or ID filters.
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.
Pause Campaign
Tool to pause a campaign. Use when you need to temporarily stop sending prospects until resumed.
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.
Run Campaign
Tool to run a campaign and set its status to RUNNING. Use when you want to activate a configured campaign after final review.
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.
Stop Campaign
Tool to stop a campaign. Use when you need to halt prospect contacts by setting campaign status to STOPPED.
Connect any two apps with Notis in the middle.
GitHub and Woodpecker co, 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 Woodpecker co.