The App Directory is a public listing of all apps that your users can create integrations with. This app listing is hosted by Integry. Instead of embedding the SDK inside your app and populating it with integrations, Integry hosts your integrations on a subdomain of your choosing, such as apps.mycompany.com or mycompany.integry.io. The domain type that you choose depends on your pricing tier.

This feature is for customers that prefer a quicker method of delivering integrations to their users. By using App Directory, you can avoid the SDK embedding step in the integrations rollout. This will take away the native integrations element, but your integrations will become up and running for your users faster, with less effort. You can also have both versions of app listings: App Directory and in-app SDK as well.

Shown below is an example of a basic app directory with Integry’s subdomain and branding. This is how your App Directory cards will appear to your users:

External App Cards

On your App Directory page, your users will see Cards that are available for them to set up. These will consist of the integration templates and external apps. However, the Cards for external apps will only act as placeholders. Clicking on these will redirect the user to an external link. This is so that you can direct your users to your integrations hosted on other platforms as well.

In addition to just creating apps that act as workspaces, you can also create external apps under the Apps menu in your dashboard. An external app is like a regular App, but with only the basic info, product page info, and an action URL. More information on app cards and how to create them can be found here.

For example, you can add an external app card and name it Shopify which links to setting up that integration on an external platform like Zapier. When a user goes to your App Directory, they will see this card which will appear just like a template card. Clicking on the install button for this app will take the user to the action URL that you provided for that card. In this case, it would be setting up this integration on Zapier. Clicking on the external app card instead of the install button will open the product page for that app, that will contain its distribution details like app description, categories, social media links, etc.

Setting up your App Directory

To create your own app directory, you will need to create a Deployment. A deployment is an ordered collection of your app cards and templates. This collection will be populated on your App Directory URL and will be shown to your users. More information about deployments can be found here.

To create a deployment, go to the Deployments section in your dashboard. You will be able to see all the previously saved deployments here as shown below.

Click on Create a Deployment. You will then be asked to select a deployment type as shown below.

There are two types of deployments. First is the embedded SDK deployment, which is basically the deployment of integrations on an SDK that will be embedded inside your app. The second is the Directory deployment, that publishes your integrations in an App Directory on a subdomain that you provide. Select this second option to create an App Directory.

1. Basic information

You will now land on the configuration page for the Directory deployment. It will start off with the basic info of your directory, as shown below.

After providing a name for your directory, you will need to select the cards that you want to show to your users. The available cards on the right side in the above image will consist of all your templates and the app cards that you’ve created. Your chosen cards will be added to the Selected Cards box on the left.

After selecting your cards, you can provide some optional information like the link to the homepage of your app and also the Google Analytics Tracking ID, if you’re using it.

After the tracking ID, you’ll need to provide the URL of your App Directory which your users will visit in order to access your integrations. This can be a subdomain of Integry, or a custom subdomain that you can create with your own app’s name in it. Of course, you will be charged more for a custom subdomain. For your users to access your App Directory, you can add this URL to the integrations section of your app, or wherever you want your users to see it.

Lastly, you’ll have to provide your app’s login URL, so that your users can log in to your app in order to create integrations from your App Directory. You can see the details of the authentication process for your users here.

2. Appearance

After providing the basic info of your Directory, you can click on the Create Directory button on the bottom right. This will save your Directory as a deployment on the Deployments page. You can then open it again and click the Appearance tab on the left. You will see new options as shown below.

The appearance page is where you set up the basic look of your App Directory for your users, as well as the look of your Directory deployment card on the Deployments page in your Integry account. Here, the following details will be required from you:

  • Title: The main title of your directory that will appear on the top for your users.
  • Header text: The supporting text that will appear below the title.
  • Directory icon: The favicon that will be displayed on the browser tab for your users, as well as on your Directory deployment card.
  • Your logo: Your app’s logo that will show your branding in the App Directory.
  • Header image: The main image that you want your users to see in the App Directory.
  • Colors: The accent, background, and text colors of the App Directory to be displayed to your users.
  • Social media links: The social media links that will appear at the bottom of your App Directory page.

Add the end of the appearance section, you can see an Advanced Options button as shown below.

Clicking on it will reveal some additional customization options:

As shown in the above image, you can customize the entire HTML of your App Directory by downloading and modifying the default code, and then uploading it back as your own HTML. This essentially makes you in charge of the complete design and look of your App Directory that your users will see.

Once done with the appearance settings, click on the Update Directory button on the bottom right to move on to the next configuration section.

3. Localization

The default interface of your App Directory will be in English. However, you have the ability to add multiple languages to this interface. This section in your Directory configuration looks like this:

Here, you can click on the +Add Language button to add more languages on top of the English language. You can provide the page title and description in each respective language. You can also select the default language of your Directory by the selection button on the far right.

After finishing with the localization settings, click the Add Languages button on the bottom right to save these settings.

After you finalize and save your App Directory, it will appear in your deployments menu as shown below.

After this, all you need to do is provide the URL of your App Directory to your users. You can do that by adding it in the Integrations section inside your app. Once your users click on this URL, they will land on your App Directory homepage.

App Directory requires integration with your authentication so that the users can create integrations. Without this, users will only be able to view, and not create integration. Click here to learn about how SSO works.

Did this answer your question?