Connect Addressfinder to Bigml

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

View example

Group Addressfinder-verified data work in BigML

When your backend sends a webhook after address data passes your checks, create a BigML project to organize the related modeling work.

View example

Annotate BigML sources after address quality checks

On a webhook from your address quality process, update the name, description, or tags of a specified BigML source to reflect its review status.

View example

Review BigML datasets alongside address data work

On a recurring schedule, list BigML datasets and have Notis summarize the inventory for follow-up, using any address data context you provide.

View example

Check BigML sources for address data follow-up

Schedule a BigML source listing and ask Notis to flag sources that may need address quality follow-up based on details or criteria you provide.

Supported Triggers and Actions

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

Addressfinder triggers

Bigml actions

Recurring trigger

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

TriggerScheduled

Create External Connector

Creates an external connector for a data source.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Project

Creates a project to group related resources.

ActionInstant

Delete Project

Permanently deletes a project.

ActionInstant

Get External Connector

Retrieves details of an external connector.

ActionInstant

Get Configuration

Retrieves a configuration’s stored parameters and details.

ActionInstant

Get Project

Retrieves project details.

ActionInstant

List Correlations

Lists existing correlation resources.

ActionInstant

Get Source

Retrieves details about a source’s raw data and parsing configuration.

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.