Check crypto events when a deployment status changes
A deployment changed. Notis checks the market calendar so the next decision has context.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
List Cryptocurrency Events
Tool to retrieve list of cryptocurrency events. Use when you need to fetch upcoming or past crypto events filtered by date range, coins, categories, or other criteria. Note: Cannot retrieve events before 25/11/2017. The can_occur_before field is important as some events may happen before their stated date.
Why this helps
Deployment work can finish successfully while the founder still lacks a clear view of nearby market-moving dates.
- Links production progress with market timing
- Reduces manual calendar checks after deploys
- Creates a consistent post-deployment handoff
Setup
Build it in a few focused steps.
- 1Connect GitHub and CoinMarketCal to Notis once through the portal.
- 2Create a new automation in the portal or ask Notis in plain language.
- 3Use this instruction: When a GitHub deployment status is created, retrieve relevant CoinMarketCal events around the deployment and summarize anything requiring follow-up.
- 4Choose the GitHub deployment status trigger and select where Notis should report runs.
- 5Test it with one deployment status.
Questions about this workflow
Which deployment states can be useful?
You can use the trigger for statuses such as success, failure, pending, or in progress, depending on your setup.
Will Notis change the deployment?
No. It only retrieves and summarizes CoinMarketCal information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Coinmarketcal. A trigger fires from one place; an action lands in another.
GitHub triggers
Coinmarketcal 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 Coins
Tool to retrieve list of all available coins/cryptocurrencies in CoinMarketCal database. Use when you need to fetch coin information including IDs, names, symbols, and event counts.
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.
List Event Categories
Tool to list all event categories. Use when you need to fetch available event categories.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
List Cryptocurrency Events
Tool to retrieve list of cryptocurrency events. Use when you need to fetch upcoming or past crypto events filtered by date range, coins, categories, or other criteria. Note: Cannot retrieve events before 25/11/2017. The can_occur_before field is important as some events may happen before their stated date.
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.
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.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Coinmarketcal. Any 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 Coinmarketcal.