Kepler integration

Two systems, one handshake

Mesa and Kepler are designed as a pair: the CMS carries the content, the CRM the enquiries. The integration connects both without maintaining content or keys twice.

Set up in minutes

Under Settings → Integrations you store the address of your Kepler instance and an access key — a connection test immediately shows whether everything stands. The key is stored encrypted and never leaves the server.

Forms directly in the entry

After that, the “Form” field type is available: in any entry, editors pick from a list which Kepler form should appear on the page — with name and field count. If the connection is temporarily unreachable, the field cleanly degrades to a text input instead of blocking.

The reverse direction too

Kepler can load choice options (for example your services) directly from Mesa collections — one source, no double maintenance.