Templates

👍

New in version 2.13 released November, 2022

Sliderule users often include the same Data Connectors across many Workflows. You may find you want to re-use your Data Connector configurations, but want to avoid setting them up from scratch for each new Workflow you use them in.

To support that, we now offer Templates. You can save a Data Connector configuration from within one of your workflows, including API Request Bodies or SQL Queries, as a Template. Then in all your other workflows, you can just Load that configuration from Saved Templates to avoid setting things up a second time.

Saving a template

Once you've set up a Data Connector block inside your workflow, and it's running the way you want, you should first Save it in your existing Workflow.

To Save the configuration as a Template for re-use elsewhere, click on the segmented arrow in the right-hand part of the Save Button to display Save Options. Select Save as Template, and give your template a name, and click Save.

Once you see the Template Saved confirmation appear, you can use this Template in future workflows. You can also click on the Templates tab on the sidebar, to see all saved templates your account has access to.

Using a Template

To use a Template in a different Workflow, simply drag out a block of the appropriate type (Database or API Call) and add it into your Workflow.

Click on the Block to open it, and in the top right, click Load Template

Once you've selected your Template, your SQL query (or request body for API calls) will be replaced with the template you saved.

Modifying your Data Connector after Loading Template

Once you've loaded your Template into a Block on your Workflow, you can modify that Block as you need for this particular Workflow. Changes you make after Loading into the new Workflow won't affect your other workflows, or the underlying template.

For example, maybe in the original Workflow where you saved this Template, you were matching a SQL query against input.phone_number but in your new Workflow, the field to match on is customer.mobile_phone. You can edit your SQL Query after loading the template to include this new field, without affecting your original Workflow.