How to enable a Custom Content Connector

This article guides you through the setup of a Custom Content Connector integration in the Templafy Admin portal. The Custom Content Connector allows you to surface images, slides, slide elements, text elements, email elements, and PDFs.

How to configure a Custom Content Connector

1. Go to Integrations section.
2. Go to Available tab.
3. Search for Custom Content Connector.
4. Click +.
5. Fill out the required fields:
   • Base URL - first part of the URL when accessing content source.
6. Pick an Asset type from the drop-down.
7. Provide a name to the asset library - this name will be displayed to end-users in Templafy Library.
   
8. Optionally, you can add additional libraries following the above step, click on + Add Library connection, or click on the ellipsis menu next to the Library and click Duplicate.
9. Select desired Authentication type:
   • OAuth 2 Client Credentials- will display same content to all users.
   • OAuth 2 Authorization Code- will require user login and will display user specific content.
   • OAuth 2 Authorization Code with PKCE- will require user login and will display user specific content.
10. Based on Authentication type, fill out necessary configuration fields:
    • For OAuth 2 Client Credentials:
      • Client ID (required)
      • Client Secret (required)
      • Token Endpoint (required) - default value will be oauth/token, but this can be changed to reflect your Authorization Server's token endpoint.
      • Scopes (optional) - added here as defined in the source system (e.g. asset:read).
        • Note - If more than one scope is needed, values should be separated with a space.
        
    • For OAuth 2 Authorization Code and OAuth 2 Authorization Code with PKCE:
      • Client ID (required)
      • Client Secret (required for OAuth 2 Authorization Code. Leave blank for OAuth 2 Authorization Code with PKCE).
      • Authorize Endpoint (required)
      • Token Endpoint (required) - default value will be oauth/token, but this can be changed to reflect your Authorization Server's token endpoint. The Endpoint can be a full absolute URL, or a relative URL. In the case of a relative URL, the Token Endpoint value will be concatenated with the Base URL.
      • Scopes (optional) - added here as defined in the source system (e.g. asset:read).
        • Note - If more than one scope is needed, values should be separated with a space
        
11. Hit Save.
    

    Note If the Custom Content Connector is utilizing OAuth 2 Authorization code or OAuth 2 Authorization code with PKCE as an authentication type, the following should be noted: When not logged in, the user will not be able to access any external system content; the content will only be displayed once the login has been successful. If the user is already logged in on the connected system's side, the log in on Templafy's side will be seamless as the token already exists.  If the user isn't already logged in on the connected system's side, the user will need to provide their credentials to log in as the token cannot be found. If a user has multiple external system accounts and needs to switch between these accounts, this can be performed by logging out and logging in again within the same browser, OR by opening a different browser (or incognito window) and logging in with the desired account.  If you are building your own API so that Templafy can connect to it, follow this guide.