extending-action-types

Custom action hooks extend JSON automation workflows by defining new actions using PowerShell scripts in the hooks directory. You create a new PowerShell script, such as download.ps1, to implement specific deterministic actions like file downloads or HTTP requests.

Yes, you can use PowerShell scripts to add custom actions to declarative workflows. By adhering to a specific PowerShell function naming convention and parameter structure, you integrate custom logic directly into your JSON-defined automation steps.

The best way to integrate Git repository initialization into automation is to define a custom action type, such as gitinit. This allows you to handle repository creation and initial file pushes directly within your declarative JSON workflows.

Yes, the automation framework supports sending HTTP requests as custom workflow steps. You can define a custom action type using a PowerShell script to handle HTTP requests, seamlessly integrating external service calls into your JSON workflows.

Custom action types defined with PowerShell are limited to deterministic actions and require strict adherence to a specific function naming convention and parameter structure to integrate correctly with declarative JSON workflows.