Skip to main content
All CollectionsHow-tosCertification Examples
Example Approach: Event Timers
Example Approach: Event Timers

In this article, we'll explore an approach to implementing PROMPTs and buffering a conditional trigger.

Yanni Hajioannou avatar
Written by Yanni Hajioannou
Updated over 2 weeks ago

Overview

As you build out your Tines stories, you may need user interaction mid-process for tasks like reviews, action validation, or other purposes. Combing the PROMPT function and conditional triggers is perfect for these scenarios.

Tines references

Before getting started, we recommend familiarizing yourself with the surrounding functionality this article covers:

Make it happen

Test a PROMPT

Prompts in Tines enable user interaction within your stories. Testing prompts ensures they function correctly, letting you verify user responses.

In this video, we show how to set up a PROMPT function within a send email action for a user to interact with (we emulate the interaction in this video via pasting the PROMPT URL into a browser).

Validate a PROMPT

Since using the PROMPT function enables feedback loops, we recommend adding a trigger action immediately after the prompt action to validate clicks; otherwise, the story may continue unchecked.

In this video, we set up a trigger action to check if the PROMPT URL was clicked by the end-user.

Remove duplicates from a PROMPT flow

To maintain the efficiency and accuracy of your story flow, it’s essential to remove duplicate submissions. Deduplication helps to prevent repetitive actions and ensures that your automation only processes unique data entries.

Apply a delay with event timers

After the trigger condition isn't met, we can add in a delay so the user has an opportunity to click on the PROMPT link. In a real world example, users aren't going to have 0 seconds to click on something before action is taken.

In this video, we create a delay with seconds, but we can always bump that number up as we are developing stories for production.

Review the results

Whenever you have situational logic that relies on a user interaction - it's good to do a final check.

In this video, we'll see what happens if the user clicks the email and how the delay event data flows/stops at the dedup.

Did this answer your question?