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 ticket id
(Mixed) The id of the ticket to update.
(String) The customer email. You can provide an existing email address of a customer. If the customer doesn't exist, a new customer will be added by the given email argument.
(String) The first name of the customer (In case the customer does not exist).
(String) The last name of the customer (In case the customer does not exist).
(String) The subject (title) of the ticket.
(String) The ticket details (content).
(Mixed) The agent. You can choose either the email or the ID of the agent.
(Integer) The product ID.
(String) The priority of the ticket.
The priority level set by the client
(String) The priority of a customer.
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)