Creating your Own Salesforce App

Out of the box, Fusebit's Salesforce Integration uses our own demonstration application. This is to make it easier to get started, however you will likely need to register your own Salesforce App for use in production in case:

  • The Salesforce method you are executing via the SDK requires more advanced permissions
  • You want to receive inbound messages via Fusebit's Salesforce Webhook infra
  • You want to deploy your Integration in production and you want end-users to see your own branding instead of Fusebit branding


Salesforce Developer Account

Salesforce recommends that you use a developer account to create an app, this also enables you to test your integration against different license types and will be required to create & distribute Managed Packages (if you choose to) later on.

If you don't have one already, you can sign up for it here

To create your own Salesforce App:

  1. From your Salesforce homepage, click on the Settings icon in the top right, and select 'Setup'

  1. In the sidebar, navigate to Apps > App Manager

  1. Click on 'New Connected App'

Salesforce has two types of apps you can create, Connected Apps and Lightning Apps. If your app sits outside of Salesforce UI and is consuming the API only, then you will want to create a 'Connected App'.

  1. After filling out the Basic Information, you must click on 'Enable OAuth Settings' and also make sure the following items are selected:
  • Use digital signatures
  • Requires Secret for Web Flow
  • Require Secret for Refresh Token Flow

Additionally, you will want to define the App Scopes that you want to enable. Be sure to select the Perform requests at any time scope, even if Full access is already selected.

  1. Back in the portal, find the Integration you would like to connect to the new Salesforce App you just created. Select the Connector tied to that integration.

  1. Select Enable Production Credentials in the Connector Configuration and list the OAuth Scopes you specified in the Space separated scopes to request from the OAuth server field. To use the example provided later in this guide, specify the following scopes: api refresh_token offline_access.

Additionally, while you're here copy the 'OAuth2 Redirect URL'. You will need to paste this into the Salesforce App.


When switching a Connector to a different Salesforce App, all Identity objects associated with that Connector will be deleted. Your users will need to re-authenticate against Salesforce after you make the change.

  1. Back in your Salesforce App and paste the 'OAuth2 Redirect URL' into the 'Callback URL' box and hit save.

  1. After you hit save, you will be taken to the Manage App screen for the app you just created. Copy the 'Consumer Key' and 'Consumer Secret', you will need to configure these in the connector in the Fusebit Management Portal.

  1. Back in the portal, paste the 'Consumer Key' in the 'Client ID' field, and the 'Consumer Secret' field in the 'Client Secret' field.


Good Job!

Now, any time a new user installs your Integration, you should now see your Salesforce App information displayed during the authorization step.

What’s Next