Check Countdown capacity when a research request arrives
See current Countdown usage and platform status while a new Jira research request is top of mind.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Get Account Information
Tool to retrieve account usage and current platform status. Use when needing to check plan, usage, and quota details for the authenticated user.
Why this helps
A founder may plan research work before checking available Countdown usage or platform status.
- Bring current account usage into the research planning moment.
- Check platform status when new work is requested.
- Reduce context switching before deciding next steps.
Setup
Build it in a few focused steps.
- 1Connect Jira and Countdown api once in the Notis portal.
- 2Create an automation in the portal, or tell Notis in plain language from any channel.
- 3Ask Notis in one instruction to retrieve Countdown account usage and platform status when a Jira research request arrives.
- 4Pick Jira New Issue as the trigger and choose where run reports should go.
- 5Test with one real Jira issue and review the account information in the run report.
Questions about this workflow
Does this check a specific Jira field?
The listed New Issue trigger fires for issues created in the configured project. No field filter is listed.
Can it guarantee there is enough quota for a request?
It retrieves account usage and current platform status. The issue does not provide a quota forecast for a particular research request.
When this happens · Trigger
Do this · Action
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.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a new collection
Tool to create a new collection. Use when you need to batch and orchestrate multiple requests on a schedule.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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.
New Project
Triggered when a new project is added in Jira
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.
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.
Start Collection
Tool to start processing a collection's queued requests. Use after creating or pausing a collection to initiate its queued requests.
Update an existing collection
Tool to update an existing collection. Use when you need to modify collection settings before scheduling runs.
eBay Autocomplete
Tool to fetch eBay autocomplete suggestions. Use when needing search-term-based suggestions from Countdown API.
Create Destination
Tool to create a destination. Use when you need to set up a new destination for results or notifications.
Connect any two apps with Notis in the middle.
Jira and Countdown api, 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 Countdown api.