Skip to content
Notis

Scan Leadfeeder feeds on pull request events

Keep a compact view of demand signals alongside meaningful product changes.

Trigger

Pull Request Event

Triggered when a pull request is opened, closed, or synchronized.

Action

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.

Why this helps

Product progress and lead research live in separate rhythms and get disconnected.

  • Creates one dependable review point
  • Reduces context switching

Setup

Build it in a few focused steps.

  • 1Connect GitHub and Leadfeeder in Notis.
  • 2Start a new automation from the portal.
  • 3Describe a custom-feed scan for important pull-request events.
  • 4Select the pull-request event trigger and reporting channel.
  • 5Open or update a pull request to test it.

Questions about this workflow

Can I focus on opened pull requests?

Yes. Say which PR events matter in the plain-language instruction.

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

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

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.

TriggerPolling

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.

ActionInstant

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.

TriggerPolling

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.

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

Connect any two apps with Notis in the middle.

GitHub and Leadfeeder, 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 Leadfeeder.