Skip to content

Integrations

It fits the tools you already have.

Boita Integrations connects large-file transfer to the tools a team already runs — Slack and Microsoft Teams, Zapier, Make and n8n, cloud drives and object storage, an SFTP endpoint for systems that only speak SFTP, and edit-suite panels — part of Boita, the large-file transfer workspace.

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 Scale 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.

#deliveries · Slack
  • 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

Example thread, as the connector posts it.

How it works

In order

  1. 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.

  2. 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.

  3. 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. Scale 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

    S3-compatible, Google Cloud Storage and Azure Blob buckets, the last two through their own APIs: import a folder, deliver into a bucket, or keep a folder and a bucket in step with a sync rule, on every plan. Auto-delivery to your own S3-compatible bucket or transfer server is Enterprise.

  • 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.

  • Live

    Docker, Helm and NAS packages for the agent

    Run the headless agent as a container or a Helm release, or install it on Synology and QNAP; the Agents page shows every server, container and NAS with a "Sync now" button.

  • Live

    SFTP endpoint

    An SFTP front door for instruments and systems that can only speak SFTP: a per-workspace login (password or SSH key), files landing in the workspace like any other upload, every session audited. Pro and above.

  • →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.

Chat apps
One Slack workspace or Teams tenant per Boita workspace; events chosen per channel.
Webhooks
Signed with HMAC-SHA256, 10-second timeout, retried after 1 min, 5 min, 30 min, 2 h and 12 h.
API keys
Scoped read or read + write, optional expiry, 600 requests a minute per key.
Presets
Deliver from Resolve, Deliver from Avid; more on request. The Linux agent applies the same presets headlessly.

Questions people ask

Boita Integrations, in answers.

Written the way people ask an assistant, and published the same way in products.json and llms.txt. More in the full FAQ.

Who uses this: an instrument or a legacy system that can only push over SFTP; a data pipeline delivering results into a customer’s bucket; an engineering firm posting supplier uploads to a Teams channel; an IT team wiring a workflow platform to create links on a ticket; a firm delivering files into the cloud drive a client already uses; a post house sending renders from the edit suite.

Can an instrument or legacy system that only speaks SFTP send files to Boita?

Yes. Boita is an SFTP endpoint on Pro and above: give the system a per-workspace login with a password or SSH key and its files land straight in the workspace, with every session audited and no server of your own to run.

Does Boita integrate with Slack and Microsoft Teams?

Yes, on Scale and Enterprise. Deliveries, comments, approvals, portal uploads and quarantines post to your channel, links unfurl, and /boita send creates a link from chat.

Can I connect Boita to Zapier, Make or n8n?

Yes. REST hooks on Pro and above expose Boita events and actions to the workflow platforms; the same API and webhooks are available directly.

Can Boita deliver files into a cloud drive or an S3 bucket the client owns?

Yes. Choose a cloud drive as the destination when you send or as an automation action, and connect S3-compatible, Google Cloud Storage or Azure Blob buckets for import, delivery and continuous sync.

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, links for outbound, and Boita itself as an SFTP endpoint (Pro and above) for instruments and legacy systems that can only speak SFTP.

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.

Tell us what you move

Sizes, where it goes, and what is slow today. A person replies with the plan and the setup that fit — no drip sequence.

Or write to hello@boita.io. Your details go to our team only; see the privacy policy.

Connect it to where the team already looks.

Chat apps come with Scale; the API, CLI and SDKs with Pro. Start free and connect a webhook first.

Chat on WhatsApp