Update a workflow node
Changed onUpdate workflow-node-owned fields for a single node. To update a node, the workflow's state must not be Sending. Shared resources such as email messages and audience segments should be updated through their own APIs.
Request
- Base URLhttps://app.loops.so/api
- AuthHTTP bearer
Request body
Example request
{
"payload": {
"contactPropertyQuery": {
"key": "firstName"
}
}
}Response
Workflow node updated.
Example response
{
"workflow": {
"id": "clw1a3b5c7d9e1f3g5h7i9j1",
"url": "https://app.loops.so/workflows/clw1a3b5c7d9e1f3g5h7i9j1",
"workflowRevisionId": "clx7a3b5c7d9e1f3g5h7i9j2",
"status": "Draft",
"name": "Welcome series",
"description": "Onboarding emails for new signups",
"workflowGroupId": "clg7n5p3q1r9s7t5u3v1w9y7",
"mailingListId": "clm2k8j4h6g0f8d6s4a2b0z8",
"rootNodeId": "cln8p0q2r4s6t8u0v2w4x6z8",
"nodes": {
"cln8p0q2r4s6t8u0v2w4x6z8": {
"typeName": "SignupTrigger",
"nextNodeIds": [
"cln1a3b5c7d9e1f3g5h7i9j1"
]
},
"cln1a3b5c7d9e1f3g5h7i9j1": {
"typeName": "SendEmailAction",
"nextNodeIds": [],
"emailMessageId": "cle5f7g9h1i3j5k7l9m1n3p5",
"subject": "Welcome to Acme!"
}
}
}
}Changes
- info
added the required property
//to the response with the status
- info
- breaking
removed
subschema #1subschema #2subschema #3from the////////////request propertyoneOflist - breaking
removed
subschema #1subschema #2subschema #3from the///////request propertyoneOflist - breaking
removed
subschema #1subschema #2subschema #3from the///////request propertyoneOflist - breaking
added
subschema #1: Stringsubschema #2: Numbersubschema #3: Booleanto the//////////////////response propertyoneOflist for the response status - breaking
added
subschema #1: Stringsubschema #2: Numbersubschema #3: Booleanto the//////////////////response propertyoneOflist for the response status - breaking
added
subschema #1: Stringsubschema #2: Numbersubschema #3: Booleanto the//////////////response propertyoneOflist for the response status - breaking
added
subschema #1: Stringsubschema #2: Numbersubschema #3: Booleanto the//////////////response propertyoneOflist for the response status - breaking
added
subschema #1: Stringsubschema #2: Numbersubschema #3: Date rangeto the///////////////////response propertyoneOflist for the response status - breaking
added
subschema #2: Nullto the////////////response propertyoneOflist for the response status - breaking
added
subschema #2: Nullto the////////response propertyoneOflist for the response status - info
added
subschema #1: Stringsubschema #2: Numbersubschema #3: Booleanto the///////request propertyoneOflist - info
added
subschema #1: Stringsubschema #2: Numbersubschema #3: Booleanto the///////request propertyoneOflist - info
added
subschema #1: Stringsubschema #2: Numbersubschema #3: Date rangeto the////////////request propertyoneOflist - info
removed
subschema #1subschema #2subschema #3from the///////////////////response propertyoneOflist for the response status - info
removed
subschema #1subschema #2subschema #3from the//////////////////response propertyoneOflist for the response status - info
removed
subschema #1subschema #2subschema #3from the//////////////////response propertyoneOflist for the response status - info
removed
subschema #1subschema #2subschema #3from the//////////////response propertyoneOflist for the response status - info
removed
subschema #1subschema #2subschema #3from the//////////////response propertyoneOflist for the response status - info
removed
subschema #2from the////////////response propertyoneOflist for the response status - info
removed
subschema #2from the////////response propertyoneOflist for the response status
- breaking