Module · Webhooks✅Knowledge checkCheck: talking to other systems3 questions · Pass at 60%1. Your workflow errors while handling an incoming webhook. What happens to the event?It is queued and retried by Expedify until the workflow succeedsIt is gone — the sender is fire-and-forget and its job is doneIt is held in the webhook log, and can be replayed from thereThe sender is notified of the failure and will send it again2. Why should a workflow that creates a record from a webhook be keyed on something in the payload?Because a payload's field order is not stable between deliveriesBecause Expedify requires idempotency keys on incoming webhooksBecause senders retry, so the same event may well arrive twiceBecause the record id must be generated before the trigger fires3. You are subscribing to outgoing webhook events. Which is right?All singular: contact.created, task.created, voice_call.createdAll plural: contacts.created, tasks.created, voice_calls.createdThey follow the table name, which is plural in every caseMixed — tasks and voice calls are plural, so do not guessCheck answers← Back to Webhooks, Debugging & Full BuildsNext topic →
