Turn GitHub pull requests into Woodpecker prospects
Keep promising technical relationships moving while the context is fresh.
Trigger
New Pull Request Created
Triggers when a new pull request is created in GitHub, matching the optional configured filters. Emits an event for each newly created pull request. Supports filtering by repository, owner/organisation, author, assignee, label, state, base branch, head branch, and draft status.
Action
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.
Why this helps
Interesting contributors and potential partners appear in GitHub, then disappear from your working memory before you follow up.
- Captures relevant contributors while the interaction is recent.
- Reduces copy and paste between engineering and outreach.
- Gives every promising relationship a consistent next step.
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 in plain language to add relevant new pull request authors to a Woodpecker campaign.
- 3Select the GitHub new pull request trigger and choose a channel for run reports.
- 4Test it with one real pull request and confirm the prospect appears in the intended campaign.
Questions about this workflow
Can every pull request become a prospect?
Tell Notis to add only pull requests that match your audience, project, or collaboration criteria.
Does Notis copy the pull request context?
Yes. Instruct Notis to include useful public context in the prospect record or campaign note when supported.
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
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.
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.
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.
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 Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Prospects in Campaigns (v1)
Tool to retrieve prospects enrolled in specified campaigns. Use when you need to list prospects for given campaign IDs.
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.
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).
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.
List Campaigns V1
Tool to list campaigns. Use when you need to fetch campaigns with optional status or ID filters.
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.
Pause Campaign
Tool to pause a campaign. Use when you need to temporarily stop sending prospects until resumed.
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.
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.
Commit Event
Triggered when a new commit is pushed to a repository.
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.
Not just GitHub and Woodpecker co. 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 Woodpecker co.