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
Assembly Editor
API Integrations

Trigger/Action Commonality

6min

Trigger and Action assemblies share some common features and behaviors.

API Credentials

Most triggers and actions invoke API's that require either user-entered credentials or OAuth credentials.

The OAuth Transaction module and its variants automatically fetch the user's credentials.

If an HTTP Transaction module or its variants is used, the Service Credentials – Get module is needed to fetch API credentials saved by the App Assembly:

Document image


By default, the OAuth Transaction modules and Service Credentials module use the service account configured in the automation editor when the trigger/action were added to the automation.

See Service Accounts if you need to be able to access connected service accounts besides the one configured in the automation editor.

Error Handling

When a Trigger or Action assembly returns an error, the following occurs:

  • The automation stops its processing immediately
  • If the automation's owner has configured it to report any error, an email alert is sent to the automation's owner based on their configured email delivery schedule
  • An email alert is sent to the system admin based on their configured email delivery schedule

Errors can be triggered in the following ways:

  • When a Fatal Error module's criteria is met
  • When a HTTP Transaction module or OAuth Transaction module, or any of their variants, has the “halt assembly if error” setting enabled and the API either returns an HTTP status code >= 400 or no data can be returned due to network-level errors
  • When any module returns an error due to misconfiguration, missing required data, or processing errors

The Turn Off Automation module can be placed within a Conditional module if a permanent error is detected such that it makes no sense to keep the automation running.

An example is an action that writes rows to a spreadsheet. If the spreadsheet no longer exists, the automation should be halted.

Configuration Settings

Triggers and Actions can display configuration settings in the Automation Editor:

Document image


Configuration settings are displayed for the corresponding Parameter modules placed into the trigger and action assemblies:

Document image


In this example, the end user must first choose a workspace and then select a project within the workspace. The List Asana Projects subassembly uses the selected workspace's id to fetch the projects for the selected workspace.

The Sequence number determines the display ordering of Parameter modules in the Automation Editor.

Document image




Updated 03 Mar 2023
Did this page help you?
PREVIOUS
App Assemblies
NEXT
Action Assemblies
Docs powered by
Archbee
TABLE OF CONTENTS
API Credentials
Error Handling
Configuration Settings
Docs powered by
Archbee