How Can I Prevent Duplicate Webhook Executions When a Mobile App Retries a Request?

Our team at AppVerticals is using Pabbly Connect in a custom app development project. The mobile application sends an event to a Pabbly webhook whenever a user completes an order.

The problem occurs when the user has an unstable connection. If the app does not receive a response quickly, it retries the request. Pabbly then receives the same event more than once, which can create duplicate CRM records and send duplicate notifications.

Each request already contains a unique event_id, an order_id and a timestamp. I tried adding a filter based on the event ID, but I could not find a reliable way to check whether that ID was processed during an earlier workflow execution.

What is the recommended way to make a Pabbly Connect webhook workflow idempotent? Can Pabbly store and check each event_id before running the remaining actions, or should this logic remain in the application backend?

Expected result: each event should be processed only once, even when the mobile app retries the webhook request.

Hello Saad,

Thank you for reaching out and for the detailed explanation.

To check the workflow and Task History, please share the workflow name and workflow URL with us.

We assure you that we will only review the setup and will not make any changes to your workflow.