Check build job details during issue follow-up
Get the current job facts alongside an issue update, without opening several build pages.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Get Job Details
Tool to fetch details of a specific job within a project. use when you need status, timing, and executor information for a circleci job by its number.
Why this helps
Switching between issue triage and job pages makes small follow-ups harder to finish.
- See job status and timing in the follow-up flow.
- Reduce context switches while triaging changes.
- Bring executor details into technical review.
Setup
Build it in a few focused steps.
- 1Connect Linear and CircleCI to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Tell Notis to fetch details for the CircleCI job relevant to an updated issue when a job check is useful.
- 4Select the Linear Issue Updated trigger and choose a channel for run reports.
- 5Test with one real issue connected to a CircleCI job.
Questions about this workflow
Does the action require a job number?
Notis needs to identify the relevant CircleCI job from the issue context and connected data.
Can it tell me whether a job is running or complete?
The job details include status and timing information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Circleci. A trigger fires from one place; an action lands in another.
Linear triggers
Circleci actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Job Artifacts
Tool to retrieve artifacts produced by a specific job. use after a job has completed to list its output files.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Job Details
Tool to fetch details of a specific job within a project. use when you need status, timing, and executor information for a circleci job by its number.
Comment Received Trigger
Triggered when a comment is received.
Get Pipeline Config
Tool to fetch pipeline configuration by id. use when you need the source or compiled yaml of a specific pipeline.
Issue Created Trigger
Triggered when a new issue is created.
Get Test Metadata
Tool to fetch test metadata for a specific job. use when you need detailed test results, run times, and failure messages after a job completes.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get User Information
Tool to retrieve information about a circleci user by their unique id. use when you need user profile details after obtaining the user id.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
List Pipelines for Project
Tool to list all pipelines for a specific project. use when you need to retrieve the pipelines for a project (e.g., to display recent runs on a dashboard).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
List Self-Hosted Runners
Tool to list available self-hosted runners. use when you need to retrieve all configured self-hosted runners for your organization.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
List Workflows by Pipeline ID
Tool to list all workflows associated with a specific pipeline. use when you need to fetch or paginate through workflows by pipeline id.
Connect any two apps with Notis in the middle.
Linear and Circleci, 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 Circleci.