Examples of How to Combine User Input, Action, and Condition Nodes

In this tutorial, you see how several core nodes can work together to create a more intelligent and scalable flow. Instead of collecting the same user information every time, the automation first checks whether the form has already been completed.

Part 01:

** Video 9 **

Use a Completion Tag Before Showing a Form

The flow starts after a user clicks a button to receive free lessons. Before showing the form, a Condition Node checks whether the user already has a tag such as lead_form_completed.

If the user already has that tag, the form is skipped and the flow continues directly to the next message. This prevents repeat users from seeing the same form again.

Collect Information Only When Needed

If the user does not have the completion tag, the flow continues to the form. In this example, the system collects first name, last name, and email address through User Input Nodes.

Then, the user selects their gender using Quick Replies and an Action Node. This approach keeps data collection structured and avoids asking for Boolean or Select-style answers through typed input.

Mark the Form as Completed

After the user submits the required information, the flow sends a thank-you message and uses an Action Node to assign the completion tag. From that point on, future flows can detect that the form has already been filled out.

Continue to the Final Offer or Resource

Once the information is collected, the flow continues to the next node and sends the free course download link. This creates a smooth experience for new users while keeping repeat users from unnecessary repetition.

Part 02:

** Video 9-2 **

Limiting Repeated Invitations

The video also includes another useful pattern. Before sending an invitation to join an Instagram channel, a Condition Node checks a number field called insta_channel_invite_count.

If the field value is below the allowed limit, the invitation is sent and an Action Node increases the count by one. If the user has already reached the limit, the invitation is skipped.

This same structure can be reused for follow requests, Telegram channel invites, or any repeated call to action that should be shown only a limited number of times.

What You Learn from This Video

By the end of this tutorial, you will understand how to combine User Input, Action, and Condition Nodes to avoid duplicate form requests, improve user experience, and control repeated invitations in a clean and maintainable way.