Connect Adrapid to Api sports

When something happens in Adrapid, Notis takes the next step in Api sports. 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 Adrapid to Api sports

View example

Turn an Adrapid campaign brief into fixture details

Use an Adrapid campaign payload to retrieve the football fixtures needed for a sports creative brief.

View example

Build a match event recap from an Adrapid sports asset request

Use an Adrapid payload with a confirmed fixture ID to retrieve goals, cards, substitutions, and other match events.

View example

Pull player stats for an Adrapid match graphic

Retrieve per-player statistics for a confirmed fixture referenced in an Adrapid creative payload.

View example

Add team match statistics to an Adrapid report

Fetch possession, shots, fouls, cards, passes, and other available fixture statistics for an Adrapid campaign.

View example

Check player availability for an Adrapid match campaign

Use supplied league, season, team, player, fixture, or date details to retrieve injuries and suspensions before publishing sports creative.

View example

Add Api sports predictions to an Adrapid campaign brief

Retrieve predictions for a confirmed fixture referenced by an Adrapid sports campaign payload.

View example

Retrieve pre-match odds for an Adrapid sports campaign

Fetch pre-match odds using fixture, league, season, date, bookmaker, and bet details supplied in an Adrapid payload.

View example

Build a team season profile for an Adrapid campaign

Retrieve detailed team statistics for the league, season, and team supplied in an Adrapid creative payload.

View example

Add AFL standings to an Adrapid campaign

Retrieve AFL rankings for the league and season specified in an Adrapid payload.

Supported Triggers and Actions

Notis builds workflows that link Adrapid to Api sports. A trigger fires from one place; an action lands in another.

Adrapid triggers

Api sports actions

Recurring trigger

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

TriggerScheduled

Get Coaches

Find coaches and view their career histories.

ActionInstant

Webhook trigger

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

TriggerInstant

Get AFL Games

Retrieve AFL games and matches.

ActionInstant

Get Countries

List countries available for league searches.

ActionInstant

Get AFL Game Player Statistics

Retrieve player statistics from AFL games.

ActionInstant

Get Fixtures

Retrieve upcoming and past football fixtures.

ActionInstant

Get AFL Seasons

Retrieve available AFL seasons.

ActionInstant

Get fixtures events

View match events such as goals, cards, substitutions, and VAR decisions.

ActionInstant

Get AFL Standings

Retrieve AFL team standings for a league and season.

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.