Add fixture details to an Asana match task
When a match task is created, look up the relevant API Sports fixture and summarize its date, competition, and status for the task context.
When something happens in Asana, 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
Fires when an attachment is added to a task.
Do this · Action
Find coaches and view their career histories.
When a match task is created, look up the relevant API Sports fixture and summarize its date, competition, and status for the task context.
When a project task gets a comment requesting a matchup comparison, use the named teams to retrieve their head-to-head fixtures and summarize the history.
When a match task moves to a review section, fetch fixture events such as goals, cards, and substitutions and summarize the match timeline.
When a task receives a squad-planning tag, retrieve injuries and suspensions for the relevant team or fixture and summarize the available records.
When a match task is updated with a fixture reference or updated match context, retrieve fixture statistics and summarize the selected match data.
When a match preview task is created with a fixture reference, retrieve API Sports predictions and summarize them as one input to the preview.
When a comment asks for an individual performance review, retrieve player statistics from the identified fixture and summarize the requested player's contribution.
When a match preparation task moves to review, retrieve the fixture lineups and summarize the starting eleven and substitutes where available.
When a competition research task is created, search API Sports leagues and cups using the competition name or other supplied context, then summarize matching records.
Notis builds workflows that link Asana to API Sports. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Find coaches and view their career histories.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Retrieve AFL games and matches.
Fires when an attachment is added to a task.
List countries available for league searches.
Fires when a comment is added to a task in a project.
Retrieve player statistics from AFL games.
Fires when a new task is created in a project.
Retrieves football fixtures and matches using filters such as date, league, or team.
Fires when a task is moved to a section in a project.
Retrieve available AFL seasons.
Fires when a tag is added to a task.
View match events such as goals, cards, substitutions, and VAR decisions.
Fires when a task is updated in a project.
Retrieve AFL team standings for a league and season.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,600+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
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:
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.
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Asana and API Sports, or any other combination from 1,600+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business API Sports.