Connect Agenty to Circleci
When something happens in Agenty, Notis takes the next step in Circleci. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Agenty to Circleci
Run CI When a Website Change Is Detected
Send an Agenty website-change result to Notis and trigger a CircleCI pipeline to validate the affected project.
Check the CircleCI Job After an Agenty Browser Run
Use an Agenty browser workflow result to look up the related CircleCI job's status, timing, and executor details.
Review Build Artifacts After an Agenty Browser Check
After an Agenty browser check reports a result, retrieve the artifacts from the related completed CircleCI job.
Get Test Failure Context for an Agenty Finding
When Agenty reports a browser issue, retrieve CircleCI test metadata for the related completed job to add failure details and timings.
Compare a Scraped Config Change with Pipeline Configuration
When Agenty extracts a configuration change, retrieve the related CircleCI pipeline configuration for review.
Review Workflows for a Pipeline Mentioned by Agenty
When Agenty reports a relevant site or service change, retrieve the workflows associated with the referenced CircleCI pipeline.
Check Recent Pipelines After an Agenty Change Alert
Use an Agenty website or structured-data alert to retrieve recent pipelines for the relevant CircleCI project.
Check Self-Hosted Runners After a Browser Workflow Failure
When Agenty reports a failed or delayed browser workflow, list available CircleCI self-hosted runners for operational context.
Look Up a CircleCI User Referenced in an Agenty Report
When an Agenty result includes a CircleCI user reference, retrieve that user's profile details for a clear handoff.
Supported Triggers and Actions
Notis builds workflows that link Agenty to Circleci. A trigger fires from one place; an action lands in another.
Agenty 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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Agenty and Circleci
Connect any two apps with Notis in the middle.
Agenty 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.