Every scenario must begin with a Start node. The Start type depends on what the scenario is used for:
- Integration (used in PingTree)
- Structure (used for validation)
- Tracking
- Custom
Integration scenarios in PingTree
When an integration is used in PingTree, you can have multiple Start nodes because each flow has its own separate path.
- PING flow has its own Start and its own End
- POST flow has its own Start and its own End
- Do not connect PING and POST directly
- These flows must stay separate with no connection between them
Building the flow
Everything starts with Start. From there you can add additional elements and connect them to Start and to each other. Each connection can include a filter that controls what is allowed to continue to the next step.
The usual flow is:
- Start
- Modify field
- HTTP
- Set variable with condition for success
Sometimes you may need to wait a few seconds, you can use the Wait step, but keep in mind the user will stay and wait on the loading screen after submitting the form. You can also repeat steps using the Repeater step if needed. In other cases, you may need to verify the lead, which is usually done via an additional HTTP request.
Saving values from responses
Sometimes you will want to store values returned by a request. You can do this by setting the value as a variable.
- Supported predefined variables are listed here
- If you need a custom variable, save it to a parameter with the prefix “custom_” and then reference it as {custom_anything}.
