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
Automation Editor
...
Building Automations
Subroutines

Creating a subroutine

6min

To create a new subroutine, start by opening the subroutine catalog by either clicking the link at the top left of the automation editor, or by clicking or dragging the catalog's vertical splitter on the left side of the screen:

Document image


Then click the Create button above the catalog at the top left:

Document image


The editor creates a skeleton subroutine with the needed input trigger and output action:

Document image


Edit the trigger and add the needed input data fields for the subroutine:

Document image


When done adding fields, click the Fetch button to configure the trigger with those fields:

Document image


Now you can optionally add any needed trigger filters. Click the Save button when done.

For this example, we'll just use two actions to uppercase both the input title and description. Their input values are mapped to the two subroutine inputs:

Document image


Edit the subroutine output action and add two output fields:

Document image


Then click the Fetch button to configure those fields:

Document image


The output fields are then mapped to the two uppercased values from the preceding actions:

Document image


This is the finished subroutine that is ready to save:

Document image


Give the subroutine a name and description that will appear in the subroutine catalog.

Document image


Accounts having the "Public content" permission can optionally save the subroutine as public. Otherwise it will be private to your account.

Now the subroutine can either be tested or used within an automation:

Testing a subroutine

Executing a subroutine



Subroutines can be nested, but don't nest the same routine within itself. Otherwise an infinite loop will occur!



Updated 03 Mar 2023
Did this page help you?
PREVIOUS
Subroutines
NEXT
Testing a subroutine
Docs powered by
Archbee
Docs powered by
Archbee