Bring CircleCI build artifacts into a release check
When your AgentQL release check is ready, have Notis collect the completed job's artifacts so the files are part of the same follow-up.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Job Artifacts
Retrieves files produced by a job.
Why this helps
Release checks and build output are split across tools, so collecting files can add a distracting manual step.
- Retrieve output files from a specific completed CircleCI job.
- Keep release check context close to its build artifacts.
- Avoid manually navigating to job outputs.
Setup
Build it in a few focused steps.
- 1Connect AgentQL and CircleCI once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis the outcome in plain language from any channel.
- 3Describe that a completed AgentQL release check should retrieve artifacts for its relevant CircleCI job, with the job number available.
- 4Choose a Notis webhook as the trigger and select where run reports should go.
- 5Test with one real release check and a completed job that produced artifacts.
Questions about this workflow
Can this retrieve artifacts before the job completes?
No. The CircleCI action is intended to retrieve artifacts after a job has completed.
What information is needed to retrieve artifacts?
The relevant CircleCI job number must be available to the automation.
Does the action inspect the contents of every file?
It retrieves the job's artifacts, meaning its output files. Notis can report what is returned, but file interpretation depends on the available output.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agentql to Circleci. A trigger fires from one place; an action lands in another.
Agentql triggers
Circleci actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Job Artifacts
Retrieves files produced by a job.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Context
Creates a context for sharing environment variables securely across projects.
Get Job Details
Retrieves status, timing, and executor details for a job.
Create Context (GraphQL)
Creates a context for storing environment variables; returns an error if creation fails.
Get Pipeline Config
Retrieves the source or compiled configuration for a pipeline.
Create Context Restriction
Creates a context restriction to limit access by project, rules, or group.
Get Test Metadata
Retrieves test results, run times, and failure details for a job.
Create Organization Orb Allowlist
Allows URL-based orb references with matching prefixes in an organization’s pipelines.
Connect any two apps with Notis in the middle.
Agentql 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.