The AddPipe Platform is now SOC 2 Type I attested. Read the announcement

Home/Integrations/ Storage/Box

Deliver recordings into Box, where your permissions already live.

AddPipe pushes each processed recording to your Box account over SFTP. The files arrive as ordinary Box content, inheriting the folder permissions, retention policies and audit trail you already run.

Governance you already configured

Recordings land inside Box, so classification labels, retention policies, legal holds and the access audit trail apply to them the same way they apply to every other document.

No new place for people to look

Reviewers open the recording in Box alongside the case file or the candidate record, rather than in a separate system with separate logins.

Diagnosable

Every attempt is written to the SFTP storage logs in your dashboard with the server response, so a permissions problem reads as an error rather than a missing file.

What lands in the folder.

Up to five files per recording, all sharing the recording's name.

name.mp4The processed recording: H.264 and AAC, plays in Box preview without a download.
name_raw.mp4The untouched browser recording, before transcoding.
name.jpgA snapshot for thumbnails and lists.
name_filmstrip.jpgA strip of frames for scrubbing previews.
name_audio.mp4The audio track on its own, for transcription.

Which of the five are produced is set per environment in the Transcoding Engine, so you can deliver only the mp4 if that is all reviewers need to open.

Details.

Why SFTP rather than the Box API?

Box exposes an FTP and SFTP gateway over its normal storage, so AddPipe can deliver into it with the same push mechanism it uses for any SFTP server. The files arrive as ordinary Box content, with your existing folder permissions, retention policies and audit trail applied.

Why does my normal Box password not work?

Box requires a separate external password for FTP and SFTP access, set in your Box account settings. Accounts using single sign-on or two-factor authentication cannot use the account password here, which is the most common reason a first connection attempt fails.

What authentication does AddPipe support?

Password-based only. public-key, host-based, keyboard-interactive and none are not supported.

Does the destination folder have to exist?

Yes. AddPipe writes into the path you give and does not create it, so create the folder in Box first.

Can I use a service account rather than a person's login?

Yes, and you should. Create a Box account for the integration, share the destination folder with it, and set an external password on that account so the connection does not break when someone leaves.

The push failed. Where do I look?

The SFTP storage logs in the dashboard show each attempt and the server response. The usual causes are a missing external password, a destination folder that does not exist, or the integration account not having write permission on it.

Record once, find it in Box.

Pushing to your own storage is included in the 14-day trial. No card required.