External actions
Last updated
Last updated
The "External Actions" feature empowers users to trigger and execute actions and processes in external systems, outside of fulfillmenttools. This includes functionalities such as sending consumer emails, adjusting payments, and other order-related processes.
The primary goal of this feature is to facilitate seamless communication with third-party systems. Users can define the capabilities and functionalities of external actions by utilizing our API and seamlessly integrating our platform with other systems.
There are currently two types of external actions available: "LINK" and "FORM" and "COMMENT".
The user who triggered the external action is displayed on the order history page (include link) on the right side.
Please go to the for more information on how to configure external actions via API. The API documentation can be found here.
With the "LINK" type, users can attach a link or deep link to a process, enabling users to execute processes in the linked external system manually.
The "FORM" type allows users to define a modal where users can input data. Upon confirmation, an external event is triggered, enabling the execution of further processes (done by a connector).
Executing an external action is logged and displayed in the order history, providing users with visibility into the actions taken throughout the order workflow.
When adding the external action COMMENT to a process it does not create another entry in the three dot menu. The purpose of this action is not to trigger an action to an external system but to receive info from such a system.
There are 2 ways to add info
you can add information to a process
you can add information to a process but relate it to another external action like FORM
Adding information to the process without relation to another external action allows you to add some general information to the process which might be important for fulfillment. An example would be: A CRM system added information about the consumer-segment which informs a user that this order might be handled in a specific way.
If you want to add information which relates to another external action you have the possibility to store "the answer" / "reaction" of the triggered system and connect it to the technicality of the external action.
An example would be: You created an external action from type "FORM" which triggers a payment system in order to reduce the paid amount by 10%. The payment system itself now might inform you that the 10% was successfully reduced. In this case it would make sense that this information is not only connected to the process but connected directly to the external action FORM of this process which was originally responsible for the trigger "payment adjustment".
Those additional information are then displayed in the order history on the right hand side.
