Connect Box to Detrack
When something happens in Box, Notis takes the next step in Detrack. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Box to Detrack
Turn Box collection requests into Detrack collections
When a collection request is added to a Box intake folder, extract its details and create the Detrack collection when the required information is present.
Apply revised delivery instructions from Box
When a new version of a delivery instruction file appears in Box, compare it with the prior version and update the identified Detrack delivery when the change is clear.
Find Detrack jobs tied to a Box exception report
When an exception report is added to Box, use its stated delivery identifiers to search Detrack and return matching jobs for follow-up.
Turn Box delivery corrections into Detrack updates
When a new comment is added to a delivery file in Box, use it to update the identified Detrack delivery when it contains a clear correction.
Look up deliveries when Box paperwork is signed
When a Box Sign request changes status, search Detrack using delivery identifiers available in the request context and report matching jobs.
Review Detrack jobs when Box assigns a task
When a new Box task assignment is added, list Detrack jobs using any delivery criteria stated in the task and summarize likely matches for the assignee.
Prepare a Detrack delivery snapshot from a Box dispatch file
When a dispatch file's metadata changes, retrieve Detrack deliveries for the date clearly stated in the file and summarize them alongside the file update.
Review Detrack collections when a Box folder gains a collaborator
When a new collaborator is added to a Box folder used for collection planning, retrieve Detrack collections and provide a concise handoff summary.
Find delivery records linked to a changed Box task
When a Box task changes, search Detrack with delivery identifiers in the task and report matching jobs to support the next step.
Supported Triggers and Actions
Notis builds workflows that link Box to Detrack. A trigger fires from one place; an action lands in another.
Box triggers
Detrack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Collection
Tool to add a new collection in detrack. use after gathering all necessary collection details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete All Collections
Tool to delete all collections in the account. use when you need to purge every collection for a specific date after confirmation.
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.
Delete All Deliveries
Tool to delete all deliveries for a specific date. use when you need to purge deliveries in bulk before scheduling new ones.
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.
Delete Delivery
Tool to delete one or more deliveries by date and d.o. number. use after confirming delivery entries to avoid accidental data loss (max 100 items per call).
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.
Edit Delivery
Tool to edit specific deliveries by date and d.o. number. use after confirming delivery identifiers to update their details (max 100 per call).
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.
List Jobs
Tool to list all jobs with optional filters and pagination. use when you need to retrieve jobs by date, status, country, or other criteria.
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.
Search
Tool to search for deliveries, collections, or vehicles. use after defining search criteria to retrieve matching jobs.
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.
View All Collections
Tool to view all collection jobs in detrack. use when you need to retrieve every collection job currently stored.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Box and Detrack
Connect any two apps with Notis in the middle.
Box and Detrack, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Detrack.