Connect Meetyn to Make
Start a Make scenario when a meeting is published, changed, cancelled or finalized, or when a guest responds.
Create your receiving scenario
In Make, create a scenario and add Webhooks > Custom webhook as its first module. Create a webhook and copy the URL. Open the matching Meetyn workspace, choose Connections, select Make and paste the URL. Give it a clear name and select the events that should start this workflow. Save the connection.
Capture a test and map real fields
Put Make into listening mode, then use Send test in Meetyn. The test confirms reachability but does not include a real meeting. To map meeting fields, publish a disposable meeting in your test workspace after connecting it. Map meeting.title, meeting.startsAt and meeting.url into the next module. Timestamps use UTC; meeting.timezone identifies the organizer timezone.
Build a useful first workflow
Write one row per published meeting into a planning sheet. Filter on meeting.created so an RSVP does not create another meeting row. For changes, look up meeting.id and update the existing row. Keep eventId to prevent duplicate processing after a retry; use meeting.version to avoid replacing a newer state with an older one.
Understand the connection boundary
Meetyn sends events into your scenario. It does not install a public Make app or configure your scenario. Other services use the accounts you authorize inside Make. This release has no inbound Meetyn API for writing generated video links into invitations. Make usage limits and account permissions still apply.
Setup references
Your questions, answered
Is there a native Meetyn module?
Use Make’s Custom webhook module for this release.
Can I try Make without a paid plan?
Make offers a limited free plan. Check its current credits and scenario limits.
Will a test publish a real meeting?
No. Send test sends a connection-test message only.
Put the idea into practice.
Start with your occasion, a time and a place. Give your group one clear next step.
Explore invitation templates ↗