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.

​
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.
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

​
Stigg items in the Flow

In the standard Stigg flow, there are three 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.
The following parameters are used across these nodes:
ParameterDescription
Salesforce Account IDThe Salesforce Account ID. Stigg uses this to reference your Salesforce instance.
Stigg Customer IDCustomer ID in the Stigg app.
Customer EmailToggles whether to pass the email address to Stigg (comes from your customer details flow).
Customer NameCustomer name as stored in Stigg.
Plan Base Charge OverrideValue in Salesforce assigned to the plan; overrides the base plan charge in Stigg on the invoice.
Plan IDPlan ID for this customer in Stigg. You can find it in Stigg: Customers → select customer → Subscription details → ID.
Add-onsAdd-ons included in the subscription. Must first be mapped as separate products in Salesforce. View in Stigg: Customers → select customer → Subscription details → Add-ons.
Billing PeriodMust be a billing period that’s supported by the associated Stigg plan, such as monthly or annually. You can find this in Product catalog → Plans → Price.
Payment MethodSpecifies how the subscription will be billed. Supported values include PAYMENT_METHOD_ON_FILE and INVOICE. If set to INVOICE, this corresponds to “Payment method - Generate an invoice to pay manually.”
TrialBoolean flag to enable trial; set to true to activate trial mode.
Trial End DateThe trial end date to assign to the subscription.
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

⌘I