Connect Box to Docnify

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

View example

Send New Box Contracts for Docnify Signature

When a contract is added to a designated Box folder, have Notis prepare the matching Docnify document for signature and send it to the intended recipients.

View example

Add Box Invitees as Docnify Recipients

When a pending Box collaboration invite arrives, use the invitee details to add that person to a specified Docnify document after confirming its ID.

View example

Review Docnify Record After Box Sign Changes

When a Box Sign request changes, fetch the related Docnify document so its current details can be reviewed alongside the Box event.

View example

Update Docnify Fields After Box Contract Comments

When a new Box file comment calls for a specific field correction, have Notis update the corresponding Docnify document field after verifying the document and field.

View example

Check Docnify When a Box Contract Version Arrives

When a new version of a Box contract is uploaded, fetch the related Docnify document details for review before signing proceeds.

View example

Review Docnify Documents When Box Folder Gets New Items

When an item is added to a designated Box folder, list Docnify documents and report the entries relevant to the folder's workflow for review.

Supported Triggers and Actions

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

Box triggers

Docnify actions

Recurring trigger

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

TriggerScheduled

Add Document Recipient

Tool to add a recipient to a document. Use after confirming the document's ID. Optionally specify signing order and authentication options.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Document Fields

Tool to create one or more fields on a document. Use after fetching a document to add fields before sending.

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

Delete Document

Tool to delete a specific document by its ID. Use when you have confirmed the document should be permanently removed.

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

Delete Document Field

Tool to delete a field from a document. Use when you need to remove a specific field from an existing document.

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

Delete document recipient

Tool to remove a recipient from a document. Use after verifying document and recipient IDs to revoke access.

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

Get Document

Tool to fetch a specific document by its ID. Use when you need to view a document's current state and metadata.

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

Get Template

Tool to fetch a specific template by its ID. Use to view a template's details and metadata.

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

List Documents

Tool to list documents in the Docnify account.

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.