website logo
⌘K
Explore our documentation
Contact APIANT support
What is APIANT?
Automation Editor
Key Concepts
Account Management
Managing Automations
App Connections
Building Automations
Alert Mappings
Troubleshooting
CRMConnect: Mindbody → HubSpot
CRMConnect: DonorPerfect → HubSpot
CRMConnect: DonorPerfect → ActiveCampaign
MailConnect: DonorPerfect → Mailchimp
ShopConnect
ShopConnect Settings
Sync Products
Manually sync Mindbody services/pricing options to Shopify
How to tag products in Shopify to prevent sync during sales sent to Mindbody
Retrying orders from Shopify → Mindbody
Manually pushing Mindbody orders to Shopify
Mindbody Pricing Discontinuation: Integration with Shopify
Guide to manually syncing Mindbody Packages with Shopify Products
Features that are not supported in ShopConnect
Automation Alert Reports
Linked Accounts
ZoomConnect
New features in version 4
Settings
General
Email & SMS
BOTs
MINDBODY
Zoom
ZoomConnect Mindbody Appointments - Setup and requirements
Troubleshooting
Assembly Editor
Key Concepts
Account Management
API Key Management
Managing Content
Building Assemblies
API Integrations
Other Assembly Types
Keyvalue Storage
Assembly development cycle
APIANT for Integrators
Help Forum
Automation Templates
Development Server
Module IDE
Shared App Connections
Tenants and Linked Accounts
APIANT Inline
Supported functionality
Embed Inline
Sandbox
Docs powered by
Archbee
APIANT for Integrators
Automation Templates

Settings annotations

3min

When templates are deployed to a user account for the first time and the deployed automations are initially turned on, the system will walk the user through the connection of needed app accounts and through the configuration of the automations.

The template developer can control which trigger and action settings need to be configured when templates are deployed and initially turned on for the first time.

Per the section about Trigger settings, trigger settings appear above the trigger filter. This example has two settings:

Document image


Per Action settings, action settings appear above the error handling. This example has two settings:

Document image


Accounts having the "Automation Templates" permission can control the visibility of settings and settings annotations via this checkbox at the bottom of trigger and action settings:

Document image


This option is checked by default. When checked, this means that the trigger/action settings will not appear when the template is deployed to an account and the automation is turned on for the first time and configured.

When unchecked, the settings will be shown to the end user when the deployed automation is turned on for the first time:

Document image


When the "show template annotations" option is checked, entry fields will appear under the settings where text can be entered to document what the end user needs to know about how to configure the setting:

Document image


HTML markup is allowed in the settings annotation text.

Updated 03 Mar 2023
Did this page help you?
PREVIOUS
Deploying templates
NEXT
Development Server
Docs powered by
Archbee
Docs powered by
Archbee