Box destination

[James Glenister (JamesG419)]

We have an S3 destination, it would be valuable to have Box as a reverse-ETL option

[James Glenister (JamesG419)]

Happy to do this work.

[Airbyte Support Bot (airbyte-support-bot)]

Hi James Glenister (@JamesG419), thank you for submitting this connector request!

A Box destination is an interesting idea — Box has a well-documented API that supports file uploads, folder management, and metadata operations, so this is technically feasible as a destination connector (similar in concept to the existing S3 destination).

How new connectors get prioritized:

• Community demand is a major signal. If others find this valuable, encourage them to 👍 upvote this discussion.
• Airbyte's Connector Builder enables building custom source connectors via a low-code UI. However, destination connectors currently require a more hands-on development approach.
• For custom destinations, you can explore the Destination CDK to build one yourself, or consider using the S3 destination with a downstream workflow to push files to Box.

Possible workaround in the meantime:
Since you already have an S3 destination, one approach is to sync data to S3 and use a Box integration (such as Box Shuttle or a Lambda/workflow trigger) to move files from S3 into Box.

We appreciate your feedback — it helps us understand what the community needs!

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.