Check the related job at your release checkpoint
Make the release handoff easier by having Notis fetch the job details named in your validation checkpoint request.
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
A release check can become another hunt for status, duration, and executor details across tools.
- Fetches job status, timing, and executor information for a specific run.
- Keeps a release checkpoint focused with relevant build context.
- Removes a manual lookup step from the handoff.
Setup
Build it in a few focused steps.
- 1Connect Zerobounce and CircleCI to Notis once in the portal.
- 2Create an automation in the portal, or ask Notis to fetch CircleCI job details when a release-check webhook arrives.
- 3Describe in one plain-language instruction how the request identifies the job to inspect.
- 4Select an incoming webhook trigger and choose where run reports should arrive.
- 5Test with a real job number and verify the status and timing are for the intended run.
Questions about this workflow
Does this fetch output files?
No. It fetches job details such as status, timing, and executor information. Use the artifact action for output files.
How does a validation checkpoint start the workflow?
Your release process or custom backend sends an HTTP request to the Notis webhook.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Zerobounce to Circleci. A trigger fires from one place; an action lands in another.
Zerobounce 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.
Zerobounce 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.