Turn a CircleCI job number into a test summary
Fetch test results, runtimes, and failure messages for a completed job when someone asks in chat.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Finding which tests failed and why can pull a founder into CI logs when they only need the key details.
- Surface failure messages from completed jobs
- Include test runtimes in the summary
- Reduce time spent searching through CI output
Setup
Build it in a few focused steps.
- 1Connect 2chat and CircleCI once in the Notis portal.
- 2Create an automation by telling Notis in plain language or using Automations, New Automation in the portal.
- 3Describe that a request with a completed CircleCI job number should retrieve test metadata and summarize failures and runtimes.
- 4Pick the notis_webhook trigger and choose where run reports should go.
- 5Test with one real completed job that has test results.
Questions about this workflow
Does the job need to be complete?
Yes. The action is intended to retrieve test metadata after a job completes.
What does the metadata include?
It can include detailed test results, runtimes, and failure messages.
Can this explain the root cause of a failure?
It can summarize the returned test details. Any diagnosis beyond those results depends on the available information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 2chat to Circleci. A trigger fires from one place; an action lands in another.
2chat 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.
Get Pipeline Config
Tool to fetch pipeline configuration by id. use when you need the source or compiled yaml of a specific pipeline.
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.
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.
2chat 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.