Keep Shopify incidents visible in GitHub
When the storefront has a problem, make the next action obvious.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Store incidents get buried among unrelated engineering work, making it easy to miss the issue that needs attention first.
- Makes store-impacting issues easy to scan
- Reduces repeated manual triage
- Creates a consistent signal for urgent work
Setup
Build it in a few focused steps.
- 1Connect Shopify and GitHub to Notis once through the portal.
- 2Create an automation in the portal or ask Notis in plain language.
- 3Use this instruction: When Shopify sends an incident webhook, add the appropriate store-incident and severity labels to the matching GitHub issue.
- 4Choose an incoming webhook trigger and a channel for run reports, then test with one real incident.
Questions about this workflow
What starts this automation?
A Shopify incident notification sent to a Notis incoming webhook.
Does it create the issue too?
This workflow labels a matching GitHub issue. Your webhook or existing process should identify the issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Shopify to GitHub. A trigger fires from one place; an action lands in another.
Shopify triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Not just Shopify and GitHub. 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 GitHub.