Publish components

4 min

Publish Components

To publish a component to the User ContentUser Content library:

Steps:

You can publish a component by selecting Publish from the ellipsis icon of Components screen or navigate to the desired playbook.
Open the component settings menu and select Publish
In the Publish Content window:
- Select Publish as New Content (V1).
- Provide a name and description for the content.
- Click Next.
Select Content to Publish:
- All the playbook components are listed.
- Click Next.
Review Content:
- Review the selected content and check for potential issues.
- If everything looks good, click Next.
Summary:
- Confirm the details: version (1.0.0), content name, description, and publish message.
- Click Publish.
Success:
- A success message confirms that the component has been published as new content.
- The new content is now available in the content library.

This scenario applies when you need to update an already published component package.

Steps:

Follow steps 1–3 as in the Publish as New Content process.
In the Publish Content window:
- Select Publish as a new version of existing content (V1+).
- From the list, choose the package you want to update.
- Click Next.
Review Changes:
- Review the selected content and check for issues.
- Click Next.
Summary:
- Confirm the new version (for example, 3.0.0 -> 4.0.0).
- Provide a detailed publish message (what was changed and why).
- Click Publish.
Merge Conflicts (if applicable):
- If conflicts are detected between the local changes and the remote repository, a Merge Conflicts screen appears.
- You have two options:
  - Keep Library Changes (retains local changes).
  - Keep Remote Changes (keeps remote repository changes).
- Click Apply to resolve conflicts.
Success: The updated content is now published, and a confirmation message appears.

You can navigate to the User Content library to verify the playbook published.

Component nesting is limited to 10: You can configure assets and settings, but you cannot remove actions within a nested component.
Task deletion: If you want to delete tasks within a component, duplicate the component as a user-made one and modify it as needed.
Ungrouping components: Ungrouping only affects the current flow; it does not delete the component from the library.
Cross-workflow limitation: You cannot create a component that spans across multiple workflows.
Branching limitation: Parallel actions and conditions must be within the same branch.