Meeting automation that starts with your group
Connect Meetyn to Make, Zapier and Discord. Turn published plans, changes and responses into useful updates for your team.
One workspace, the right destinations
Connections belong to the workspace you are using. An owner or admin chooses a destination and the events it receives. A volunteer workspace can post to its Discord channel while a business workspace sends updates into an automation workflow. Editors can keep organizing meetings without gaining access to connection credentials.
Choose meaningful moments
Available events are meeting published, meeting changed, meeting cancelled, poll finalized and RSVP received. A poll becomes a scheduled meeting when its organizer confirms a time. Native-app and website actions use the same service, so the source device does not change which connections receive an event. Existing meetings are not replayed when a connection is added.
Know what was delivered
Send a test, then refresh Recent deliveries. Delivered means the destination accepted the request, not that every later step succeeded. Temporary failures retry up to five attempts. Pausing skips queued deliveries and cannot recall messages already sent. Delivery may take several minutes or longer if the scheduler is delayed.
Your questions, answered
Who can manage connections?
Workspace owners and admins. Webhook URLs are encrypted at rest and are not returned to the settings screen.
Are guest names sent?
No. RSVP events contain the response choice without a name, email address or guest identity token.
Does Meetyn need my Google or Zoom password?
No. These connections use webhook URLs from Make, Zapier or Discord.
Put the idea into practice.
Start with your occasion, a time and a place. Give your group one clear next step.
Explore invitation templates ↗