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 Assemblies

1min

Trigger assemblies cause the actions in an automation to be executed when their criteria is met.

Typically triggers will fire upon new or updated data.

The main categories of triggers are:

  • Polling triggers that periodically check an API for new or updated data, for example every 15 minutes.
  • Date/Time triggers that fire at a certain date and time, or on a periodic time schedule like once an hour.
  • Gated triggers that fire only once each time a threshold criteria is met, like a weather trigger that fires when a temperature goes below a certain value.
  • Webhook triggers that receive new or updated data pushed from an external system. These are also called Instant Triggers.
  • Protocol thread triggers that maintain an always-on connection for sending and receiving data by running in threads on the server. Generally a SDK is used that under the hood will maintain a socket connection and communicate with a protocol over the socket. An example is the XMPP protocol for Jabber. Another example is a message queue listener. Protocol triggers are also Instant Triggers.
  • Export triggers used for one-time bulk exports of data, typically for loading into another system.



Updated 03 Mar 2023
Did this page help you?
PREVIOUS
Action Assemblies
NEXT
Polling Triggers
Docs powered by
Archbee
Docs powered by
Archbee