Templates

A template is a platform-maintained, read-only starting point for a configuration, pre-populated for a use case. Templates show the kind of analysis a use case calls for, so you can adopt a working setup and adjust it rather than assembling one from scratch.

What a template contains

A template's definition is a complete configuration document — the operators to run, their granularities and context settings, and the actions to fire — with one deliberate gap: actions are defined without their delivery destinations. The granularities reflect a suggested setup for the use case, not a fixed one.

Templates are maintained by Simwood and available to every account; you cannot edit a template itself.

Applying a template

You apply a template on your side, in three steps:

1. Fetch the template and read its definition.
2. Complete the fields it leaves open — at minimum each action's webhook_url — and adjust operator selection, granularity, and context to suit.
3. Create a configuration from the result.

The configuration you create is your own, owned by your account and identified by its own uuid. You can record where it came from by passing template_id, which is kept for lineage only and never merges anything from the template back in — later changes to the template never affect a configuration you have already created.