LetsFlow
Search…
LetsFlow
Introduction
Getting started
Tutorials
The basics
A handshake
A proper introduction
Under one condition
Invitation by e-mail
REST API
Authentication
API endpoints
Client libraries
Reference
Workflow
Scenario
Process
Response
Trigger
HTTP trigger
NOP trigger
Event trigger
Advanced topics
Distributed workflows
Cryptography
Powered By
GitBook
NOP trigger
NOP trigger is able to manipulate data within the process. So it allows you to update asset or actors information.
YAML
JSON
"$schema"
:
https
:
//specs.letsflow.io/v0.2.0/action/nop/schema.json
#
actor
:
issuer
default_response
:
approve
trigger_response
:
"<if>"
:
condition
:
"<apply>"
:
input
:
available
:
"<ref>"
:
assets.available
query
:
available.shipments
>
`0`
then
:
approve
else
:
deny
responses
:
approve
:
{}
dany
:
{}
{
"$schema"
:
"https://specs.letsflow.io/v0.2.0/action/nop/schema.json#"
,
"actor"
:
"issuer"
,
"default_response"
:
"approve"
,
"trigger_response"
:
{
"<if>"
:
{
"condition"
:
{
"<apply>"
:
{
"input"
:
{
"available"
:
{
"<ref>"
:
"assets.available"
}
},
"query"
:
"available.shipments > `0`"
}
},
"then"
:
"approve"
,
"else"
:
"deny"
}
},
"responses"
:
{
"approve"
:
{},
"dany"
:
{}
}
}
Previous
HTTP trigger
Next
Event trigger
Last modified
2yr ago
Copy link