Request a collection overview when you need it
Start a fresh collections lookup with an HTTP request and send the run report where it helps.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
A one-off collection lookup can interrupt focused work when it takes several manual app steps.
- Start a lookup from an HTTP request.
- Retrieve a current collections overview on demand.
- Keep the result in the selected run report channel.
Setup
Build it in a few focused steps.
- 1Connect 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 list Countdown collections and summarize the available results.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test by sending one real HTTP request and reviewing the report.
Questions about this workflow
What starts this workflow?
An HTTP request to the Notis webhook starts it.
Does the webhook accept collection filters?
The trigger is an HTTP request. Specific input fields are not described here, so do not assume a particular filter payload.
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.