Connect Affinda to Dovetail

When something happens in Affinda, 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 Affinda to Dovetail

View example

Turn interview documents into Dovetail research data

Send an interview transcript or document to a Notis webhook, extract its research content with Affinda, and save a titled data item in Dovetail.

View example

File survey feedback summaries in Dovetail

Use a webhook to submit survey feedback documents, extract and organize their contents with Affinda, and create a Dovetail doc.

View example

Convert interview documents into Dovetail insights

Submit interview documents through a webhook, extract and synthesize their findings, then create a Dovetail insight.

View example

Register resume contacts in Dovetail

Send resumes to a Notis webhook, extract candidate contact details with Affinda, and create Dovetail contacts when the document provides them.

View example

Record invoice document details as a Dovetail data point

Submit invoice documents through a webhook, extract key details with Affinda, and record a structured data point in a Dovetail channel.

View example

Review interview transcripts on a schedule

On a recurring Notis schedule, process the interview documents made available to Affinda and create Dovetail data items for new transcript content.

View example

Prepare scheduled survey feedback docs

On a recurring schedule, process survey feedback documents available to Affinda and create an organized Dovetail doc for review.

View example

Synthesize available research documents into insights

On a recurring schedule, extract available research documents with Affinda and create a Dovetail insight grounded in their contents.

View example

Register contacts from available resume documents

On a recurring schedule, extract contact details from resumes available to Affinda and create Dovetail contacts when details are present.

Supported Triggers and Actions

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

Affinda 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.