Connect Aeroleads to Box

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

View example

Create a Box dossier for each new prospect

Start a prospect dossier in Box when an Aeroleads lead is ready for research, with the lead details and enrichment results organized in one place.

View example

Share a Box file for a qualified prospect

When a lead reaches a defined stage, have Notis create a shared link to the relevant Box file so collaborators can review the same material.

View example

Assign a Box task after a lead handoff

When a prospect is handed off through a webhook, assign a Box task on the relevant file so the next review step has an owner.

View example

Prepare Box folders for upcoming prospect campaigns

On a recurring schedule, use campaign information you provide to create Box folders for upcoming Aeroleads prospecting work.

View example

Share a prospect research folder with a reviewer

When a lead is ready for review, create a Box shared link for the specified prospect folder to make the research easier to access.

View example

Schedule recurring reviews of prospect files

On a recurring schedule, assign Box tasks to review specified prospect files so ongoing lead research receives a regular check.

View example

Add a lead handoff note to a Box file

When a webhook reports a prospect handoff, add a concise comment to the specified Box file with the context supplied for the next person.

View example

Classify sensitive prospect files in Box

When a lead handoff includes a sensitivity decision, apply the specified Box classification to its file.

View example

Refresh shared links for scheduled prospect reviews

On a recurring schedule, create or update a shared link for specified Box prospect files ahead of a planned review.

Supported Triggers and Actions

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

Aeroleads triggers

Box actions

Recurring trigger

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

TriggerScheduled

Add classification to file

Adds a classification label to a file.

ActionInstant

Webhook trigger

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

TriggerInstant

Add classification to folder

Adds a classification label to a folder.

ActionInstant

Add domain to list of allowed collaboration domains

Allows a domain for inbound, outbound, or two-way enterprise collaboration.

ActionInstant

Add initial classifications

Sets up an enterprise’s initial classification options.

ActionInstant

Add or update user avatar

Adds or updates a user’s avatar.

ActionInstant

Add shared link to file

Adds a shared link to a file.

ActionInstant

Add shared link to folder

Adds or updates a shared link to a folder.

ActionInstant

Add shared link to web link

Adds a shared link to a web link.

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.