Connect Affinda to Botsonic

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

View example

Train a Botsonic Bot on Approved Document URLs

When Affinda document processing is complete, send approved source URLs to Botsonic in one training update.

View example

Review Botsonic Knowledge Assets on a Schedule

Run a scheduled inventory of Botsonic bot data so Notis can summarize assets that need a human review.

View example

Find the Right Bot Before a Document Handoff

Use a webhook request to retrieve available Botsonic bots and summarize the options before sending document knowledge onward.

View example

Turn Botsonic Conversation Lists into a Review Brief

On a schedule, retrieve Botsonic conversation threads and condense the returned list into a short review brief.

View example

Check Botsonic FAQs After an Affinda Document Update

Start a webhook review after a document update and retrieve Botsonic FAQs to spot questions that may need a human check.

View example

See Botsonic Conversations with Their Sources

Retrieve Botsonic conversations with source information on a schedule and summarize useful context for follow-up.

View example

Add a Starter Question for a New Document Topic

After an Affinda document review, use a webhook to create a Botsonic starter question and answer for an approved topic.

View example

Keep Botsonic Starter Questions Focused

On a schedule, retrieve Botsonic starter questions and summarize possible gaps or overlap for a human review.

View example

Refresh a Starter Question After Document Review

Use an HTTP request with a confirmed starter question ID and approved wording to update the existing Botsonic prompt.

Supported Triggers and Actions

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

Affinda triggers

Botsonic actions

Recurring trigger

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

TriggerScheduled

Bulk Upload Bot URLs

Adds or updates multiple URLs in a bot’s training data at once.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Starter Question

Creates a preset question and answer for users to select.

ActionInstant

Delete Starter Question

Permanently deletes a starter question from a bot.

ActionInstant

Delete Uploaded File

Permanently removes an uploaded file from a bot’s training data.

ActionInstant

Get All Bot Data

Retrieves all files and resources associated with a bot.

ActionInstant

Get All Bots

Retrieves the bots associated with your account.

ActionInstant

Get All Conversations

Retrieves conversations related to a bot.

ActionInstant

Get All FAQs

Retrieves the frequently asked questions associated with a bot.

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.