Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.colossal.sh/llms.txt

Use this file to discover all available pages before exploring further.

An app action step runs an operation from any installed app. This includes built-in Colossal actions (email, HTTP, cart operations) and third-party app actions (Stripe charges, Klaviyo events, Slack messages).

​
Configuration

FieldTypeDescription
actionstringAction identifier. Built-in actions use colossal/actionName, third-party apps use app-id/actionName.
parametersobjectKey-value pairs passed to the action. Supports data access variables.

​
Example

{
  "id": "send-confirmation",
  "type": "action",
  "action": "colossal/send_email",
  "parameters": {
    "to": "{{payload.customer_email}}",
    "subject": "Order confirmed",
    "body": "Your order {{payload.order_uid}} has been confirmed."
  },
  "next": "next-step-id"
}

​
Available actions

The Colossal app provides built-in actions for cart, checkout, customer, product, orders, inventory, invoices, email, payments, and HTTP. These use the colossal/ prefix. Third-party apps add their own actions when installed, using the format app-id/action-name (e.g. stripe/create_payment_intent, klaviyo/track_event). See Colossal app actions for the full built-in list and Apps for third-party apps.