Skip to main content

Cyware Orchestrate

Input Node

An input node holds the playbook execution at any point and requests users to provide information such as file paths, passwords, or other configuration details to execute the playbook. You can use the dynamic path to fetch the input passed to an input node and use it in any other node of the playbook. For more information, see Fetch Data from Input Node.

Sample Process

Screenshot_2023-03-03_at_12_00_55_AM.png

Steps

To configure an input node, do the following:

  1. From the Nodes list, under the Input node, drag and drop the Regular node.

  2. Enable Abort Playbook If This Node Fails to terminate the Playbook if the node fails to execute.

  3. In Define Input Parameters, configure the following fields:

    1. Field Title: Enter the field title. For example, Access ID.

    2. Field Identifier: Enter the unique identifier for the input field. For example, access_id.

    3. Field Type: Select the field type of the field identifier from the drop-down. 

      Note

      You can approve or reject playbook execution directly from email notifications. This eliminates the need to sign in to Orchestrate for playbook approvals.

    4. Description: Enter the description of the field title. The description can be the details of the field title or how to retrieve the value of the input.

    5. Mandatory Parameter: Enable this option to mark the input parameter as mandatory.

    6. +Parameter: You can click +Parameter to add additional input parameters

  4. Turn on the Notify Orchestrate users via email toggle to send an email notification to users for entering the input value through email and select user groups and email subject. By default, this field is disabled.

  5. Turn on the Notify Orchestrate users via platform and mobile app toggle and select user groups to notify Orchestrate users for entering the input value through the platform and mobile notifications. By default, this field is disabled.

  6. Turn on the Notify external users when playbook is on hold to inform the external users about the on-hold status of a playbook. By default, the first 20 users will be notified. To increase this limit, contact Cyware Support.

    While triggering a playbook using Open API, analysts can specify a list of external users (email addresses) to be notified when the playbook is on hold status and provide a re-directional link for navigation to take the appropriate action. For more information, see Run Playbook Open API in Orchestrate API Reference.

    If a playbook is triggered from CFTR, the assigned user and user group of the incident receive an email notification about the on-hold status of the playbook and the re-directional link to the CFTR platform to take the appropriate action. For more information on running playbooks from CFTR, see Run Playbooks.

    Notice

    This feature is available from the release version v3.5.0 and later.

  7. In Email/Mobile Notifications, enter the notification message to send to the users.

  8. I Describe This Node, enter a title, and add a brief description of the node. It is recommended to add a relevant description for the node as analysts can use this for their reference, and click Save.