Template Metadata will define how your template will appear in the SDK. The metadata takes in the basic template info and branding details. It will appear inside your app.
Setting up the template metadata is very simple. On the right side of the template builder, you can see a slide-in menu. You can define various aspects of the template, which are discussed below in detail.
Under the General Settings option, you can set the Template title & description.
Wizard: The toggle, if turned on, displays the template as a multi-step wizard. For more information, click here.
Loop Prevention: Makes sure your two-way sync integration is not affected by potential endless loops. This is talked about in detail here.
Forced Updated Order: Provides an order to the events sent by the triggers in your template. Details about this can be found here.
Cache Output: Let's you to use the trigger response (within the given time), cached last time instead of executing the template steps
The Fields tab displays the template data tree i.e. all the steps, structure, and data inside steps' tags. A tag refers to an individual field & its data inside a step. If you want to pass around the value of a field in your workflow, you simply use a tag. When you first open the Fields tab, you will see all the template steps.
On clicking a step, it will expand and display the tags & data inside them. When you hover the tag it gives you the following options
Add to Field: By clicking on the button you can add the tag inside any field in focus in your template
Copy: It copies the tag key & value
You can also create multiple data trees for testing purpose
This tab lets you define the errors you want to send to your users, how often to send them. Details discussed below:
"error_detail":"This is test message"
"integration_name": "My integration",
"user_name": "User One",
You can set up the error notification in two different ways:
1. If you have your own incoming webhook URL, you can paste it here
2. If you have an API for dispatching errors to your end-users, store errors in the database, etc, you can set up the URL as follows:
Set up a separate template with a dedicated use case where the first step will be an incoming webhook trigger and the second step can be your own app’s action (send email notification etc). You then create an integration via this separate template, it will provide you an integration URL to post data on, you can copy that URL and provide it under the error notification settings of your first template. etc.
The product information lets you define custom branding, help on how the template works, a little about apps used, any useful social media links, etc on the Template Product page. All this information only appears if you turn on the "Enabled" toggle for product information. So, when a user opens a template to set up the integration, they will be redirected first to the Template Product page where they will see all configurations you do, in this tab. When you open this tab you can see the following options
Screenshots: You can add helpful visuals for your user on step by step integration creation
Category: The app's category that you can select from a drop-down.
Keywords: The keywords or tags that will help people discover your app.
Website: The link to the app's homepage.
Terms and Services: The link to the terms and services section of the app.
Documentation: The link to the app's API documentation.
Product Info Icon: The template icon
Support email address: The app's support email address or the link to the contact page.
Social media: These are the app's social media link for Facebook, Twitter, and LinkedIn.
This is the eventual look of the Product page
Lastly, click the Save button to save all the changes