Keep GitHub issue authors in your CRM
When a new issue introduces someone worth knowing, Notis can add them to CentralstationCRM and keep the follow-up from getting lost in GitHub.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
Action
Create Person
Tool to create a new person record. use when you need to add a person to your crm before linking them to other records.
Why this helps
Potential customers and collaborators can appear in issue threads, then disappear into a busy repository queue.
- Keep potential customer conversations visible alongside other relationships.
- Reduce manual copying of author details out of GitHub.
- Make it easier to continue a conversation beyond the issue thread.
Setup
Build it in a few focused steps.
- 1Connect GitHub and CentralstationCRM once in the Notis portal.
- 2Create an automation from any channel, or open Automations, then New Automation in the portal.
- 3Tell Notis to create a CentralstationCRM person for each new GitHub issue author, using the available author details.
- 4Pick New Issue Created as the trigger and choose where run reports should go.
- 5Test with one real issue and review the created contact.
Questions about this workflow
Does this trigger include pull requests?
No. The New Issue Created event excludes pull requests and emits true issues.
What if GitHub does not provide an email address?
Notis can only use details available in the event or elsewhere in the connected apps. You can ask it to skip incomplete contacts or use only the available profile information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Centralstationcrm. A trigger fires from one place; an action lands in another.
GitHub triggers
Centralstationcrm actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Connection
Tool to verify the connection status of the centralstationcrm api key. use when validating credentials before making other api calls.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Count People
Tool to retrieve the total number of people in the account. use when you need the current total number of contacts in your centralstationcrm account. example: "how many contacts exist in my account?"
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.
Create Company
Tool to create a new company record. use when you need to add an organization to your crm before linking it to contacts or deals.
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.
Create Deal
Tool to create a new deal record. use when needing to log a sales opportunity after grouping contacts or companies.
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 Person
Tool to create a new person record. use when you need to add a person to your crm before linking them to other records.
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.
Create Person Address
Tool to create a new address for a specific person. use when you need to add or update postal details after confirming person id.
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 Person Assistant
Tool to create a new assistant (assi) entry for a specific person. use after confirming the person id when you need to manage assistant contacts.
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.
Create Person Avatar
Tool to create a new avatar for a specific person. use when you need to attach a base64-encoded image file after confirming the person's id.
Connect any two apps with Notis in the middle.
GitHub and Centralstationcrm, 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 Centralstationcrm.