Connect Adyntel to Countdown api

When something happens in Adyntel, 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 Adyntel to Countdown api

View example

Turn LinkedIn competitor findings into an eBay collection

Use an Adyntel competitor ad report to create a Countdown collection for related eBay research.

View example

Add eBay requests from Adyntel keyword insights

Use supplied Adyntel keyword or ad-copy findings to add specific eBay requests to an idle collection.

View example

Expand ad-derived eBay search terms

Use Adyntel search and ad language to request eBay autocomplete suggestions before creating research requests.

View example

Find eBay requests matching an ad campaign

Search an existing Countdown collection for requests tied to a supplied Adyntel campaign reference or query.

View example

Route ad research results to a Countdown destination

Create a Countdown destination using destination details explicitly supplied with an Adyntel reporting payload.

View example

Review Countdown collections for an Adyntel research brief

Use a supplied Adyntel brief to list and inspect relevant Countdown collections.

View example

Inspect one eBay collection during campaign review

Retrieve details for a specific Countdown collection named in an Adyntel campaign payload.

View example

Retrieve a Countdown result set for an Adyntel insight

Fetch a specific completed Countdown result set identified in a supplied Adyntel report.

View example

List result sets for an Adyntel campaign

List retained Countdown result sets for the collection identified in an Adyntel campaign payload.

Supported Triggers and Actions

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

Adyntel 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

Clears all pending requests from a collection.

ActionInstant

Webhook trigger

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

TriggerInstant

Create a new collection

Creates a collection for batching and scheduling requests.

ActionInstant

Get Collection

Retrieves details about a collection.

ActionInstant

List Collections

Lists collections in the authenticated account.

ActionInstant

Start Collection

Starts processing the queued requests in a collection.

ActionInstant

Update an existing collection

Updates the settings of an existing collection.

ActionInstant

eBay Autocomplete

Fetches autocomplete suggestions for search terms.

ActionInstant

Create Destination

Creates a cloud storage destination for batch results.

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.