Troubleshoot meeting automations
Check whether an event was queued, accepted, retried or skipped before changing the workflow.
Read the delivery status
Pending means waiting; sending means an attempt is in progress; delivered means the endpoint accepted it. Retry indicates a temporary failure. Failed means a permanent error or exhausted attempts. Skipped usually means a connection is paused, removed or its workspace is unavailable.
Check the destination
In Make, check that the scenario is listening or enabled. In Zapier, check that the Zap is enabled and can use Webhooks. In Discord, verify the channel and webhook still exist. Share a connection name and failure time with support, rather than exposing the secret URL in a screenshot.
Separate delivery from later actions
An accepted webhook can still lead to a failed spreadsheet or calendar action. Inspect the receiving workflow’s run history and account permissions. Exclude test messages when mapping meeting fields. If duplicates appear, deduplicate by eventId before running the action.
Your questions, answered
Why was an old meeting not sent?
Only events generated after connection setup are eligible. Historical events are not imported.
Why did an RSVP create another meeting row?
Filter by event and look up meeting.id to update the appropriate row.
Can I replay a failed event here?
Manual replay is not included. Correct the connection, send a test and use a controlled new event to verify it.
Put the idea into practice.
Start with your occasion, a time and a place. Give your group one clear next step.
Explore invitation templates ↗