Call an operation
BetaChanges data
Calls one operation of your own SOAP web service and returns its answer.
Settings
| Setting | What it is |
|---|---|
| ConnectionRequired | The SOAP web service connection the step signs in with. |
| OperationRequired | The operations the connection read from the service's description when it was tested. Test the connection again to see one the service added since. |
| Parameters | The operation's parameters by the names the service uses, such as { "werknemerId": 12 }. A field left out is not sent; null sends it empty. An update usually REPLACES the record: read it first, change what you need, and send the whole record back. |
| What this operation does | A read may be re-run freely. Choose the other one for any operation that creates, updates or sends something: run twice, it could create two records. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `soap`) |
operation | texta value from the list the connection's Test read |
parameters | object (any keys), by default {} |
changes | "reads" or "changes", by default "changes" |
Output
| Field | Type |
|---|---|
resultWhat the service answered | any |
Sample output, and the expression for each field
- result
- Achternaam"Jansen"
- Id12
Errors
When a step of this node stops a run, the run page shows a code. Look it up:
Example step
The step as a flow file holds it. Replace each value in <…>.
{
"config": {
"changes": "changes",
"connection": "<connection id>",
"operation": "<operation>",
"parameters": {}
},
"label": "Call an operation",
"type": "soap.callOperation",
"version": 1
}