Skip to main content
Version: 3.1.4

Default Behavior

The SDK rendering configuration comes with sensible defaults so you can get started quickly. Let's see what those defaults are and how to configure them to your liking.


The SDK will render the templates view in the configured container as a list.

Configured integrations

Integrations that have been configured will be shown in a separate tab.

Searching templates

The search function supports fuzzy search and will return results that match template names, template tags and third party app names such as Slack and Facebook.

Template forms

We require the consumer app to provide a renderMode parameter when initializing views. This parameter controls where and how the template form will load when attempting to set up an integration.

Rendering in a modal

In this mode, the SDK will open a custom modal to show template forms.

Rendering in-line

In this mode, the SDK will swap out the templates view with the template form in the same container.

Rendering in a detached state

This mode is used when the template form does not exist in the same context and page as the template listing view. You can use this to render the form in a container in a different DOM hierarchy or a new page.