Differences Between Automations Pro & Automations

Introduction

This article explores the distinctions between Automations Pro and Automations, focusing on three key aspects: the ability to start trigger events, the ability to perform actions, and feature limitations.

Difference

  • ☑️: indicates partial support for features
  • ✅: indicates full support for all features
  • ❌: indicates no support for features

Type

Feature

Automations

Automations Pro

Ability to Start Trigger Events

Form Trigger (Data Change)

Trigger when adding records

Trigger when updating records

✅(Trigger Automations Pro when any fields or any specified fields are updated.)

Trigger when deleting records

Form Trigger (Workflow Change)

Trigger when workflows flow to next node

✅(Trigger Automations Pro when you submit or return workflows at a specified field.)

Trigger when workflows end

Scheduled Trigger

Trigger based on custom time

☑️(Only trigger a plugin at a scheduled time)

Trigger based on Date&Time field

Triggered by HTTP

Trigger when the specified URL receives third-party data.

Choose Multiple Triggers

You can choose multiple trigger events. When any of the events occurs, automations will run.

☑️(Only support events, including records addition or update.)

Trigger Linkage

Tigger other automations

✅(Enabled for all by default; no trigger rules; it can only trigger other Automations)

✅You can set the rules:

  • Tigger all automations
  • Tigger specified automations
  • Trigger none

Note: Automations and Automations Pro do not form trigger linkage.

N

Ability to Perform Actions

Add Record

Add one record

Add multiple records based on multiple records

Add one/multiple record(s) based on a subform

Update Record

Update one/multiple record(s)

Update records in the current form

☑️(Update form fields only. Note that the trigger events cannot be the same as actions.)

Update form records based on a subform

Update/add subform records based on a subform

✅(Update a subform with multiple records. Automations Pro supports more options for setting filter conditions.)

Update/add subform records based on a form

☑️ (Only support updating subform records.)

Delete Record

Delete a row in a subform

❌(Do not delete a subform record separately.)

Delete one/multiple record(s)

Delete form records based on a subform

☑️

☑️

Query Record(s)

Query one/multiple record(s) in a form

Add Path

Perform actions based on different conditions

Add Formula

Perform calculations on existing records, which can be used for subsequent actions, such as adding/updating records.

✅(Perform calculations via the Add Formula node.)

Add Plugin

Call a plugin

✅(Call a plugin via the Add Plugin node.)

Feature Limitation

Number of Action Nodes

The number of action nodes that can be processed for each trigger

5

100

Nested Loops

/

  • Do not support loop configurations
  • Support a maximum of three nesting levels
  • Support loop configurations. Runs once and then stop.
  • No limit to the nesting levels of the configuration, but support a maximum of 10 execution layers.

Trigger Limit

Some operations do not trigger automations.

  • Import data
  • Output a form from Data Factory
  • Delete data in batches
  • Update data in batches
  • Import data
  • Output a form from Data Factory
  • Delete data in batches (Deleting multiple records, deleting filtered records, or deleting all records will not trigger the automation; however, deleting a single record will trigger it.)
  • Update data in batches (Selecting single or multiple records for batch editing will not trigger automations.)
  • When the automation is set with Trigger by Date&Time field and more than 500 records meet the triggering condition(s) at the same time, no actions will be performed.

Data Limit

The number of records that can be processed for each trigger

  • Maximum added records: 200
  • Maximum updated records: 200
  • Max deleted records: 100
  • Maximum added records
    • At one node: 200
    • In a single automation series: 1000
    • In entire automation system (within one hour): 10,000
  • Maximum deleted records: 100
  • Maximum updated records: 200; for multiple subform records to be updated, the calculation volume for record matching must be less than or equal to 1 million.

Was this information helpful?
Yes
NoNo
Need more help? Contact support