Prerequisites
- 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
1
Open the Salesforce integration in Stigg
In the Stigg app, go to the Integrations section and click on the Salesforce tile.
2
Enter your Salesforce domain
Enter the domain of the Salesforce instance you want to integrate with Stigg.
3
Continue with the setup
Click Continue to proceed with the integration flow.
Install the Stigg app
1
Open the installation link
Click on the Stigg app for Salesforce installation link:

2
Install the app
In the Salesforce installation screen, select Install for Admins Only.

Configure API key
1
Copy your API key from Stigg
In the Stigg app, copy the generated Integration API key.
2
Open the Stigg app in Salesforce
Go to Salesforce and open the App Launcher.
- Search for “Stigg”
-
Select the Stigg app from the results
3
Configure the integration key
In the Stigg app, go to the Stigg Configuration tab.
- Paste the API key you copied from the Stigg app
-
Click Save to apply the configuration
Map Salesforce and Stigg entities
1
Understand the purpose of entity mapping
Provisioning entities in Stigg based on Salesforce data requires a mapping between the two systems.
This mapping is defined within Salesforce using custom fields that connect Salesforce entities (like Products) to their counterparts in Stigg.
This mapping is defined within Salesforce using custom fields that connect Salesforce entities (like Products) to their counterparts in Stigg.
2
Add Stigg mapping fields in Salesforce
In Salesforce, go to the entity type you want to map to Stigg (e.g., Product).
Add the following custom fields:
Add the following custom fields:
- Stigg Type (Picklist/Enum):
Indicates what kind of Stigg entity this is. Supported values:"Plan"
– maps to a custom plan in Stigg"Add-on"
– maps to an add-on in Stigg"Entitlement"
– maps to a custom entitlement in Stigg
- Stigg ID (Text):
The unique identifier of the matching entity in Stigg- Example prefixes:
plan-
for plansaddon-
for add-onsfeature-
for entitlements
- Example prefixes:
3
Add the fields to the page layout
To make the new custom fields editable in the UI:
- Add them to the entity’s default page layout
💡 If you’re using Salesforce price books, products, or CPQ, it’s highly recommended to add the fields to the Product entity, as shown below:

4
Set field values when creating or editing entities
When creating or editing the relevant Salesforce entities:
- Set the Stigg Type to match the type of entity in Stigg
-
Enter the corresponding Stigg ID from your Stigg app