Marketplace Apps: Managing External Connections in Sparkforge
Sparkforge marketplace apps connect to third-party tools at the sub-account level using OAuth, API keys, or Basic Auth. Single installs prompt for the connection immediately; bulk installs require each sub-account user to connect from their own marketplace.
Marketplace apps let Sparkforge talk to third-party tools. Every app needs a connection to the external service before data flows. Here is how those connections are scoped, when they are prompted, and which authentication methods are supported.
How connections are scoped
- Connections are made at the sub-account level. Each sub-account holds its own credentials with the third-party app — connecting once at the agency level does not propagate downstream.
- If you install an app into a single sub-account and that app needs an external connection, the connection prompt opens right after install completes.
- If you bulk-install an app across many sub-accounts, the connection prompt does not open automatically. Each sub-account user must open their marketplace and connect the app themselves before it works.
Supported authentication methods
Sparkforge marketplace apps use one of three authentication methods, set by the app's developer:
- OAuth — log in to the third-party app and authorize Sparkforge. Tokens refresh automatically.
- API Keys — copy the API key from the third-party app and paste it into Sparkforge.
- Basic Auth — provide the username and password for the third-party account.
If a connection breaks (revoked token, rotated key, changed password), reconnect from the same sub-account marketplace where the app was installed.
Frequently Asked Questions
Can I connect a marketplace app once and use it across all sub-accounts?
Why didn't my bulk-installed app prompt me to connect it?
Which authentication method should I use?
What happens if my connection breaks?
Was this article helpful?
Thanks for the feedback.