In this article, we'll explain how to set up your Marketplace and how to configure a sign-in method for your Marketplace.
Creating an Integration Marketplace
Go to Integry's Homepage and click on Deployments, as seen below.
Your app's deployment in Integry represents how your Flows are visible to your end-users. There are two deployment options available in Integry.
- The Marketplace Deployment lets you deploy your Flows on your app's Integration Marketplace.
- The SDK Deployment lets you deploy Flows on an SDK that will be embedded inside your app.
Click on 'Create Marketplace Deployment.'
Adding Basic Information
We'll start with adding the basic information of your app. The information you give here will be used to populate the appearance and default text of your Marketplace.
Add the following information. These fields will be pre-filled based on your workspace app, however, you can edit them as well.
- Homepage URL: Insert the link to your app's homepage in this field.
- Marketplace URL: Your end-users will use this URL to reach your Marketplace. By default, a free subdomain under .integry.io is given to you, but you can also use a custom URL based on your domain.
- Custom Flows: Turn this toggle on to enable your end-users to create their Custom Flows on your Marketplace.
- Logo Navigation URL: Add a URL of the source where you want to redirect your end-user when they click on your app's logo in the marketplace header.
- Google Analytics Tracking ID: Add your Google Analytics ID here for Integry to send visitor traffic information of your Marketplace to your Google Analytics account.
Sign-in for End-User
There are three sign-in options that you can enable on your Marketplace for your end-users. We'll discuss each of them below.
This option is auto-selected if you haven't configured any authorization methods for your App Connectors.
If this option is selected in your Marketplace deployment settings, and your end-user visits your Marketplace, they won't see a Sign-in option, shown above. Your end-users can set up integrations with the Flows on your Marketplace.
However, these integrations will be disabled and they won't be able to activate them.
This option could be helpful if you want your beta testers to view how the Flows work in your Marketplace so they can test integrations before you make them live for your end-users.
This is the least recommended option and is only suitable for demonstrating Flows and testing purposes.
2. Connector Auth
If your connector supports authorization methods other than API Key, e.g., OAuth2, JWT, Basic auth, etc., you can choose this option. This will enable your end-users to log into your Marketplace via your Connector's authorization method.
The list of connectors for which you've configured an authorization method will be displayed in a dropdown menu. You can choose a connector from the list.
After this setting, your end-user can see the option to sign-in upon visiting your Marketplace. When your end-user would try to sign in, they'll be asked to sign-in via the authorization method you have configured for your connector. For example, we selected Slack for authorization, shown above.
Slack's connector has OAuth2 authorization type configured, therefore, we were shown the OAuth2 authorization interface, shown above.
If you've configured multiple authorization methods for your connector, your end-users will be asked to choose an authentication method while signing in.
After signing-in, your end-user will be able to create integrations and view the integrations they've created.
Let's assume, your end-user has signed into your Marketplace with their Slack account. If Slack is a part of the Flow the end-user is setting up an integration with, they will not be asked to add their Slack account at integration setup.
In the above example, we are setting up an integration with a Flow, "When a message is posted in a Slack channel, create a task in Doneday." We're signed-into the Marketplace using our Slack account. You can see that while creating an integration, we were able to configure Slack without connecting our account first.
How to Enable Connector Auth Support?
If you haven't configured an authorization method for your connector, you'll see the message, "Your connector doesn't have auth support. Click learn more to see how to add it."
You'll see the same message if you have configured an authorization method for your connector but haven't enabled auth support yet.
The User Information Endpoint is created in Integry when you set up an authorization for your app connector. To enable the auth support for your connector, you have to configure the User Information Endpoint in your authorization.
To enable connector auth support, open your app in connector builder v3. Select the authorization to edit it.
Here, you can find the field where you can select the user information endpoint.
Note: Integry sends an API request to the User Information Endpoint and expects to receive a unique identity of your end-user. Therefore, before saving your configuration, make sure the response received from the user information endpoint returns a unique identity for every user.
Currently, Integry's SSO only supports API Key type authorization method. So, you can set up SSO for your Marketplace if your app connector supports API Key type authorization method.
Add a link to your app's login page here. This is where your end-users will be redirected to once they click on 'sign in' on the Integration Marketplace homepage. You can append a query parameter like source=appdir to your Login URL. This will enable you to know where the login request is originating from. Learn how the authentication works if you implement SSO to your Integration Marketplace.
Note: If you haven't configured a sign-in option, you can change it to Connector Auth or SSO. However, once you've chosen a sign-in option for your Marketplace and your end-users have created integrations using their authorization details, you will not be allowed to change the sign-in option. If you do, your end-users will lose access to their integrations. However, if the integrations created by your end-users are no longer needed, you can disable them from your Flow's Integration View. If no integrations are enabled in your Marketplace, only then can you change the sign-in option for your end-users.
After setting up your Marketplace, you can click on the preview link to see how your Marketplace would look like for your end-users.