Triggers: Define when to initiate the automation process. Can be based on changes in the base, time, or external events.
Actions: Specify operations to execute after a trigger is activated. Can include data operations, sending notifications, or integration with external systems.
Conditions: Allow adding logical decisions between triggers and actions for more precise control.
Testing: Provides functionality to test automation processes before actual deployment, ensuring they work as expected.
Execution Logs: Record automation run history for monitoring and troubleshooting.
Select an action type, such as “Create Record in Another Table”
Choose the target table.
Configure field values for the new record
Select values from the trigger’s dynamic record.
Click the “Generate Preview” button to validate the action configuration. Or click “Run as Configured” to create an actual record and get the return value
When modifying a running automation, for easier debugging, changes to the automation configuration won’t take effect immediately in the running automation. Instead, a prompt will appear on the page, and the automation will only be applied to the running process after you confirm the update. You can safely modify the automation without worrying about accidentally interrupting existing processes.By combining these elements, users can create complex automation workflows, from simple data updates to complex multi-step business processes. Automation not only saves time but also reduces human error, ensuring process consistency and reliability.In the following chapters, we’ll explore in detail the functionality, configuration methods, and best practices for each component.