Turn actionable GitHub failures into Agiled tickets
A failed run gets a clear support owner instead of becoming a forgotten notification.
Trigger
GitHub Workflow Run State Changed
Triggers when a GitHub Actions workflow run's status or conclusion changes. Monitors a single workflow run and fires an event whenever it transitions between states (e.g., queued to in_progress, or in_progress to completed) or when its conclusion is set (e.g., success, failure, cancelled).
Action
Create Ticket
Tool to create a new support ticket in agiled. use after gathering all required ticket details (subject, message, priority, user id).
Why this helps
Build failures are easy to notice and hard to follow through on when they stay in GitHub alone.
- Centralize actionable failures
- Keep run evidence attached
- Avoid duplicate manual reporting
Setup
Build it in a few focused steps.
- 1Connect GitHub and Agiled once.
- 2Describe the authorized ticket requester, priority, and conditions in one plain-language prompt.
- 3Select Workflow Run State Changed, choose a report channel, and test with one authorized failure.
Questions about this workflow
Does every status change create a ticket?
Only the conditions in your instruction should create one; the run ID, conclusion, and URL must be present in the actual event data.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Agiled. A trigger fires from one place; an action lands in another.
GitHub triggers
Agiled actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Expense
Tool to create a new expense in agiled. use after gathering expense details and authenticating with your api key.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Project
Tool to create a new project in agiled. use when you have collected all project details and need to set up the project before assigning tasks. example: "create a new project named website redesign with start date 2023-09-01 and status in progress."
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 Task
Tool to create a new task in agiled. use when you have all task details and want to add it to your project board. example: "create a task titled 'draft specs' for project 45, assigned to user 7, priority normal, due date 2025-11-05."
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 Ticket
Tool to create a new support ticket in agiled. use after gathering all required ticket details (subject, message, priority, user id).
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 Contacts
Tool to retrieve a list of all contacts. use after configuring the api key to fetch contacts with optional pagination or search filters.
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 Currencies
Tool to list currencies. use when you need to fetch available currency options after authentication.
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 Deals
Tool to retrieve a list of all deals. use after confirming your api key to list all deals for crm reporting.
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 Employees
Tool to retrieve a list of all employees. use when you need up-to-date employee directory from agiled.
Connect any two apps with Notis in the middle.
GitHub and Agiled, 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 Agiled.