Connect GitHub to NetHunt CRM
When something happens in GitHub, Notis takes the next step in NetHunt CRM. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Fires when a new GitHub Actions workflow artifact is created in a repository.
Do this · Action
Permanently delete a CRM record.
Ways Notis can move work from GitHub to NetHunt CRM
Pull request client context
Find the related CRM record when a customer-facing pull request opens.
New issue customer lookup
Search NetHunt for the customer behind each new GitHub issue.
Review feedback deal context
Find the associated deal when a pull request review arrives.
Secret alert CRM audit
Check recent NetHunt record changes when GitHub detects an exposed secret.
Code alert account search
Search for affected accounts when a code scanning alert is created.
Failed deployment deal lookup
Find active customer records when a deployment status changes.
Merged PR account updates
Retrieve recently updated CRM records when a pull request changes state.
Issue comment CRM conversation check
Retrieve fresh CRM comments when a GitHub issue receives a new comment.
Assigned issue customer priority
Find the CRM record behind issues assigned to you.
Supported Triggers and Actions
Notis builds workflows that link GitHub to NetHunt CRM. A trigger fires from one place; an action lands in another.
GitHub triggers
NetHunt CRM actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Record
Permanently delete a CRM record.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Find Records
Finds records in a CRM folder by record ID or text query.
New Workflow Artifact Created
Fires when a new GitHub Actions workflow artifact is created in a repository.
Get New Call Logs
Retrieve recently created call logs from a folder.
Branch Changed
Fires when a branch’s commits or protection status or settings change.
Get New Comments
Retrieve recently created comments on records in a folder.
New Branch Created
Fires when a new branch is created in a GitHub repository.
Get New Google Drive Files
Retrieve recently created Drive files linked to CRM records.
Check Run Status / Conclusion Changed
Fires when a GitHub check run’s status or conclusion changes.
Get New Records
Retrieve records recently created in a folder.
Check Suite Status / Conclusion Changed
Fires when a GitHub check suite changes status or conclusion for a reference.
Get Record Changes
Retrieve recent record changes and their field-level differences.
New Code Scanning Alert Created
Fires when a new code scanning alert is created in a repository.
Get Updated Records
Retrieve records updated since a specified time.
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 schedule (recurring or one-time), and a change in one of your Notis databases.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ 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.
Scheduled triggers
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Database triggers
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
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 through 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 NetHunt CRM
Connect any two apps with Notis in the middle.
GitHub and NetHunt CRM, or any other combination from 1,500+ 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 NetHunt CRM.