Skip to main content

You generate the enquiry.
Elara gets it to the client.

Connect website forms to the platform your client uses to follow up. Save the lead, send it onward and check delivery without forwarding every enquiry yourself.

  1. Your client’s websiteA visitor sends an enquiry.
  2. Saved in ElaraThe submission and delivery are tracked.
  3. Their connected platformThe enquiry reaches its next destination.

The right connection for each client.

Choose the client’s platform. Each connection has its own setup, permissions, and destination.

Jobber

App setup + account authorization

Create a client and attach an enquiry note.

Register the workspace’s developer app, then authorize each client’s account.

Housecall Pro

API key

Send a lead to Job Inbox.

Requires an eligible account plan and API Leads access.

ServiceTitan

Tenant and application credentials

Create a booking request.

Configure the tenant, app credentials, environment, and booking provider. A booking request is not a scheduled job.

HighLevel

Private integration token + location

Create or update a contact and add an enquiry note.

Use the client’s sub-account token and the correct Location ID.

JobNimbus

API key + workflow settings

Create a contact with the enquiry details.

Choose the exact contact workflow and status required by the client’s account.

Capture first. Deliver next.

The website enquiry is saved in Elara, with CRM delivery tracked separately from email notifications. A problem with a connected platform should not become a lost form submission.

See what happened.

Review delivery history, paused connections, and failures that need attention. Use test enquiries to confirm the destination before relying on the connection.

Connect a workflow instead.

An outgoing webhook can pass an enquiry to a compatible workflow. A successful webhook response confirms receipt; the receiving workflow owns the next action.

Set up once. Verify the whole journey.

  1. 01

    Choose the platform

    Open Client Settings → Integrations for the correct client.

  2. 02

    Connect the account

    Follow the provider-specific credential or authorization steps.

  3. 03

    Send a test enquiry

    Confirm the destination, fields, and delivery history before using the connection.

Owners and admins configure connections. Each real account needs its own credentials or authorization and a successful test enquiry. Provider plans and permissions apply.

A little more detail.

Ask us something else
Do I need a different setup for every platform?

Yes. Some platforms use API credentials and others require account authorization. Elara provides provider-specific setup rather than treating every connection as the same webhook.

What happens if the CRM is unavailable?

The enquiry is retained in Elara and delivery status is recorded. Retryable failures can be retried; uncertain writes may need review to avoid creating duplicate records.

Does connecting an account send all my old enquiries?

No. New connections do not automatically backfill older submissions. Test the connection and confirm where new enquiries should go.

Give your agency room for more clients.

Give your next client a connected home for their website, SEO, content and social. Give yourself the capacity to take on the one after that.