Connect Affinda to Anchor browser

When something happens in Affinda, Notis takes the next step in Anchor browser. 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 Anchor browser

View example

Open a focused resume review session

Start an isolated browser session when Affinda parses a resume, ready for a recruiter to review the candidate in the hiring system.

View example

Check a vendor page after invoice parsing

Retrieve rendered webpage content for the vendor website associated with an invoice Affinda has parsed.

View example

Navigate to a document's review portal

Use a URL supplied with an Affinda document extraction request to open the relevant review portal in an existing browser session.

View example

Prepare a parsed document for browser upload

Upload a document file from the Affinda workflow as an agent resource in an Anchor browser session for a supported web form.

View example

Enter a reviewed extracted value in a form

Paste a specific value from an Affinda extraction into the currently focused field in an Anchor browser session.

View example

Click a known control on a review page

Click a specified coordinate in an Anchor browser session after an Affinda document workflow reaches a review step.

View example

List open tabs for a document review

Retrieve the pages open in a browser session associated with an Affinda document review request.

View example

Check files downloaded during a review session

Retrieve download metadata from an Anchor browser session linked to an Affinda document workflow.

View example

Check the result of a document browser task

Retrieve the output or error details for a specific Anchor browser task execution tied to an Affinda document workflow.

Supported Triggers and Actions

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

Affinda triggers

Anchor browser actions

Recurring trigger

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

TriggerScheduled

Create Profile

Create a browser profile from an active session to preserve its data.

ActionInstant

Webhook trigger

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

TriggerInstant

Click Mouse

Click at specified coordinates in a browser session.

ActionInstant

Delete Profile

Delete a browser profile.

ActionInstant

Copy Selected Text

Copy the currently selected text in a browser session to the clipboard.

ActionInstant

End All Sessions

End all active browser sessions.

ActionInstant

Create Integration

Create an integration that is immediately available in browser sessions and profiles.

ActionInstant

End Browser Session

End a specific browser session.

ActionInstant

Create or Update Task Draft

Create or update a task’s draft version for development and testing.

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.