process studio - workflows - automation node management

  • Updated

Overview

An Automation node is a workflow step that executes a predefined automation within Neostella. The Automation node supports the inclusion of actions that do not require user intervention. It helps streamline processes and improve efficiency, especially in workflows that combine automated actions with manual tasks.

During execution, the system runs the nested automation. The execution waits for this automation to finish successfully before following the outbound path. This means the node acts as a blocking step.

 

Prerequisites & Dependencies

  • An existing Workflow template must be created.
  • At least one Published Automation must exist in Neostella.
  • The trigger type of the Published Automation must be set to nested automation for workflows.

 

Required Permissions

  • Admin permissions with Workflow configuration access.

 

Configuration Steps

  1. Open the Workflow Template editor for the desired workflow.
  2. Drag and drop the Automation node onto the canvas.
  3. Select a Published Automation with Nested Automation trigger type from the Select an automation dropdown.
  4. Enter a value in the Custom Name field. The name must be unique among all nested automations within the template.
  5. Click NEST AUTOMATION.

 

Validation and Expected Results

When an execution reaches the Automation node, the selected automation runs. This execution remains paused until the automation completes successfully.

Executions can be monitored from the global list located at Control Center -> Process Studio -> Workflows -> Running tab or within the contextual Workflows view of a specific Project or Lead record.

 

Common Issues

  • Problem: The desired automation does not appear in the Select an automation dropdown.

    Cause: The automation is not published or the trigger type is not configured as a nested automation for workflows.

    Resolution: Verify the configuration of the automation in the platform. Ensure the automation is published and the correct trigger type is assigned.

     

  • Problem: The execution is stalled at the Automation node.

    Cause: The nested automation returned a failed status.

    Resolution: The system retries the automation up to four times. If the automation still does not succeed, the execution remains blocked at that point. Review the nested automation configuration to resolve the underlying failure.