Retrieve Storeganise admin details from an assigned issue
For an assigned access-support issue that identifies a specific Storeganise admin, Notis can retrieve that account’s details for a focused review.
Trigger
New Issue Assigned to Me
Triggers when a new issue is assigned to the authenticated user. Fires an event for each GitHub issue that is newly assigned to the authenticated user. Pull requests are automatically excluded -- only true issues are emitted. Issues can optionally be filtered by labels and state. The payload includes the issue number, title, body, state, labels, assignees, creator, repository details, and timestamps.
Action
Get Admin User By ID or Email
Tool to retrieve a specific admin user by id or email. use when you need detailed information of a single admin user.
Why this helps
An access-support task can require a separate lookup before you can understand which admin account it concerns.
- Retrieve details for the one admin account named in the assigned request.
- Keep sensitive account information scoped to a private run-report channel.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Storeganise to Notis once in the portal.
- 2Create the automation in the portal or ask Notis for it in plain language.
- 3Tell Notis to retrieve one admin’s details only when an assigned access-support issue explicitly provides that admin’s ID or email.
- 4Select GitHub New Issue Assigned to Me, optionally filtered to your access-support label, and choose a private channel for run reports.
- 5Test with one assigned issue and an authorized admin identifier.
Questions about this workflow
Will it retrieve all Storeganise administrators?
No. The selected action retrieves one admin by ID or email. This workflow excludes the bulk admin lookup action and requires a specific identifier.
Will the admin details be posted into GitHub?
No. The instruction routes results to the private run-report channel and does not edit the issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Storeganise. A trigger fires from one place; an action lands in another.
GitHub triggers
Storeganise actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Admin Site by ID or Code
Tool to retrieve a specific site by id or code. use when you have the site identifier and need full site details, optionally including related resources like units.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Admin User By ID or Email
Tool to retrieve a specific admin user by id or email. use when you need detailed information of a single admin user.
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.
Get Admin Users By IDs
Tool to fetch multiple admin users by their ids. use when you need to retrieve details for a specific set of admin accounts in bulk after verifying their ids.
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 Storeganise, 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 Storeganise.