All protocols that can be used as Triggers in an Automation can also be used as Actions.

All protocols that can be used as Triggers in an Automation can also be used as Actions.

• A. False
• B. True
• C. Maybe
• D. Not applicable

Answer: (A)

When building an Automation, triggers and actions serve different roles: triggers start the workflow by waiting for an event, while actions carry out tasks once the workflow is running. A protocol defines how that piece of the automation behaves, and not all protocols are designed to function in both roles. Some protocols are built to listen for specific conditions or events and so can only be used as triggers. Others are designed to perform a task or operation and so can only be used as actions. Because of these role-specific designs, you can’t assume every protocol available as a Trigger can also be used as an Action (and vice versa). Check the capabilities of each protocol to know where it fits.

When building an Automation, triggers and actions serve different roles: triggers start the workflow by waiting for an event, while actions carry out tasks once the workflow is running. A protocol defines how that piece of the automation behaves, and not all protocols are designed to function in both roles. Some protocols are built to listen for specific conditions or events and so can only be used as triggers. Others are designed to perform a task or operation and so can only be used as actions. Because of these role-specific designs, you can’t assume every protocol available as a Trigger can also be used as an Action (and vice versa). Check the capabilities of each protocol to know where it fits.