In some cases, you might not want to trigger all actions immediately. For example: you want to dim your lights through 10 stages from 100% to 0%. Or you want to turn off all light's in your house when leaving, but give you 10 minutes of light to find your way through your backyard.
You can achieve such scenarios with the "Delay" option. Delayed actions will wait in a queue until the time is up and execute then. If you configured multiple actions, the next one will be looked at after the previous one fired.
Delays are defined in seconds and can be any value from 0 to 3600 (seconds).
- The delay value is counted from one action to the next. So if you configure one action with a delay of 30 seconds and a second one with 20 seconds, the second action will be triggered after 50 seconds.
- After the logicblock has evaluated, all current configured actions are collected and saved for execution. If you add an action while others are pending, it will not be active until the next logicblock evaluation.
- If you delete a pending action from the logicblock configuration, it's execution will be skipped.
- If you change a parameter value of a pending action, the last saved action configuration will be taken.
Additional Webhook Parameters
When triggering an IFTTT applet, it is possible to pass up to three parameters to the Webhook Service. Those parameters are named value1 to value3. Within an applet, the content of those parameters is accessible as ingredient and can be passed to the outgoing action.
You can set static values here and they will be passed with every call. This is handy if you have setup a generic applet in IFTTT (e.g. send a notification) which you want to use in multiple logicblocks with only the values changing (e.g. to track which logicblock fired the action).
In other cases, you might want to pass along the content of a variable instead of a static value. You can do this by entering the variable name in double curly braces.
- Static content and variables cannot be combined in one field, so make sure you use multiple value fields for that case.
- If you make a mistake in the syntax, the string will not be modified and passed as is.
- If you enter a variable name that does not exist, Apilio will replace the string with the text "variable_not_found". This will also be the case if you rename or delete a variable which was used in a action.
After you save a logicblock and look at it in show mode, the current values will be parsed into the action URLs to let you check if it comes out as expected.