Workflows Licensing
When you use Automation content that was not authored by your organization, such as workflows and atomic actions, it is important to be mindful of and comply with the applicable license for that content. This page explains some of the license sources you are likely to see depending on where you obtain your content, and what your responsibilities are as a user of the platform.
Use of the Cisco Workflows platform is governed by the Cisco Customer Contract, unless you have a different applicable signed agreement with Cisco. Effective February 5, 2024, Cisco's End User License Agreement(EULA) has been replaced with Cisco's General Terms. When publishing to the Exchange, adhere to the licensing as mentioned in the table below. Be aware that after you submit a workflow for review, you may be contacted by the reviewer with questions or feedback about your request.
However, pre-built workflows and atomic actions you use in Cisco Workflows could be governed by different license agreements. You are responsible for checking the source of what you import and install in Cisco Workflows and reviewing the applicable agreement. Below are a few of the common sources and licenses that may govern workflows and atomic actions for Automation:
Warning: Regardless of which agreement applies, it is very important that you test your workflows and atomic actions carefully in a test environment before using them in a production environment.
Licensing Details
The following table provides some examples of sources for Automation workflows and atomics. If applicable, we recommend you go to the source repository to review licensing details when in doubt.
|
Content Source |
Applicable License |
Support |
|---|---|---|
|
Content authored by Cisco:
|
MIT License (see below) |
Supported by Cisco TAC |
|
Workflows in Cisco Automation Exchange, authored by a Cisco Technology Partner (Cisco Verified) |
MIT License (see below) |
Supported by the Cisco Technology Partner |
|
Workflows in Cisco Automation Exchange, authored by the Community (Community) |
MIT License (see below) |
Supported by the Cisco DevNet Community on a best-effort basis. |
|
Third-party repositories |
When you obtain content from third-parties not listed above, it is your responsibility to know how the content is licensed. Typically, the license is available in the provider’s repository. If not, you should ask the provider for the license. |
Dependent on third-party |
MIT License
All workflows, atomic actions, and other associated files that are available from within Cisco Workflows or GitHub repositories owned by Cisco are subject to the following license:
MIT License
Copyright (c) 2025 Cisco Systems, Inc.
Third party content Copyright (c) 2025 each respective third party
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.