Connect Jira to Countdown api

When something happens in Jira, Notis takes the next step in Countdown api. 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 Countdown api

View example

Turn Jira Research Issues into eBay Collections

Create a Countdown collection when a Jira issue requests eBay product research, using its details to describe the collection.

View example

Check Countdown Capacity for New Jira Requests

When a Jira issue arrives, check Countdown account usage and status so you can decide whether research work can proceed.

View example

Review a Countdown Collection When Jira Work Changes

When an existing Jira issue changes, retrieve the relevant Countdown collection details to bring collection status into the review.

View example

See Countdown Collections During Jira Updates

Use a Jira issue update to retrieve a Countdown collection overview when you need to find the collection related to active work.

View example

Schedule a Countdown Collection Inventory

On a recurring schedule, list Countdown collections and deliver a concise inventory to your chosen run report channel.

View example

Schedule a Countdown Usage and Status Check

Retrieve Countdown account usage and platform status on a recurring schedule and send the report to your chosen channel.

View example

Look Up Countdown Collections on Request

Start from an HTTP request and return a Countdown collections overview for a just-in-time research lookup.

View example

Request a Countdown Account Check

Use a Notis webhook to retrieve Countdown account usage and platform status when an external process asks for a check.

Supported Triggers and Actions

Notis builds workflows that link Jira to Countdown api. A trigger fires from one place; an action lands in another.

Jira triggers

Countdown api actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Clear Collection Requests

Tool to clear all requests from a specified collection. Use when you need to remove all queued requests for an idle collection.

ActionInstant

Webhook trigger

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

TriggerInstant

Create a new collection

Tool to create a new collection. Use when you need to batch and orchestrate multiple requests on a schedule.

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 Collection

Tool to retrieve details for a single collection by ID. Use when you need collection metadata and counts for a given collection ID.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

List Collections

Tool to list all collections for the authenticated account. Use when you need to retrieve paginated collections with filtering, sorting, and timing constraints.

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

Start Collection

Tool to start processing a collection's queued requests. Use after creating or pausing a collection to initiate its queued requests.

ActionInstant

Update an existing collection

Tool to update an existing collection. Use when you need to modify collection settings before scheduling runs.

ActionInstant

eBay Autocomplete

Tool to fetch eBay autocomplete suggestions. Use when needing search-term-based suggestions from Countdown API.

ActionInstant

Create Destination

Tool to create a destination. Use when you need to set up a new destination for results or notifications.

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.