Integrations

Connect a Breakdown Takedown organization to Multica, Jira Cloud, or Wrike so teams, tasks, assignments, and comments stay aligned.

Before you connect

• You must be an organization owner. Open Organization Settings → Integrations.
• Enable bi-directional sync, then map each Breakdown Takedown team to the external project, space, or folder that should contain its work. An unmapped team is not synchronized.
• Load the external member directory and map people across systems. Members are not created or copied. An unmapped person stays unassigned on the receiving side.
• New tasks under a mapped team can be excluded individually by turning off “Sync to…” when you create them.

What all integrations synchronize

• Team title and description ↔ external project/container name and description.
• Task title and description ↔ external task/issue title and description.
• Task status, priority, dates, assignee, and parent-task nesting ↔ the provider’s nearest equivalent.
• Task comments, including later edits and deletions, ↔ external comments.
• Task and team deletions are mirrored. Disconnecting stops sync and clears the stored links; it does not describe a data-archive workflow.

Changes made in Breakdown Takedown are pushed immediately on create, edit, or delete. Changes made in the external system are pulled by the scheduled poll and whenever an owner selects “Poll now.” Only mapped containers are read. A newly enabled integration does not automatically push older local tasks; new tasks are linked as they are created, while polling imports or updates external tasks in mapped containers.

Multica

Prepare a Personal Access Token from Multica → Settings → Personal Access Tokens, your workspace slug, and each destination project ID. Add the workspace UUID from Workspace Settings → General if you want to load members for user mapping. The API and web URLs are optional unless you use a self-hosted instance.

• Team ↔ project; task ↔ issue; title, description, priority, start date, due date, assignee, nesting, and comments map directly.
• Statuses todo, in progress, done, and cancelled map directly. Multica backlog maps to To do; in review and blocked map to In progress when pulled.
• Multica members use the user mapping. Multica agents and squads can be selected on synced tasks and remain agent/squad assignments in Multica.

Jira Cloud

Prepare the full HTTPS URL of your Atlassian site, such as https://acme.atlassian.net, and know the project you want to map. Select “Connect with Jira” and approve the requested access. Breakdown Takedown stores and refreshes the OAuth connection; you do not paste an Atlassian API token.

• Team ↔ Jira project; task ↔ Jira issue of type Task; title ↔ summary; description ↔ description; due date ↔ due date; assignee ↔ Atlassian account; comments ↔ comments.
• Start date uses Jira custom field customfield_10015 when present. Jira sites with a different start-date field may not synchronize that value.
• Low, Medium, and High map to Jira priorities of the same names. Jira Lowest maps to Low and Highest maps to High when pulled.
• To do ↔ To Do, In progress ↔ In Progress, Done ↔ Done, and Cancelled ↔ Cancelled. Jira Backlog/Open/New pull as To do; In review/Blocked pull as In progress; Closed/Resolved/Complete pull as Done.
• Jira status changes use available workflow transitions. If the mapped project has no matching transition or Task issue type, Jira may leave the status unchanged or reject creation.

Wrike

Prepare a permanent token from Wrike → Apps & Integrations → API → Personal access tokens. After connecting, choose a Wrike space or folder for each team and map organization users to Wrike members.

• Team ↔ Wrike space; Breakdown Takedown folders ↔ nested Wrike folders; task ↔ Wrike task. Task and folder nesting is preserved.
• Title ↔ title, description ↔ description, priority ↔ importance (Low/Normal/High), assignee ↔ the first Wrike responsible, and comments ↔ comments.
• Wrike dates map to Breakdown Takedown’s optimizer-produced actual start and end dates, not its requested start and calculated end-date fields. Running optimization pushes the new actual dates to Wrike.
• To do and In progress both map to Wrike Active; Done maps to Completed; Cancelled maps to Cancelled. Wrike Deferred pulls as To do.

Claude Code & Model Context Protocol (MCP)

In addition to project management tool integrations, Breakdown Takedown supports the Model Context Protocol (MCP). This allows AI assistants like Claude Code to query elements, update task fields, and create elements directly from the command line. See the Claude Code & MCP section for setup instructions.

Avoiding surprises

• Do not map two teams to the same external container unless you intend them to share one task pool.
• A provider outage never blocks saving local work; the failed change can remain unsynchronized until a later edit or poll succeeds.
• Use the “View in…” link on a synchronized task to confirm which external record it is linked to.