Consonance - Asana Integration and Automation

Common Integration Use Cases Between Consonance and Asana

Consonance and Asana complement each other well in publishing operations. Consonance manages the structured publishing lifecycle, title metadata, rights, and production workflows, while Asana provides flexible cross-functional task coordination, timeline visibility, and dependency tracking. Integrating the two helps publishing teams connect editorial and production execution with broader project management across departments.

1. Auto-create Asana projects for new book titles in Consonance

When a new title is approved or moved into active development in Consonance, an Asana project can be created automatically with a standard publishing template. This project can include tasks for editorial review, copyediting, design, proofing, production, and launch preparation.

• Data flow: Consonance to Asana
• Business value: Speeds project setup and ensures every title follows a consistent workflow
• Example: A newly acquired manuscript in Consonance triggers an Asana project with due dates aligned to the publication schedule

2. Synchronize title milestones with Asana timelines and dependencies

Key publishing milestones in Consonance, such as manuscript delivery, editorial sign-off, cover approval, and print release, can be pushed into Asana as timeline milestones and task dependencies. This gives broader teams visibility into publishing deadlines without needing to work directly in Consonance.

• Data flow: Consonance to Asana
• Business value: Improves schedule visibility across editorial, marketing, sales, and operations teams
• Example: When cover approval is completed in Consonance, Asana automatically updates the downstream marketing launch tasks

3. Route cross-functional approvals through Asana while keeping publishing status in Consonance

Publishing teams often need approvals from marketing, sales, legal, and finance that are not native to the editorial workflow. Asana can manage these approval tasks, while Consonance remains the system of record for title status. Once approvals are completed in Asana, the status can be updated back in Consonance.

• Data flow: Bi-directional
• Business value: Separates operational approvals from publishing records while maintaining one source of truth
• Example: Rights clearance or jacket copy approval is completed in Asana, then Consonance is updated to allow the title to move to production

4. Trigger production and asset readiness tasks from Consonance metadata changes

When metadata fields in Consonance change, such as trim size, format, ISBN, or publication date, Asana can generate or update tasks for production and downstream teams. This is especially useful when changes affect cover design, distribution, or digital conversion work.

• Data flow: Consonance to Asana
• Business value: Reduces missed handoffs and ensures dependent teams react quickly to title changes
• Example: A publication date change in Consonance automatically updates Asana tasks for print scheduling, eBook QA, and retailer metadata review

5. Manage marketing launch plans in Asana based on publication readiness in Consonance

As titles approach publication, Consonance can signal readiness milestones that trigger marketing launch plans in Asana. This allows marketing teams to coordinate campaigns, catalog updates, social content, and sales enablement around the confirmed publication date.

• Data flow: Consonance to Asana
• Business value: Aligns launch activities with actual production status and reduces premature campaign execution
• Example: Once final proofs are approved in Consonance, Asana creates a launch checklist for publicity, email campaigns, and retailer asset delivery

6. Escalate overdue publishing tasks from Asana back into Consonance

If critical tasks in Asana are delayed, such as author review, design delivery, or rights confirmation, the issue can be reflected in Consonance to alert publishing managers. This helps editorial and production leaders monitor risks that may affect the publication schedule.

• Data flow: Asana to Consonance
• Business value: Improves exception management and supports proactive schedule recovery
• Example: A delayed cover approval task in Asana updates the title risk status in Consonance so the production manager can intervene

7. Coordinate multi-imprint or series publishing programs across both platforms

For publishers managing multiple imprints or book series, Consonance can track title-level publishing data while Asana manages program-level coordination across teams. This is useful for shared resources, seasonal lists, and coordinated release campaigns.

• Data flow: Bi-directional
• Business value: Supports portfolio-level planning without losing title-specific publishing detail
• Example: A seasonal list in Consonance feeds multiple Asana projects for editorial, production, and marketing workstreams across different imprints

Overall, integrating Consonance and Asana helps publishers connect structured publishing operations with flexible team collaboration. The result is better schedule control, fewer manual updates, clearer ownership, and faster execution across the full book lifecycle.