Connect GitHub to Tomba
When something happens in GitHub, Notis takes the next step in Tomba. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from GitHub to Tomba
Turn new repository stars into qualified leads
Capture new GitHub stargazers in Tomba so promising product interest does not disappear into a notification stream.
Save new GitHub followers as leads
Turn new GitHub followers into organized Tomba leads without manually checking profiles or keeping a separate follow-up list.
Enrich new repository collaborators
Create a Tomba lead when someone becomes a GitHub collaborator so onboarding, partnerships, and future follow-up stay connected.
Capture new pull request contributors
Save authors of new pull requests as Tomba leads when contribution activity may signal a future customer, advocate, or partner.
Remember valuable issue reporters
Create Tomba leads from new GitHub issue authors so product feedback and potential customer conversations remain connected.
Track new pull request reviewers
Save reviewers who engage with pull requests as Tomba leads when their expertise or interest could support future collaboration.
Capture high-context review commenters
Create Tomba leads from new inline pull request commenters when detailed product or technical feedback signals a valuable contact.
Record newly requested reviewers
Add newly requested GitHub reviewers to Tomba when an emerging expert, advisor, or partner enters an important workflow.
Create follow-up leads for assigned issues
Save people connected to newly assigned GitHub issues in Tomba so customer or partner follow-up does not get lost while work moves forward.
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
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.
List lead attributes
Tool to list all lead attributes. use when you need to discover available attributes before enrichment.
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.
Domain Status
Tool to check if a domain is webmail or disposable. use when validating email deliverability constraints.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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 API Keys
Tool to list all api keys. use when you want to retrieve information about your existing tomba api keys.
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.
Create Lead
Tool to add a new lead. use when you have lead details and need to save them to tomba.
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 Leads
Tool to list all leads. use when you need to retrieve and paginate your leads list.
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.
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.
Commit Event
Triggered when a new commit is pushed to a repository.
List Lead Lists
Tool to list all lead lists. use when you need to retrieve and paginate your lead lists.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it trough Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect GitHub and Tomba
Connect any two apps with Notis in the middle.
Not just GitHub and Tomba. 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 Tomba.