Integrations
It fits the tools you already have.
Deliveries post to the channel. Landed files go on to the cloud drive the client uses. The edit suite sends renders on its own. A pipeline drives it from the CLI, the SDKs or a workflow platform. What is not built yet is marked as coming.
Plans: Slack and Teams apps come with Studio and Enterprise. REST hooks for workflow platforms, the CLI, SDKs and API keys are on Pro and above. Cloud-drive destinations, the edit-suite presets and the panel are on every plan that has the underlying feature.
Boita09:12
Delivery “Ridge survey · orthomosaics” is up — 4 files, 1.95 TB, expires in 7 days.
Boita11:40
priya@client.example downloaded 4 of 4 files · verified · 2.1 Gbps · 1 h 58 min.
Boita11:52
New comment on orthomosaic_north.tif: “North edge looks great, approved.”
ravi12:03
/boita send Deliveries/Ridge/dsm_full.tif
How it works
In order
- 01
Connect once
Add the Slack or Teams app to a channel, paste a webhook, connect a cloud drive, or create an API key under Developers. Secrets are shown once and stored encrypted.
- 02
Pick what should flow
Which events reach the channel, which folder goes to which drive, which watch folder uses which preset, which rule fires on which trigger.
- 03
Forget it is there
Every delivery, comment, approval, portal upload and quarantine shows up where the team already looks; every failure is retried and logged.
Everything in Integrations
Shipped items are marked Live; the rest is committed roadmap or built and waiting on an outside approval, and says so.
- Live
Slack
Deliveries, comments, approvals, portal uploads and quarantines to your channel; delivery links unfurl; /boita send makes a link from chat. Studio and above.
- Live
Microsoft Teams
The same notifications to a Teams channel through an incoming webhook today; the full Teams app with unfurls and commands follows its directory registration.
- Live
Zapier, Make and n8n
REST hooks on the API expose every event to the three platforms with generated integrations; works today with an API key, public listings follow their reviews. Pro and above.
- Live
Cloud-drive destinations
Deliver a share or any files straight into the cloud drive the client already uses — the four common ones — as a send option or an automation action; the personal drives connect as each app review clears.
- Live
Object storage
Import from any S3-compatible bucket; auto-deliver to your own S3-compatible bucket or transfer server (Enterprise). Buckets on the other major clouds work through their S3-compatible endpoints today; native connectors are coming.
- Live
Premiere Pro panel
Deliver renders, jump to reviewers’ timecoded notes and import from the workspace without leaving the edit; the marketplace listing follows the developer-account step.
- Live
Resolve and Avid watch-folder presets
Point a preset at the render or export folder: the right file types, a longer stability wait for renders that grow, index files that never leave, and a share link per finished delivery.
- Live
Finder and Explorer
Right-click "Send with Boita" on any file or folder; boita://send links open the drop window from scripts and other apps.
- Live
CLI, SDKs and OpenAPI
The boita CLI for scripts and render pipelines; TypeScript and Python SDKs generated from the OpenAPI description; scoped API keys and signed webhooks. Pro and above.
- Live
WhatsApp
Recipients by WhatsApp number, replies as comments; reminders, receipts and sign-in codes over WhatsApp switch on when the message templates are approved.
- →Coming
Docker, Helm and NAS packages for the agent
Run the headless agent as a container or as a package on the common NAS platforms.
- →Coming
SFTP endpoint
An SFTP front door for systems that can only speak SFTP, landing in the workspace like any other upload. Until then, portals, the CLI and the agent replace the FTP server.
- →Coming
Native GCS and Azure Blob connectors
Import from and auto-deliver to the two other major clouds without an S3-compatible endpoint.
- →Coming
Media asset management connectors
Connectors for the common MAM and archive systems, starting with the ones that offer self-serve trials.
Good to know
Real limits, stated up front.
Taken from the product’s configuration and plan data, not from a sales deck.
Do I need Slack for automations to work?
No. Rules can email, tag and create links without any chat app. Slack and Teams add a channel as a destination and let people make a link from chat.
Can the client receive files in their own cloud drive?
Yes. Choose the drive as the destination when you send, or make it an automation action for a folder; the delivery lands there and the receipt still records it.
We only have an FTP workflow. What replaces it?
Portals for people, the CLI and the agent for machines, and links for outbound. An SFTP endpoint for legacy systems is on the roadmap; until then the agent on the same server usually covers it.
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.
Connect it to where the team already looks.
Chat apps come with Studio; the API, CLI and SDKs with Pro. Start free and connect a webhook first.