Templates & Template Deployment
Pre-built automation logic that can be deployed and reused across multiple accounts while maintaining a single source of truth for updates.
Automation templates are useful when multiple accounts need to use the same automation logic yet the developer(s) of the automation logic want to maintain a single copy.
An automation template can be deployed from one account to multiple other accounts.
The deployed automations can be linked back to the original templates, so that subsequent deployments will update the linked copies rather than creating all-new separate copies.
In this section
Categories & collections
Organizing templates into categories and collections using folders, including how to create multi-automation template collections with placeholder catalog entries.
Deploying templates
End users can deploy templates from the catalog with one click, and system staff can manually distribute templates across multiple user accounts.
Publishing templates
Process for publishing automation templates to the templates account, with different procedures for non-development and development systems.
Settings annotations
Control which trigger and action settings display to end users during template deployment and initial automation configuration, with optional annotation text.
Templates catalog
Set up a branded template catalog within your dedicated APIANT system to let users install pre-built automations with a single click through customizable categories and collections.
Templates dashboard
Central interface for creating, organizing, and publishing automation templates to a catalog, with options to control template visibility and deploy them to user accounts.
The "templates" account
Special system account used to maintain the template catalog and optionally deploy templates to user accounts, accessible via direct login or account switching.