Once a workflow is triggered, you can perform a wide range of actions. Stigg’s Workflow Builder comes with a variety of nodes for actions.

​
Stigg actions

These actions let your workflow interact directly with the Stigg platform to provision resources, manage subscriptions, fetch entitlements, and more. They include: Customer actions
  • Provision a customer
  • Get a customer
Subscription actions
  • Provision a subscription
  • Get a subscription
  • Get active subscriptions
  • Cancel a subscription
  • Update a subscription
Paywall actions
  • Get a paywall
Entitlement actions
  • Revoke a promotional entitlement
  • Grant promotional entitlements
  • Get all of the customer’s entitlements
  • Get entitlement to a feature
Usage actions
  • Get usage history

​
Actions in third-party applications

Use these actions to perform operations inside external services like SendGrid, Salesforce, Slack, and over 400 other integrations. You can create rows, send messages, update records, or trigger actions in your favorite apps — no manual integration required. If none of the available integrations suit your needs, you can also add a generic HTTP request node to make requests to external APIs (GET, POST, PUT, etc.) or run custom code in Python or JavaScript.

​
Data transformations

Transform, clean, filter, or convert data within the workflow itself. You can:
  • Format dates, numbers, or strings
  • Map values or rename fields
  • Convert between types (e.g. string to number)
  • Parse JSON or split text
  • Filter arrays or extract specific properties

​
Sub-workflow execution

As you build more complex automations, you might want to reuse workflow logic or create modular pieces. The Workflow Builder supports sub-workflows (also known as calling one workflow from another). To execute a sub-workflow:
  1. In the reusable workflow - adding an Execution from another workflow trigger.
  2. In the executing workflow - add an “Execute sub-workflow” action node.