Skip to main content

​
Create provisioning automation flows

1

Open Salesforce Setup

In Salesforce, click the Setup gear icon in the top-right corner and select Setup from the dropdown.
2

Search for Flows

In the Quick Find search box at the top of the left sidebar, type "flows".
  • Under the Process Automation section, select Flows.
Before using the default provisioning automation (including the CPQ flow), make sure your Salesforce org has at least one product with Stigg Type = Plan.Provisioning can’t run on entitlements alone. Even if you mark a CPQ product as entitlements, the flow still needs a Plan to:
  • Recognize which Opportunity Products map to a Stigg plan
  • Build a complete provisioning payload when an Opportunity is marked Closed Won
  • Create / attach the subscription in Stigg with a valid plan ID
If no Plan-type product exists on the Opportunity, the subscription input step will produce an empty plan ID, and the Stigg Subscription node will fail or skip execution.

​
Default template

1

Use the default Salesforce Flow template

To help you get started quickly, the Stigg app for Salesforce includes a default Salesforce Flow template.
  • This flow automates the provisioning of customers and subscriptions in Stigg when a Salesforce opportunity is marked as Closed - Won.
  • The template is fully customizable to fit your specific business logic.
The default template uses an Opportunity as its trigger, but the Stigg flow actions (Create Stigg Customer, Create Stigg Subscription, Create Stigg Credit Grant) are standard Salesforce Flow actions and can be embedded in any flow. You can trigger provisioning from any Salesforce entity — Accounts, Contacts, Cases, custom objects, or any other object — simply by building a flow that starts from that object and includes the relevant Stigg actions.
2

Locate the template flow

In the list of flows, search for:
Opportunity - Stigg Subscription Template
The default template flow does the following:
  1. Triggered when the status of Opportunity in Salesforce changes to Closed won.
  2. Iterates over the opportunity’s products and compiles the input for provisioning subscriptions in Stigg using the defined entity mapping.
  3. Provisions a customer in Stigg.
  4. Provisions a subscription in Stigg.
  5. Updates the opportunity’s account with the Stigg Customer ID and Stigg Customer URL. The latter serves as a deep-link to the relevant customer in Stigg.

Default template flow in Salesforce

Error handling: Use the Flow’s built-in fault path to handle failures gracefully. When a Stigg API call fails, the fault connector lets you log the error, send a notification, or retry the provisioning request - without silently dropping it.

​
Stigg items in the Flow

In the standard Stigg flow, there are four Stigg nodes:
  • Create Stigg Customer without email: used when the customer Contact does not have an email address assigned in Salesforce.
  • Create Stigg Customer with email: used when the customer Contact has an email address assigned in Salesforce.
  • Create Stigg Subscription: creates a subscription in Stigg.
  • Create Stigg Credit Grant: grants credits to a customer in Stigg.

​
Create Stigg Subscription parameters

​
Create Stigg Credit Grant parameters

When customer and subscriptions are created in Stigg through the Salesforce integration, in both places you will see a deep link to the matching entity in the other system, so it’s easier to navigate and find the corresponding entity in the other system:

Customers in the Stigg app have a deep-link to the Account object in Salesforce

Accounts in Salesforce have a deep-link to the Customer object in the Stigg app