Connect Affinda to Chaser

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

View example

Create Chaser invoices from parsed documents

Send an invoice document to a Notis webhook, extract its details with Affinda, and create the invoice in Chaser when its customer is confirmed.

View example

Add customers from verified documents

Use Affinda to extract customer details from a submitted document and create a Chaser customer when the document provides enough information.

View example

Refresh Chaser customer details from documents

Extract updated customer information from a submitted document and update a Chaser customer when its external ID is confirmed.

View example

Apply verified invoice corrections in Chaser

Extract a correction from a submitted document and update a Chaser invoice after confirming the existing invoice record.

View example

Create Chaser credit notes from adjustment documents

Extract credit note details from a submitted adjustment document and create a Chaser credit note after the invoice adjustment is confirmed.

View example

Review queued invoice documents on a schedule

On a schedule, have Notis process invoice documents available to Affinda and update confirmed matching invoices in Chaser.

View example

Update multiple Chaser customers from a document batch

Extract customer records from a submitted document batch and bulk upsert confirmed customer details in Chaser.

View example

Process invoice document batches into Chaser

Extract multiple invoice records from a submitted document batch and bulk upsert them in Chaser after confirming invoice identifiers and customers.

View example

Process adjustment batches into Chaser credit notes

Extract confirmed credit note records from a submitted adjustment batch and bulk upsert them in Chaser.

Supported Triggers and Actions

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

Affinda triggers

Chaser actions

Recurring trigger

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

TriggerScheduled

Create Invoice

Creates a new invoice record in the organization.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Contact Person

Adds a contact person to an existing customer account.

ActionInstant

Get Credit Notes

Retrieves credit notes.

ActionInstant

Get Customer by ID

Retrieves detailed information about a specific customer.

ActionInstant

Create Overpayment

Creates an overpayment record for an existing customer to track credit toward future invoices.

ActionInstant

Get Customers

Retrieves a list of all customers and their contact and status details.

ActionInstant

Delete Contact Person

Deletes a contact person from a customer record.

ActionInstant

Get Organization

Retrieves information about the connected organizations.

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.