Set up your first Meetyn automation

Start with one outcome

Choose a task: add a planning-sheet row when a meeting is published, or post a Discord notice when it is cancelled. Create the receiving webhook in your service. Check the workspace name in Meetyn, open Connections and add the destination. Never paste a secret webhook URL into a public invitation.

Review the shared data

Meeting events include the invitation URL, title, times, timezone, status and version. RSVP events add a response choice. Names, email addresses, descriptions and raw joining links are excluded from the payload, but following the invitation URL reveals its public details. Saving the connection authorizes sharing with that destination.

Test transport and the complete workflow

Use Send test to verify reachability. Then publish a disposable meeting after connection setup to obtain real fields. Test an edit and cancellation. Check Meetyn history and the destination’s execution history. Filter connection.test out of production actions because it contains no meeting object.

Plan for retries

Use eventId to avoid processing an event twice and meeting.id to identify a record. Use meeting.version to avoid overwriting a newer state with an older one. RSVP events describe activity, not final attendance. Pausing skips queued deliveries and resuming does not replay them. To change the destination, remove the connection and create its replacement.

Your questions, answered