Action-based extensibility uses streamlined scripts of code within Automation Assembler to automate extensibility actions.

Action-based extensibility provides a lightweight and flexible run-time engine interface where you can define small scriptable actions and configure them to initiate when events specified in extensibility subscriptions occur.

You can create these extensibility action scripts of code within Automation Assembler, or on your local environment, and assign them to subscriptions. Extensibility action scripts are used for more lightweight and simple automation of tasks and steps. For more information on integrating Automation Assembler with a Automation Orchestrator server, see Configure an Automation Orchestrator integration in Automation Assembler.

Action-based extensibility provides:

  • An alternative to Automation Orchestrator workflows, using small and reusable scriptable actions, for lightweight integrations and customizations.
  • A way to reuse action templates, which contain reusable parameterized actions.
You can create extensibility actions by either writing a user-defined action script code or importing a predefined script code as a .ZIP package. Action-based extensibility supports Node.js, Python, and PowerShell run-time environments. The Node.js and Python run-times rely on Amazon Web Services Lambda. Therefore, you must have an active subscription with Amazon Web Services Identity and Access Management (IAM), and configure Amazon Web Services as an endpoint in Automation Assembler. For information on getting started with Amazon Web Services Lambda, see ABX: Serverless Extensibility of Cloud Assembly Services.
Note: Extensibility actions are project-specific.