Agility - Box Integration and Automation

Common Integration Use Cases Between Agility and Box

1. Secure document repository for CMS-managed content

Data flow: Box to Agility

Marketing and legal teams store approved source files in Box, such as product brochures, policy PDFs, case studies, and compliance documents. Agility pulls selected assets from Box through API-based integration and embeds them into web pages, landing pages, or resource centers. This keeps sensitive files governed in Box while allowing content teams to publish them through Agility without duplicating storage.

• Reduces risk by keeping the system of record in Box
• Ensures only approved assets are exposed on public channels
• Supports faster publishing of regulated content

2. Controlled approval workflow for web content and digital assets

Data flow: Agility to Box and Box to Agility

When a new page, campaign asset, or content update is ready for review in Agility, the content package or supporting files are sent to Box for legal, compliance, or executive approval. Reviewers annotate, approve, or reject the content in Box, and the approval status is returned to Agility to trigger publishing. This creates a governed review process for teams that need formal sign-off before content goes live.

• Improves auditability of content approvals
• Shortens review cycles across distributed teams
• Supports regulated publishing processes

3. Centralized storage for brand and campaign collateral

Data flow: Agility to Box

Agility content editors create campaign pages, landing pages, and microsites, while Box serves as the central repository for supporting collateral such as brand guidelines, creative briefs, campaign decks, and final artwork. Links or metadata references from Agility point to the authoritative Box files, ensuring teams always work from the latest approved version.

• Eliminates duplicate file versions across teams
• Improves consistency of brand and campaign materials
• Makes it easier to manage access for internal and external stakeholders

4. Customer-facing document delivery with secure file governance

Data flow: Box to Agility

Organizations can use Agility to present customer-facing content such as resource libraries, investor relations pages, or partner portals, while Box stores the underlying documents with strict permissions and retention controls. Agility displays only the documents that are approved for public or authenticated access, and Box maintains security, versioning, and compliance controls behind the scenes.

• Supports secure publishing of sensitive documents
• Maintains governance without sacrificing user experience
• Useful for healthcare, financial services, and government portals

5. Automated publishing of approved assets after workflow completion

Data flow: Box to Agility

Once a file in Box completes a workflow in Box Relay, such as legal approval, translation review, or final QA, the integration updates Agility with the approved version and metadata. Agility then publishes the content to the website or app. This is especially useful for time-sensitive campaigns, policy updates, and multilingual content releases.

• Removes manual handoffs between operations and marketing
• Speeds up release of approved content
• Reduces the chance of publishing unapproved materials

6. External partner collaboration for content production

Data flow: Bi-directional

Agility teams can manage content requirements and page structures, while Box is used to share drafts, creative files, and review comments with agencies, freelancers, or legal partners. Final approved assets and copy are then synced back into Agility for publication. This supports distributed content production without exposing the CMS to broad external access.

• Enables secure collaboration with external contributors
• Separates content creation from publishing control
• Improves governance for agency-managed campaigns

7. Compliance archive for published web content and supporting files

Data flow: Agility to Box

Every time Agility publishes a page, campaign, or regulated disclosure, the final version and related source documents are archived in Box for retention and audit purposes. Compliance teams can later retrieve the exact content that was live at a specific point in time, along with supporting approvals and attachments.

• Supports audit and legal hold requirements
• Creates a defensible record of published content
• Helps organizations meet retention policies

8. Content operations dashboard with linked source files and published assets

Data flow: Bi-directional

Agility can display metadata from Box, such as file status, owner, approval stage, or expiration date, alongside content records in the CMS. In return, Box can store references to the live Agility page or campaign where the file is used. This gives marketing, compliance, and operations teams a shared view of what content exists, where it is published, and whether it is still approved.

• Improves visibility across content lifecycle stages
• Helps teams identify stale or expired assets
• Supports governance and content maintenance at scale