Connect Jira to Circleci

When something happens in Jira, 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

Build an automation Browse examples

Examples

Ways Notis can move work from Jira to Circleci

View example

Run CircleCI when a Jira issue is ready for QA

Start a CircleCI pipeline when a Jira issue moves into your QA-ready state, so the build starts without a manual handoff.

View example

Build from a Jira release request

Turn a qualifying new Jira release request into a CircleCI pipeline run, with the project and branch defined in your instruction.

View example

Start a CircleCI bootstrap build for a new Jira project

When Jira adds a project, have Notis start the CircleCI setup or validation pipeline you specify.

View example

Get a scheduled CircleCI pipeline digest alongside Jira work

Ask Notis to list CircleCI pipelines on a schedule and summarize recent runs for the project context you provide.

View example

Look up CircleCI job details from a webhook request

Send Notis a webhook containing a CircleCI job number and have it retrieve that job's status, timing, and executor details.

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.

TriggerScheduled

Get Job Artifacts

Tool to retrieve artifacts produced by a specific job. use after a job has completed to list its output files.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Get Pipeline Config

Tool to fetch pipeline configuration by id. use when you need the source or compiled yaml of a specific pipeline.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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).

ActionInstant

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.

ActionInstant

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.

ActionInstant

Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.