Fetch CircleCI job details from a webhook
Send a job number to your Notis webhook and get the key CircleCI details in a run report.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Finding a job's status and timing can interrupt focused work when a build needs quick triage.
- Look up a specific job without opening CircleCI.
- Return job status, timing, and executor information.
- Use webhook requests from a system or workflow that already has the job number.
Setup
Build it in a few focused steps.
- 1Connect CircleCI once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language.
- 3Describe how to use the CircleCI job number supplied with each webhook request and what details to report.
- 4Pick a Notis webhook as the trigger and choose where run reports go.
- 5Test by sending one webhook request with a real CircleCI job number.
Questions about this workflow
What does the webhook request need?
Include the CircleCI job number so Notis can request details for that specific job.
Does this retrieve test failures too?
This action retrieves job details such as status, timing, and executor information. Use the test metadata action for detailed test results and failure messages.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Circleci. A trigger fires from one place; an action lands in another.
Jira 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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Get Pipeline Config
Tool to fetch pipeline configuration by id. use when you need the source or compiled yaml of a specific pipeline.
New Project
Triggered when a new project is added in Jira
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.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
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).
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.
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.
Jira 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.