Connect Adyntel to Dovetail

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

View example

Turn competitor ad messaging into a Dovetail insight

Analyze LinkedIn ads from selected competitors and save recurring messages, claims, and audience themes as a Dovetail insight.

View example

File a weekly competitor ad research brief

On a schedule, review selected LinkedIn ads with Adyntel and create a Dovetail doc summarizing notable changes and patterns.

View example

Save an Adyntel campaign analysis as Dovetail data

Turn a requested LinkedIn campaign analysis into a structured Dovetail data item for later research and retrieval.

View example

Turn an ad insight request into Dovetail notes

Ask Adyntel a focused question about LinkedIn ads and preserve the analysis as a Dovetail note for your team.

View example

Add scheduled ad themes as Dovetail data points

Run a scheduled Adyntel review and record distinct LinkedIn ad themes as classified data points in a Dovetail channel.

View example

Create a Dovetail channel for a competitor ad study

Start a focused Adyntel competitor ad study and create a dedicated Dovetail channel after its purpose and details are clear.

View example

Organize ad research under a Dovetail topic

Analyze a defined LinkedIn ad research request and create a topic in the specified Dovetail channel when a new theme needs a home.

View example

Archive Adyntel campaign reports in Dovetail

On a recurring schedule, generate Adyntel campaign reports and keep each report as a titled Dovetail doc in your research project.

View example

Capture competitor positioning evidence in Dovetail

Analyze selected LinkedIn ads and save supported positioning claims, creative cues, and unanswered questions as Dovetail project data.

Supported Triggers and Actions

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

Adyntel triggers

Dovetail actions

Recurring trigger

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

TriggerScheduled

Create Channel

Create a channel to organize and collect feedback.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Contact

Create a new contact.

ActionInstant

Create Data Point

Record and classify a data point in a channel.

ActionInstant

Create Data

Creates a research data item in a project.

ActionInstant

Create Insight

Save a research insight, optionally linking it to a project.

ActionInstant

Create Topic

Create a topic in a channel to organize feedback.

ActionInstant

Create Doc

Creates a document in a project; its content is stored but not returned.

ActionInstant

Delete Channel

Move a channel to the project trash, where it can be restored for 30 days.

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.