Connect Affinda to Clientary

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

View example

Turn Parsed Resumes Into Clientary Leads

Create a Clientary lead from an Affinda parsed resume, carrying over the candidate's contact details and relevant experience.

View example

Create Clientary Clients From Affinda Invoice Documents

Read company and contact information in an invoice document and add a client record in Clientary for account setup.

View example

Record Affinda-Read Receipts As Clientary Expenses

Create a Clientary expense from a receipt processed by Affinda, using the extracted amount and available expense details.

View example

Add Contract Contacts To Clientary

Extract a named contact from a processed contract and create that contact under the specified Clientary client.

View example

Create Clientary Follow-Up Tasks From Document Findings

Turn a specific follow-up identified in a processed document into a Clientary task so the next action is visible.

View example

Create Clientary Projects From Signed Scopes

Use a processed signed scope to create a Clientary project with its extracted project name and rate when both are available.

View example

Schedule Clientary Tasks For Documents Awaiting Review

On a recurring schedule, create Clientary tasks for documents that your process identifies as awaiting review.

View example

Schedule Clientary Expense Entry From Processed Documents

On a recurring schedule, record eligible processed expense documents in Clientary when the required amount is available.

View example

Draft Clientary Invoices From Affinda Invoice Details

Create a Clientary invoice from supplied document details when the required invoice date, due date, and currency are present.

Supported Triggers and Actions

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

Affinda triggers

Clientary actions

Recurring trigger

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

TriggerScheduled

Create Client

Creates a new client record.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Contact

Creates a new contact for a client.

ActionInstant

Create Expense

Creates a new expense record.

ActionInstant

Create Lead

Creates a new lead record.

ActionInstant

Create Invoice

Creates an invoice, optionally linked to a client.

ActionInstant

Create Project

Creates a new project for tracking client work, time, or expenses.

ActionInstant

Delete Client

Permanently deletes a client and its related projects, invoices, estimates, and contacts; this cannot be undone.

ActionInstant

Create Project Hours

Logs hours worked on a project as a new time entry.

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.