Learn about Stigg's native integration with Salesforce CRM


Stigg's native integration with Salesforce streamlines sales processes by automating fine-grained provisioning of bespoke enterprise accounts directly from Salesforce.


  1. Reduce time from opportunity close to account provisioned from days and hours to 0.
  2. Ensure alignment between the customer's contract and the level of access that they were provisioned.
  3. Leverage the same entitlement management and metering infrastructure for access enforcement and usage reporting regardless of how your product is sold - via self-service, sales-led, sales-assisted, or all of the above.

Example use-cases

  1. Provisioning trial access when an opportunity reaches a POC status.
  2. Provisioning subscriptions upon opportunity close.
  3. Updating customers' entitlements upon contract amendment and renewals.


The integration can be fully customized to your existing business process and needs by leveraging Salesforce Flow workflows.

Integration with Salesforce CPQ

Stigg's native integration with Salesforce works seamlessly with Salesforce CPQ.

Setting up the integration


  • A Salesforce organization with Enterprise edition or higher
  • A user with admin access to the Salesforce organization, that you'll be integrating with Stigg

Connect your Salesforce domain

In the Stigg app, navigate to the Integrations section and click on the Salesforce tile.

Enter the domain of the Salesforce instance that will be integrated with Stigg.

Click "Continue".

Install the Stigg app

Install the Stigg app for Salesforce using this link.

Click on "Install for Admins Only".

Configure the Stigg app

Configure API key

In the Stigg app, copy the generated API key.

In Salesforce, open the App Launcher.

Search for "Stigg".

Open the Stigg app and select the "Stigg Configuration" tab.

Enter the integration API key that you copied from the Stigg app, and save the settings.

Map Salesforce and Stigg entities

Provisioning entities in Stigg according to entities in Salesforce requires mapping between these two entities to be defined. This mapping is defined in Salesforce.

In Salesforce, under the relevant Salesforce entity that you'd like to map to Stigg:

  1. Stigg type - an enum with following possible values:
    1. "Plan" - represents a custom plan in Stigg
    2. "Add-on" - represents an add-on Stigg
    3. "Entitlement" - represents plan's a custom entitlement
  2. Stigg ID - the ID of the matching entity in Stigg, for example: plans would start with a "plan-" prefix, add-ons start with an "addon-" prefix, and entitlements start with a "feature-" prefix

Add these new custom fields to the entity's default page layout.

If you're using Salesforce price books, Salesforce products or Salesforce CPQ, it's high recommended to add these custom fields to the Salesforce product entity, as can seen below:

When creating or editing the relevant Salesforce entities that are mapped to Stigg entities, set the values of these custom fields:

Create provisioning automation flows

In Salesforce click on the "Setup" icon and open the "Setup" action.

In the search box that appears at the top of the page, enter "flows".

Select the "Flows" item under "Process Automation".

Default template

To help you get up-and-running, the Stigg app for Salesforce includes a default Salesforce Flow template for automating provisioning of customers and subscriptions in Stigg when an opportunity in Salesforce is marked as "Closed - Won".

This template can be fully customized to cater to your business needs.

In the opened list, search for a flow called "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

Default template flow in Salesforce

Creating your own flow

Leverage the default template flow to create flows that meet your business needs.

To do so, apply the relevant changes to the default template flow.

Specifically, provision resources (i.e. accounts, organizations, workspaces) in your application before provisioning the resources in Stigg (between steps 2 and 3 of the default template) by adding a new HTTP callout action which will make an API request to your application to provision those resources.

Update the "Create Stigg Customer" and "Create Stigg Subscription" actions to use IDs of the generated resources when creating customers and subscriptions in Stigg.

One done, click on the "Save as" link to create a new flow with your changes.

Ensure that the default flow is deactivated and that the new flow is active.


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:

Customer in Stigg has a Link to the Account in Salesforce

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

Account in Salesforce has a link to the customer in Stigg

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

Removing the integration

To remove the integration, click on the dotted menu icon and select the "Remove" action.

Confirm the action by clicking on the "Remove" button in the opened modal.