Connect Affinity to Brightdata

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

View example

Check investor backgrounds before outreach

Search the web for public information about an investor before you send an Affinity outreach message.

View example

Enrich a company prospect with public records

Look up a company from an Affinity deal or prospect request and return matching public business records.

View example

Run a deeper company lookup for diligence

Start an asynchronous Bright Data Deep Lookup for a company tied to an Affinity deal, then review its results and progress.

View example

Collect targeted website records for a deal

Run a synchronous Bright Data scrape for up to 20 supplied input objects related to an Affinity deal request.

View example

Crawl a company domain for deal context

Start an asynchronous site crawl for supplied company URLs and follow its snapshot through completion.

View example

Scan portfolio companies for notable search changes

On a recurring schedule, search public web results for selected portfolio companies and summarize notable findings.

View example

Review search visibility for priority prospects

Search selected Affinity prospects on a schedule and surface public results that may help prioritize follow-up.

View example

Review available datasets for recurring research needs

On a recurring schedule, list Bright Data marketplace datasets and report options relevant to research needs you specify.

View example

Review Bright Data balance for research planning

Check Bright Data current and pending balances on a schedule and report them for research planning.

Supported Triggers and Actions

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

Affinity triggers

Brightdata actions

Recurring trigger

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

TriggerScheduled

Start Site Crawl

Starts an asynchronous dataset or site crawl for later status checks and result retrieval.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Safe Zone

ActionInstant

Filter Dataset

Creates a billable, filtered snapshot of a marketplace dataset.

ActionInstant

List Marketplace Datasets

Lists prebuilt marketplace datasets for structured scraping.

ActionInstant

Get Customer Balance

Retrieves current and pending account balances; the API key must have Admin permission.

ActionInstant

Get Dataset Metadata

Retrieves the field definitions for a marketplace dataset.

ActionInstant

Get Deep Lookup Results

ActionInstant

List Unlocker Zones

Lists configured zones and their types for protected URL scraping.

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.