Automations
When files land, things happen.
Write a rule once — when this happens, if these conditions hold, do these things — and Boita runs it every time: a delivery link to the client, a message to the channel, a tag for the report. No scripts, no cron, and a dry-run before you switch it on.
Plans: Rules come with Studio and Enterprise. The email-in address is on Pro and above. Calendar links, Slack and Teams notifications and REST hooks follow their own plan lines below.
How it works
In order
- 01
Pick a trigger
Files land in the workspace, a delivery is downloaded, a portal upload completes or is reviewed, or a time of day on chosen weekdays.
- 02
Narrow it with conditions
A folder prefix, file extensions, a size range, a specific portal, a weekly window. A rule with no conditions fires on every matching event.
- 03
Add up to ten actions
Email, a chat message, a share link with expiry and recipients, a tag. Test it against the last matching event and see exactly what each action would do before anything is sent.
Everything in Automations
Shipped items are marked Live; the rest is committed roadmap or built and waiting on an outside approval, and says so.
- Live
Five triggers
Files land (an upload, an import or a filed email), a delivery is downloaded, a portal upload completes, a portal upload is approved or rejected, or a daily schedule in the workspace time zone.
- Live
Conditions that read like the job
Folder prefix, up to 50 extensions, minimum and maximum size, one portal, days and hours. "Renders/ and .mov over 2 GB on weekdays" is one rule.
- Live
Create a delivery link
Turn the landed files into a share link with expiry (capped by your plan and policy), up to 50 recipients, email verification and a message — the moment the last file finishes.
- Live
Email and chat
Email up to 10 people with a templated subject and body, or post to a channel. Templates know the file, the folder, the sender, the byte count, the link and the decision.
- Live
Slack and Microsoft Teams apps
Deliveries, comments, approvals, portal uploads and quarantines post to your channel; delivery links unfurl; /boita send makes a link from chat. Studio and above.
- Live
Dry-run and a runs log
Test evaluates a rule against the most recent matching event and shows what would happen. Every real run is logged with its outcome; failed actions retry on a ladder up to 12 hours; runs are kept 30 days.
- Live
Email-in address
ingest-<token>@in.boita.io files the attachments of any mail under Inbox/<date>/<subject>, thanks the sender, and raises an event rules can act on. Rotate the address whenever you like. Pro and above.
- Live
Calendar links
An embargoed delivery and a portal deadline both offer an .ics with a reminder, so the moment sits in the calendar of everyone who needs to be there.
- Live
Zapier, Make and n8n
The same events reach any workflow platform through REST hooks on the API (Pro and above). Generated integrations for the three platforms are built; the public listings follow their reviews.
- Live
Also deliver to
Send an upload to several destinations at once — a client’s cloud drive, your own bucket, a second workspace folder — by naming delivery rules on the send.
- →Coming
Request approval as an action
A rule that opens a review with approvers when files land. Reserved; skipped today with a note in the run log.
The numbers
Real limits, stated up front.
Taken from the product’s configuration and plan data, not from a sales deck.
Can a rule send the wrong thing to a client?
It can only do what you wrote, and you can see that before it runs: Test shows each action against the last real event with nothing sent. A share-link action also respects workspace policy — if links must have a password, the rule fails cleanly instead of sending an open link.
Do I need a developer for this?
No. Rules are built in the app from dropdowns and templates. If you do have developers, the same events are available as signed webhooks, a polling event stream and REST hooks for workflow platforms.
What happens to rules if we change plan?
Rules are kept. On a plan without automations they stop firing until the plan includes them again; nothing is deleted.
Where does email-in mail go?
Only the attachments are kept, under Inbox/<date>/<subject> in your workspace. The sender gets a confirmation or a reason it could not be filed. The panel says so if inbound mail is not switched on for your deployment yet.
Next step
Try it, or ask first.
Start free with 10 GB and no card, book a demo, or talk to a person on WhatsApp. Leads from this page reach us with the page name attached, so the reply already knows what you read.
Write the rule once.
Automations come with Studio; email-in with Pro. Start free and build the rule in dry-run mode before you upgrade.