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.
Use globally defined OpenAI credentials to authenticate this action.
The ID of the model you want to use. E.g.: text-davinci-003
The input text used for the edit.
The instructions that tell the model what to do.
The number of inputs generated for the edit.
This argument accepts a value between 0 and 1. The higher the temperatue (e.g. 0.9), the more creative the answer for the edit.
This is an alternative to the temperature argument where the model considers the results of the tokens with the given probability mass. Its suggested to use temperature instead.
Set the number of seconds you want to wait before the request to OpenAI runs into a timeout.
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)