All arguments are inherited from the REST API, however here you are able to extend or add arguments that are specific to the action.
Please refer to Argument Fundamentals for more details on each property and how arguments work.
.png "image(43).png")
Parameter Arguments
Within an action, you can set an argument’s location to param , which can then be accessed within the URL property of the action. You can see example here:
Within the arguments list:
.png "image(73).png")
Within the argument properties:
.png "image(74).png")
Use of the argument within the URL :
.png "image(75).png")
NOTE: param arguments can be accessed in the URL by prefixing with : which will trigger an autocomplete pre-filled with all param arguments.
Argument Features
Arguments also have a set of additional features, that include the following:
Limit & Offset
These settings will enable or disable the pagination settings for the action (for example, “create” actions wouldn’t support pagination, while others might).
Custom Args
This feature is a boolean option that, if enabled, will allow you to add custom arguments at the workflow level. This is particularly important when client-specific implementations have created additional arguments that aren’t defined at the app level (and therefore shouldn’t be included within the action definition itself).
If enabled, you can also configure them (accessed via the small right-arrow next to the “Enabled” value).
.png "image(45).png")
If you define the custom args as “free form,” it will allow users to create their own args when building a workflow, but you can also link the custom args to a lookup. If you connect the custom args to a lookup, it must be connected to another action that will retrieve the list of arguments specific for that client account.
Filters
You can also override any filters set at the API level here by enabling them, and then adjusting the relevant configuration (accessed via the small right-arrow next to the “Enabled” value).
.png "image(46).png")