Keep contributor history aligned with pull request progress
A pull request can move through several meaningful moments. Preserve the story without asking yourself to remember each one.
Trigger
Pull Request Event
Triggered when a pull request is opened, closed, or synchronized.
Action
Create Lead
Tool to add a new lead. use when you have lead details and need to save them to tomba.
Why this helps
Follow-up timing becomes guesswork when pull request milestones are not recorded with the contact.
- Improve timing for personal follow-up
- Preserve contribution history
- Reduce mental bookkeeping
Setup
Build it in a few focused steps.
- 1Connect GitHub and Tomba to Notis once in the portal.
- 2Create the automation in the portal or ask Notis to update the relevant Tomba lead whenever a pull request lifecycle event occurs, recording the event and link.
- 3Select the GitHub Pull Request Event trigger.
- 4Choose a channel for reports and test with one pull request event.
Questions about this workflow
Which lifecycle changes are included?
The trigger covers pull requests being opened, closed, or synchronized.
Can merged pull requests be recognized?
Yes, the event payload includes the pull request state and merge information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Tomba. A trigger fires from one place; an action lands in another.
GitHub triggers
Tomba actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List lead attributes
Tool to list all lead attributes. use when you need to discover available attributes before enrichment.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Domain Status
Tool to check if a domain is webmail or disposable. use when validating email deliverability constraints.
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.
Delete API Key by ID
Tool to delete an api key by id. use when you need to permanently revoke an api key before its expiration.
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 API Keys
Tool to list all api keys. use when you want to retrieve information about your existing tomba api keys.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Lead
Tool to add a new lead. use when you have lead details and need to save them to tomba.
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 Leads
Tool to list all leads. use when you need to retrieve and paginate your leads list.
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.
Delete Leads List by ID
Tool to delete a leads list by id. use when you need to permanently remove a list after confirming its 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.
List Lead Lists
Tool to list all lead lists. use when you need to retrieve and paginate your lead lists.
Connect any two apps with Notis in the middle.
GitHub and Tomba, 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 Tomba.