What is your goal?
I’m running an inbound Vapi assistant that calls a Make.com webhook to pull applicant data from monday.com at call start.
The data now pulls correctly, but during a single call the webhook fires multiple times instead of once. This appears tied to Vapi server messages / tool calls rather than Make retries.
Has anyone handled a similar setup (voice/AI platform → Make → CRM) and found a reliable way to:
ensure the webhook logic executes only once per call, or
gate / dedupe repeated executions cleanly on the Make side?
Looking for architectural or Make-native patterns (filters, data stores, flags, etc.), not workarounds.
What is the problem & what have you tried?
I have an inbound voice AI (Vapi) calling a Make Custom Webhook, which then pulls data from monday.com.
The data now pulls correctly, but during a single phone call the same webhook fires multiple times, even though I expect it to run once per call.
This does not appear to be Make retries — it looks tied to repeated inbound webhook requests from Vapi during the call (likely multiple server/tool messages).
I’m trying to understand the correct Make-native pattern to ensure the logic executes only once per call (e.g. filtering, locking, data store flags, execution gating), without relying on hacks or time delays.
Error messages or input/output bundles
there are no errors, its just consistenly running without stopping
Screenshots (scenario flow, module settings, errors)