I think the biggest improvement needed for Cisco Crosswork Network Automation is its multi-vendor support, which needs to be more robust. Ingesting telemetry and deploying policies across third-party gear still requires heavy custom API development, so lowering the initial cluster deployment complexity and flattening the learning curve for non-Cisco gear would significantly accelerate time to value. I think the technical documentation for Cisco Crosswork Network Automation is pretty solid, especially for greenfield Cisco environments. However, troubleshooting multi-vendor API issues requires senior Cisco TAC involvement, so if they provide more plug-and-play SDK templates and clear integration patterns for non-Cisco equipment, that would make third-party deployments much smoother.
Consultant En Réseau Sécurité at a comms service provider with 10,001+ employees
Real User
Top 5
Sep 19, 2026
Cisco Crosswork Network Automation needs improved API documentation, an expense integration guide, and code samples to simplify custom script development for DevOps and NetOps teams. I would like to see more templates and an improved user interface, as well as enhancements in network lifecycle automation and real-time streaming telemetry. There are other improvements needed for Cisco Crosswork Network Automation, particularly for the on-premise system.
Network Automation streamlines IT processes by reducing manual interventions, facilitating efficient management, and enhancing network reliability.Network Automation allows organizations to efficiently manage and optimize their infrastructure through automated solutions often preferred by network administrators. These solutions integrate seamlessly with existing environments, allowing scalability while maintaining security. It addresses challenges like reducing human errors, offering faster...
I think the biggest improvement needed for Cisco Crosswork Network Automation is its multi-vendor support, which needs to be more robust. Ingesting telemetry and deploying policies across third-party gear still requires heavy custom API development, so lowering the initial cluster deployment complexity and flattening the learning curve for non-Cisco gear would significantly accelerate time to value. I think the technical documentation for Cisco Crosswork Network Automation is pretty solid, especially for greenfield Cisco environments. However, troubleshooting multi-vendor API issues requires senior Cisco TAC involvement, so if they provide more plug-and-play SDK templates and clear integration patterns for non-Cisco equipment, that would make third-party deployments much smoother.
Cisco Crosswork Network Automation needs improved API documentation, an expense integration guide, and code samples to simplify custom script development for DevOps and NetOps teams. I would like to see more templates and an improved user interface, as well as enhancements in network lifecycle automation and real-time streaming telemetry. There are other improvements needed for Cisco Crosswork Network Automation, particularly for the on-premise system.