What is your goal?
Hi everyone, I’m having trouble with my scheduling scenario. Currently, my flow searches for Google Calendar events and sends a confirmation via Webhook to my chatbot (BootConversa).
The issue is that every time the scenario runs, it picks up the same events over and over again (even the ones already processed). This leads to two main problems:
1 - Excessive consumption of operation credits.
2 - The client receives multiple confirmation messages for the same appointment.
I’ve tried using date filters like Start Date > {{now}}, but this doesn’t stop Make from reading today’s appointments repeatedly in every cycle. I need a logic that tells Make: "If this event has already been sent once, do not send it again.
Could anyone guide me on how to create a “lock” or a filter that identifies only new appointments that haven’t passed through the flow yet? Should I use a “Search” vs “Watch” module or some kind of flag in the event description?
Thanks in advance!
What is the problem & what have you tried?
I’ve tried using date filters like Start Date > {{now}}, but this doesn’t stop Make from reading today’s appointments repeatedly in every cycle. I need a logic that tells Make: "If this event has already been sent once, do not send it again.
I have already used the following filters:
condição
start
Datetime operators: Later than
AND
Status
text operators; Equal to
confirmed
Share a link to your scenario
blob:https://us2.make.com/e8d5514c-3404-47e1-86cc-c2a768cfbd80

