execute
Execute a specified section or URL as a subroutine, and upon completion, return to the current document. Use the return statement to pass any return values or objects back to the current document.
Properties
execute
An object that accepts the following properties.
execute.dest
Accepts any valid destination
execute.params
Named parameters to send to section or URL
execute.meta
User-defined metadata. This data is ignored by SignalWire and can be used for your own tracking purposes.
execute.on_return
Array of SWML methods to execute when the executed section or URL returns.
execute.result
Action to take based on the result of the call. This will run once the peer leg of the call has ended.
Will use the switch method when the return_value is a object, and will use the cond method when the return_value is an array.
Valid Destinations
The destination string can be one of:
"section_name"- section in the current document to execute. (For example:main)- A URL (http or https) - URL pointing to the document to execute. An HTTP POST request will be sent to the URL. The
paramsobject is passed, along with the variables and theCallobject. Authentication can also be set in the url in the format ofusername:password@url. - An inline SWML document (as a JSON string) - SWML document provided directly as a JSON string.
Examples
Executing a subroutine
Executing a subroutine and branching on return
Execute a SWML script hosted on a server
A minimal server for this SWML script can be written as follows:
Python/Flask
JavaScript/Express
This server (running on localhost) can be made accessible to the wider web (and thus this SWML script) using forwarding tools like ngrok.
Visit ngrok.com to learn how.
The server will be sent the following payload:
The call object is described in detail in the introduction. All variables created
within the SWML document are passed inside vars, and the params object contains the parameters defined in the params
parameter of execute.