Keep a timely PR conversation from getting lost
A new pull request can mark a useful moment to connect. Ask Autobound for a personalized draft when the context is relevant and details are confirmed.
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
Generate Personalized Content
Tool to generate hyper-personalized sales content. Use after confirming contact and user details.
Why this helps
A timely opening around a new pull request can be missed while the team moves quickly through reviews.
- Capture a timely follow-up opportunity from PR activity.
- Prepare content for human review.
- Avoid drafting from unverified contact details.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Autobound once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3Describe the outcome: assess whether the new pull request gives a relevant reason to connect, confirm contact and user details, then generate personalized content for review.
- 4Pick the GitHub New Pull Request Created trigger.
- 5Choose where run reports go, then test with one real pull request.
Questions about this workflow
Does every pull request justify outreach?
No. Instruct Notis to generate content only when the PR context offers a relevant reason to connect.
Does the workflow send the draft?
No. Autobound generates personalized content; the available action does not send it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Autobound. A trigger fires from one place; an action lands in another.
GitHub triggers
Autobound actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Generate Insights
Tool to generate ranked prospect or company insights. Use after resolving identifiers to retrieve the most relevant insights.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Generate Personalized Content
Tool to generate hyper-personalized sales content. Use after confirming contact and user details.
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.
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.
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 Autobound, 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 Autobound.