Hi ​@josefinemk ,
One way to solve this is to assign a condition block and a TAG to the contact right after they click the button. Create a new TAG, for example named 'Message Sent', and add an extra action step to apply this TAG.
Before applying the TAG, insert a condition block to check if the TAG already exists. If it does, it means the user has clicked before, so the flow should stop here. If it doesn’t exist, it means it’s the first click, so you should add the TAG and schedule a 5-minute delay before sending the message.

Let me know if this helped you.

Hey ​@rogerioaraujo ,

That makes sense – the only thing I can’t wrap my head around is the fact that the tag is applied upon the click. So I can’t see how I can set up the condition block before the tag is applied..?

Everything else you’re mentioning with the 5 minute delay etc, I’ve already done! hmm…   

You can set the Instagram opt-in right after the click. Then, add the condition block, followed by the action block to add the TAG. It should look similar to the screenshot below.

I create a new automation for every single Reel I post on Instagram, all driving them to different articles  – and after clicking, they end up in the same automation. So the input is different every time but the final part is the same.

So if I set up a condition before checking if they’ve clicked and then not tagging them after, they wouldn’t get the final message at all, would they? The issue is more the fact that manychat triggers the action multiple time even though they’re further down the automation. As if them clicking the article again brings them back to earlier in the automation. Does that make sense?

I wish there was a feature I could turn on that says “only send message once” just like there are in most CRMs!

Hello ​@josefinemk ,

In ManyChat, each automation runs only once per user per post. That means once someone interacts with a post, they won’t see the same flow again on that post—but the flow will trigger again for that user on any new post.

To ensure each person receives your sequence only once, you can use TAGs and split your setup into two flows:

1. Trigger Flow (one per post)

• Condition: check if the user has the Message_Sent tag.

  • If yes: end the flow or send an alternative message for repeat interactions.

  • If no:

    1. Send the initial prompt (e.g., “Click the button to continue”).

    2. Start the Standard Flow.

2. Standard Flow (reused for all posts)

• Essential step: apply the Message_Sent tag as soon as the user enters this flow, marking them as already served.

• Include your full sequence of messages, links, and content that you want to deliver after the click.

How it works in practice:

• On the first click, the user doesn’t have the tag, so they enter the Standard Flow and receive the entire sequence.

• On subsequent clicks, the condition sees the Message_Sent tag and stops the flow before sending the same messages again.

This setup ensures each user experiences your welcome sequence only once, even if you point multiple automations to the same final flow.