Manage
Connect your gym website to the tools you use
Add a supported booking embed to a page. On eligible plans, send form submissions to an HTTPS endpoint through a webhook. Check each provider's setup and test the complete visitor path before relying on it.
- Booking embeds keep your existing scheduler visible on the site
- Form webhooks send new submissions to an endpoint you control
- Payment and CRM connections depend on the tools and plan you use
Launchmiga
Manage
Check available options
Account-scoped settings
Why it works
Check available options
Use the product settings to confirm which embed and webhook options are available for your account.
Account-scoped settings
Set up the webhook for the site and form that should send submissions.
One-way form delivery
A form webhook sends a submission out. It does not bring payment or booking status back into the inbox.
Test your webhook
Connect a webhook only when the receiving system accepts the payload and you can verify delivery.
How it works
Open integrations settings
Choose a booking embed or the form webhook settings for the site that needs the connection.
Map fields once
For a webhook, enter the HTTPS endpoint and match the form fields to what that endpoint expects.
Test with a live submission
Submit a test form or booking and verify it arrives in the intended tool before using the page publicly.
Who this helps
Show your booking tool
Embed a supported scheduler and check the booking flow on mobile.
Send form submissions
Use a form webhook on an eligible plan to POST new submissions to your own HTTPS endpoint.
Check the receiving system
Confirm field names, permissions and error handling with the provider before sending real member data.
Integrations should reduce tabs, not add another login
Start with the exact handoff you need. A booking embed lets visitors use your existing scheduler. A form webhook sends a new enquiry to an external endpoint. These are separate options and neither automatically synchronizes your entire CRM or payment system.
For webhooks, choose the receiving HTTPS URL, map the fields it expects and submit a test form. Check that the record arrives with the correct values. If a provider changes its API, update the receiving integration and test again. Availability can depend on your plan.
FAQ
Which integrations are native?
Do not assume a named CRM or payment provider has a native two-way connector. Check the current settings in your account. Booking embeds and form webhooks are different from a provider-specific integration.
Can I send forms to my CRM?
A form webhook can send submissions to an HTTPS endpoint on an eligible plan. Your CRM or integration service must accept the payload. This does not create an automatic two-way CRM sync.
Do integrations require developers?
A booking embed usually needs a link or embed code from your provider. A webhook needs an HTTPS receiver and may need technical help to map fields and handle errors.
Will an integration break my site?
Site rendering stays independent. Integration failures affect sync, not public page uptime.
Build the site around the tools you already use
Start with a clear website, then add a supported booking embed or form webhook when you need it.
Browse website templates