Skip to content
APIANTdocs
GuidePlatformv1

Publish template to production

Learn how to publish automation templates from development systems to linked production systems. Users with the "Publish to Production" permission can easily select the option from the gear menu. Multiple automations can be published at once by choosing t

#automation#triggers#actions#account#modules

Development systems can publish automation templates to their linked production systems "templates" account. See Automation Templates

To publish an automation as a template from a development system to a production system, accounts having the "Publish to Production" permission can use the following gear menu option:

More than one automation can be published at once by first selecting a folder then choosing this option under the Group menu:

Select the destination production system(s):

If a single production system is selected and it has more than one tenant, also choose the destination tenant(s):

The automation(s) are published into the "templates" account in the selected production system(s) and tenant(s).

All of the automation's referenced apps, triggers, actions, assemblies, and modules are included.

Any content in the production system that is older than the published content will be updated!

The automation template in the development system becomes linked to the published template(s) in the destination production system(s) and tenant(s). This is done by them all sharing the same UUID identifier.

Related docs

CalendarConnect: Calendly → Mindbody
#actions#account
CRMConnect: DonorPerfect → ActiveCampaign
#automation
Automation Editor
#automation#triggers#actions
AppConnect
#automation#triggers#account
APIANT Inline
#automation
Last updated April 4, 2026