Review Kaleido deployment regions from a GitHub issue
When a deployment-planning issue asks where a network could run, Notis can retrieve Kaleido’s available regions and endpoints for the team to review.
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
Get Regions
Tool to retrieve the list of deployment zones and endpoints. Use after authenticating to list available regions.
Why this helps
Deployment planning can pause while someone switches to Kaleido just to find which regions are available.
- Bring available deployment-zone options into the planning handoff.
- Keep the lookup read-only so the team can decide where to deploy.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Kaleido to Notis once in the portal.
- 2Create the automation in the portal or ask Notis for it in plain language.
- 3Tell Notis to retrieve Kaleido deployment regions only when a new planning issue explicitly asks for available zones or endpoints.
- 4Select GitHub New Issue Created, optionally filtered to your deployment-planning label, and choose where run reports should go.
- 5Test with one new planning issue requesting a region lookup.
Questions about this workflow
Does this launch a blockchain network?
No. The selected Kaleido action retrieves region and endpoint information only; it does not deploy a network.
Does it use details from the issue?
It uses the issue’s title and body to determine whether a region lookup was requested; the GitHub New Issue Created payload includes those fields.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Kaleido. A trigger fires from one place; an action lands in another.
GitHub triggers
Kaleido actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Organization Identity Proof
Tool to add an identity proof to an organization. Use when registering an x.509 certificate chain for an org immediately after creation.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create API Key
Tool to create a new API key for an organization. Use after confirming the org_id.
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
Tool to delete a specific API key. Use when you need to remove an API key by its identifier after confirming it's no longer in use.
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.
Get API Keys
Tool to retrieve all API keys associated with the organization. Use when you need an overview of existing API keys after authenticating.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get App2App Runtimes
Tool to retrieve App2App runtimes by listing all services and filtering where service == 'app2app'. Use after authenticating to enumerate App2App service instances.
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.
Get Application Credentials
Tool to retrieve application credentials for a specific environment. Use when you need to list DApp credentials after environment setup.
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.
Get Consortia
Tool to retrieve all consortia associated with the organization. Use after authenticating to view existing consortia.
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.
Get Event Streams
Tool to list all event streams configured in the environment. Use when you need to retrieve current event stream setups.
Connect any two apps with Notis in the middle.
GitHub and Kaleido, 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 Kaleido.