Arguments are specific pieces of information you can set within an action. They allow you to send over custom information based on your needs. For Flows automation, all of those will be available directly within the action step. If you are using "Webhooks" in combination with automation services such as Zapier, Pabbly Connect, or Make.com, the argument is the key/value pair within the body of the request. Within JSON strings, the key is the argument, and the value is the argument value (To learn more about the webhooks action parameters, please click here). All of the arguments are available within both the Webhooks and Flows Automations.
The relative path of the folder you want to copy. For example: wp-content/uploads/demo-folder
The relative path of the destination. For example: wp-content/uploads/new-folder (See the main description for more information)
The mode is 0777 by default, which means the widest possible access.
Allows the creation of nested directories specified in the pathname. Possible values: "yes" and "no". Default: "no". If set to yes, all in your path mentioned folders will be created if they don't exist.
Advanced: Register a custom action after this webhook was fired.
WordPress action callback (Advanced)
(String) Register a custom WordPress hook callback. The value will be called as followed: do_action( $yourdefinedaction, $action_return_data, $request_data )
Flows or Webhooks?
While automating, it is crucial that you understand the difference between our Flows feature and Webhooks as it affects the way you work with our product. Below you will find further details of the core differences.
Can receive data from an external URL/API/Webhook to run multiple actions within our plugin (E.g., When a flow was executed, create a user, then the data to Zapier, take the response, and send an email).
Offers bidirectional connections (Can send AND receive data)