Connect Box to Chaser

When something happens in Box, 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 Box to Chaser

View example

Turn Box invoice files into Chaser invoice records

When a new file lands in your Box invoice folder, extract the invoice details and create the Chaser invoice after confirming the customer exists.

View example

Update invoice status after a Box Sign request changes

Use a Box Sign status change as a cue to review the related Chaser invoice and update its status when the agreement outcome supports it.

View example

Create a Chaser invoice from an approved Box Sign request

When a Box Sign request is created, check its available details and create a Chaser invoice only when the request contains the invoice information and customer match you require.

View example

Refresh a Chaser customer contact from Box file changes

When a designated customer record file changes in Box, use its current details to update the matching Chaser customer by external ID.

View example

Apply revised invoice details from a new Box version

When a Box invoice file gets a new version, review its updated details and revise the existing Chaser invoice when it can be matched confidently.

View example

Create a Chaser customer from a Box intake file

When a new item is added to a Box customer intake folder, create a Chaser customer from the available details when the record is complete and not already present.

View example

Use Box invoice comments to flag a Chaser invoice update

When a comment is added to a Box invoice file, interpret the requested change and update the matching Chaser invoice only when the comment and invoice identify a clear supported change.

View example

Review Chaser customers against Box records on a schedule

On a recurring schedule, compare Chaser customer details with the Box records you specify and report discrepancies for follow-up.

View example

Get a scheduled Chaser organization billing context report

On a schedule, retrieve Chaser organization details and summarize the currency, timezone, and legal information available for your billing operations.

Supported Triggers and Actions

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

Box triggers

Chaser actions

Recurring trigger

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

TriggerScheduled

Create Invoice

Tool to create a new invoice record in the organization. use after ensuring the customer exists in chaser.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Credit Notes

Tool to retrieve a list of credit notes. use after authenticating this detail.

ActionInstant

Collaboration Details Changed

Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.

TriggerPolling

Get Customer by ID

Tool to retrieve details for a specific customer by their external (source system) id. use after obtaining the external id when you need specific customer information.

ActionInstant

Comment Changed

Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.

TriggerPolling

Get Customers

Tool to retrieve a list of all customers associated with the organization. use when you need to display or process complete customer contact and status information.

ActionInstant

New File Comment Added

Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.

TriggerPolling

Get Organization

Tool to retrieve information about the connected organizations. use when you need organization ids, currency, timezone, or legal details before other operations.

ActionInstant

File Metadata Changed

Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.

TriggerPolling

Create Credit Note

Tool to create a new credit note record in the organization. use after confirming invoice adjustments.

ActionInstant

File Shared Link Changed

Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.

TriggerPolling

Create Customer

Tool to create a new customer record in chaser. use after obtaining basic auth credentials.

ActionInstant

New File Version Uploaded

Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.

TriggerPolling

Update Customer

Tool to update an existing customer's information using their unique externalid. use after confirming the customer's externalid. e.g., "update contactemailaddress for externalid cust abc123."

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.