About this article
This article will guide you through the setup of a Custom Content Connector integration in the Templafy Admin portal. The Custom Content Connector allows to surface images, slides, slide elements, text elements, email elements, and PDFs.
Prerequisites
|
How to configure a Custom Content Connector?
- Go to
Integrations
tab - Go to
Available
tab - Search for Custom Content Connector
- Click
+
- Fill out the required fields
- Base URL - first part of the URL when accessing content source
- Pick an
Asset type
from the drop-down - Provide a name to the asset library - this name will be displayed to end-users in Templafy Library.
- 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 clickDuplicate
- Select desired Authentication type
OAuth 2 Client Credentials
- will display same content to all usersOAuth 2 Authorization Code
- will require user login and will display user specific contentOAuth 2 Authorization Code with PKCE
- will require user login and will display user specific content
- 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
andOAuth 2 Authorization Code with PKCE
- Client ID (required)
- Client Secret (required for
OAuth 2 Authorization Code
. Leave blank forOAuth 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
- For
- Hit
Save
|
|
Related articles
Comments
0 comments
Article is closed for comments.