Yes, you can build this logic into a single journey using the Wait for Trigger element. It pauses a user's journey until they perform one of the events you configure, or until the waiting period expires.
Here is how to set up an onboarding task with a reminder:
Initial Message: Start your journey by sending the user a message prompting them to complete the first task (e.g. "Welcome! Your first task is to...").
Add 'Wait for Trigger': Immediately after the initial message, add a
Wait for Triggerelement to the canvas.-
Configure the element:
- Set the waiting period — how long the element waits before users fall through. The maximum is 90 days.
- Create a branch, give it a BRANCH NAME, and use ADD EVENT to pick the event that means the task is done (for example
task_1_completed). Use ADD CONDITION if you also need to filter on event attributes, and AND/OR if a branch needs several events. - You can define up to 3 event branches in one element.
- Optionally enable Fixed waiting period if users must wait the full duration even when the event fires earlier.
-
Connect the outputs:
- Event branch: connect it to the next primary step — e.g. the message introducing Task 2.
- "Not triggered" branch: this is the fall-through for users who did not trigger any of the branch events within the waiting period. Connect it to your reminder message (Push, Email, etc.).
Handle post-reminder actions: After the reminder on the "Not triggered" branch, add another
Wait for Triggerelement listening for the same event, so users who complete the task after the reminder rejoin the main flow.
Tip: make the waiting period realistic for the action you expect. A period that is too short pushes almost everyone down the "Not triggered" branch.
Comments
0 comments
Please sign in to leave a comment.