Skip to content
Business productivity ⇄ Storage

Atlassian to Box integration — real-time, two-way sync

Keep Atlassian and Box in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Atlassian and Box

Land the records and documents that build up in Atlassian into Box as they are created, and surface Box's file details on the Atlassian records that point to them, without an export job to maintain.

Atlassian and Box hold different kinds of data. Atlassian carries records and the activity around them — the tickets, messages, orders, or issues a team works through, often with documents attached. Box holds files and the metadata that describes them. Where the two meet is narrow but real: much of what Atlassian produces has to be kept somewhere durable, and many of the files Box stores are the very documents Atlassian's records point to.

Stacksync syncs Confluence Spaces, Jira Issues, Jira Projects, Boards and Sprints in Atlassian with Events, Files, Folders, Metadata in Box in real time. Records and attachments created in Atlassian are written into Box as objects or files within seconds of being created. In the other direction, the metadata Box keeps about those files — name, location, owner, modified date — flows back onto the matching record in Atlassian, so people see the current document without leaving the tool. Field-level mapping controls exactly what crosses over and in which direction, so you keep a durable copy of what matters without an extract to schedule or a nightly dump that leaves the copy a day behind.

Common use cases

  • 01 Create Jira issues from records in other systems, such as onboarding tasks generated from a closed-won CRM deal.
  • 02 Keep Jira and a second tracker (for example a customer's Jira instance) aligned during co-delivery projects.
  • 03 Stream enterprise Events (admin events) into a warehouse for audit, DLP, and access-review reporting.
  • 04 Two-way sync of Files and Folders between Box and an operational database so applications track document status without calling the Box API directly.

Common sync patterns

A copy that outlives the tool

A continuously synced copy in Box preserves records and documents even as they age out of Atlassian or get changed inside it, so history stays intact and reachable.

Feed a data lake or downstream pipeline

Structured records from Atlassian land in Box as objects a data lake, search index, or processing pipeline can read, without a custom extract to build and babysit.

Archive what Atlassian produces into Box

Records and events from Atlassian — tickets, messages, orders, or issues — are written into Box as objects or files as they change, giving you a durable, addressable copy for retention and audit.

What you can sync between Atlassian and Box

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Atlassian objects Box objects How this pairing syncs
Jira Projects Containers that scope issues, workflows, and permissions for a sync. Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. Jira Projects is specific to Atlassian and Groups to Box — each maps to any object or custom field on the other side.
Boards and Sprints Agile structures read to report on sprint contents and status. Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. Boards and Sprints is specific to Atlassian and Tasks to Box — each maps to any object or custom field on the other side.
Issue Comments Threaded discussion synced into linked tickets in external systems. Events Enterprise admin event stream, an audit log of uploads, deletes, logins, and shares across the account; read-only, consumed for reporting or change feeds. Issue Comments is specific to Atlassian and Events to Box — each maps to any object or custom field on the other side.
Attachments Files on issues mirrored to paired records where needed. Files Core content object with versions, name, size, and metadata; synced two-way so files and their attributes move between Box and a database or another store. Attachments is specific to Atlassian and Files to Box — each maps to any object or custom field on the other side.
Custom Fields Instance-specific fields (customfield IDs) that carry most business-specific data in syncs. Folders Hierarchical containers whose tree, names, and parent moves are mirrored so a target system reflects Box's structure; the account root is always folder ID 0. Custom Fields is specific to Atlassian and Folders to Box — each maps to any object or custom field on the other side.
Workflows and Statuses Status transitions mapped to stages in the paired system. Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. Workflows and Statuses is specific to Atlassian and Metadata to Box — each maps to any object or custom field on the other side.

How changes propagate between Atlassian and Box

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Atlassian Box Sub-second propagation

DetectionAtlassian notifies Stacksync of record changes through webhook events. Webhooks on issue and page events, plus JQL polling on the updated timestamp for backfill.

DeliveryEach detected change is written to Box through its API, with automatic retries and rate-limit backoff.

Box Atlassian Sub-second propagation

DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.

DeliveryEach detected change is written to Atlassian through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
What ships with Atlassian ⇄ Box

Connect Atlassian and Box for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Atlassian–Box connection.

Real-time

Two-way sync

Changes in Atlassian or Box instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Atlassian or Box data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Atlassian or Box record.

Observability

Monitoring

Track your Atlassian ⇄ Box sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Atlassian and Box.

How the Atlassian and Box connectors work

Atlassian

Integration surface
REST APIs per product (Jira Cloud and Confluence Cloud)
Authentication
OAuth 2.0 (3LO) for apps or API tokens with basic auth for scripts
Change detection
Webhooks on issue and page events, plus JQL polling on the updated timestamp for backfill
Capabilities
read · write · webhooks

Box

Integration surface
REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
Authentication
OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
Change detection
V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
Capabilities
read · write · webhooks
Rate limits
Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
How it works

How to connect Atlassian to Box — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Atlassian and Box with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Atlassian connected
    Box connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Atlassian and Box objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Atlassian ⇄ Box
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Atlassian Box
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Atlassian and Box integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 435 integrations available for Atlassian and Box.

Popular · 7 of 435
All Atlassian integrations All Box integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own