Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.box.com/llms.txt

Use this file to discover all available pages before exploring further.

Box Automate availability depends on your Box plan and how your organization enables the product. Work with your Box admin or account team before building integrations against production content.
Box Automate is a workflow automation platform built natively on the Box content platform. You can use it to design, build, and run automated workflows with a visual builder that supports conditional branching, loops, and a broad set of triggers and actions. This overview summarizes what the platform can do, how developers can integrate with it, and which Box Platform APIs and scopes you are to use alongside workflows.

​
Capabilities

  • Triggers — File, folder, task, File Request, Box Sign, metadata triggers, Forms submissions manual, webhook events can start workflows.
  • Outcomes — File and folder outcomes, collaborations, task assignments, Workflows can assign tasks, send notifications, AI outcomes, Integrations, and metadata.
  • Logic — Branching, variables, JSONPath, and structured AI output help route work and pass data between steps.
  • AI — Custom agents can use knowledge sources, citations, and reasoning traces where those features are enabled for your enterprise.
  • Third-party APIs — The OpenAPI Connector Engine builds steps from OpenAPI 2/3 specs (import by URL or file), with domain allowlisting and auth from the spec. Custom HTTP (phase 1) covers arbitrary REST calls with manual configuration when no spec is used.
  • Extensibility — Box Functions ties custom logic to a developer application so advanced integrations and scripts can plug into orchestration where the product supports it.

​
Use cases

Box Automate fits document-centric processes that combine content, people, and policy. Common examples include:
  • Approvals and reviews — Route files for review, capture outcomes, and notify stakeholders.
  • Case and project folders — React to uploads or metadata changes and kick off the next step automatically.
  • AI-assisted triage — Classify or summarize incoming content, then branch on the result.
  • Cross-product flows — Combine uploads (for example, File Request), metadata, Doc Gen, or Sign in one automation.

​
Developer integrations

Automations run on Box content. Most integrations use a , standard OAuth or JWT auth, and a mix of workflow APIs plus the content and collaboration endpoints. Start with ,

​
Rate limits

Workflow and content API calls are subject to Box Platform rate limits. See the for details.