Connect Affinity to Adyntel

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

View example

Check a company’s LinkedIn ads from an Affinity deal

When an Affinity deal needs a closer look, retrieve the company’s LinkedIn ads using its domain or LinkedIn page ID.

View example

Review a prospect’s Meta ads from an Affinity request

Start a Meta ad lookup for a company domain or Facebook page URL when a prospect enters your research workflow.

View example

Scan portfolio companies for Google ads

Run a recurring scan of user-supplied portfolio company domains and retrieve their Google ads for review.

View example

Search Meta ads when a campaign idea arrives

Send a topic into a Notis webhook to search the Meta ad library and collect related examples for campaign planning.

View example

Compare a competitor’s paid and organic keywords

On a recurring schedule, analyze paid versus organic keyword performance for company domains you choose.

View example

Find TikTok ads related to a research topic

Start a TikTok ad search when a research topic arrives by webhook and summarize matching examples.

View example

Track TikTok ad examples for chosen keywords

Run a scheduled TikTok ad library search for keywords you provide and review matching creatives and engagement details.

View example

Look up LinkedIn ads from a competitor research request

Send a company domain or LinkedIn page ID through a webhook to retrieve LinkedIn ad creatives and campaign details.

Supported Triggers and Actions

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

Affinity triggers

Adyntel actions

Recurring trigger

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

TriggerScheduled

Get Google Ads By Company

Retrieves ads associated with a company domain.

ActionInstant

Webhook trigger

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

TriggerInstant

Search Meta Ads

Searches ads in the Meta ad library.

ActionInstant

Get Google Shopping Search Status

Checks a Google Shopping ad search and retrieves its results.

ActionInstant

Get LinkedIn Ads By Company

Retrieves a company’s LinkedIn ads, creatives, and campaign details.

ActionInstant

Get Meta Ads By Company Or Page

Retrieves a company’s Meta ads, creatives, engagement metrics, and campaign details.

ActionInstant

Get Paid Vs Organic Keywords

Compares a company’s paid and organic keyword performance.

ActionInstant

Search TikTok Ads By Keyword

Searches TikTok ads by keyword and returns matching ads and details.

ActionInstant

Start Google Shopping Search

Starts an asynchronous Google Shopping ad search for a company.

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.