Playbook Constructs and Paradigms
Introduction
Playbooks 101
Paradigms
Constructs
Array Iteration
Collecting and Processing Data in Playbooks
CSV Parser
HTTP Trigger Response Codes
How to Check if a String is Empty
Human-in-the-Loop Workflows
If-Merge: Merging Conditional Paths
JSON Path Filtering
JSON-to-Join: Converting String Array to String
Making a Playbook Fail
Making HTTP Requests and Visually Selecting JSON Paths
Merge Operator
Retrieving the Value of a Custom Metric
Trigger Passback
Try Until Complete
Using Breakpoints to Debug Playbooks
Variable Initialization
Introductions
Helpful Tips and Tricks
Gotchas
Powered by GitBook
Have an account? Sign in

Constructs

Last updated 9 months ago
Edit on GitHub

When I say "construct", I am referring to two or more Playbook apps which are connected in a way that allow a user to accomplish a common goal (e.g. requesting content from a website) in a robust, (relatively) simple, effective, and maintainable manner.

Previous
Structuring Playbook Systems
Next
Array Iteration