Supported integrations

Check the connections your enquiries depend on.

Connect the tools you use today. See what each check confirms, what it needs and where its coverage ends.

14-day Growth trial · No card required. Brand names describe compatibility, not partnerships or endorsements.

Start with your website

Find the form. Define a successful enquiry.

Website and form monitors are built into Alertira. Provider connections add specific checks where you need them.

Pages and landing pages

Check whether a public page responds, where it redirects and how long it takes. This verifies reachability; it does not complete a form, booking or purchase.

Authorised lead forms

Preview a page to find supported forms and suggest fields. The preview only reads the page: it never runs scripts or submits a form. Embedded and JavaScript-only forms may need manual setup.

After you authorise monitoring, a real check submits clearly synthetic values and looks for your chosen confirmation, thank-you page or supported receipt. Technical selectors stay in Advanced options.

Available today

Choose a connection with a clear purpose.

Each provider requires your own valid connection. Successful connection tests and successful customer journeys are shown separately.

Available

Webhook / API

Check that your chosen endpoint accepts a clearly marked test request.

  • Send a signed synthetic probe to the endpoint you authorise.
  • Check its response, response time and an optional expected JSON value.
Coverage limits

A probe is a real request. Use an endpoint that safely handles test data; a successful response alone does not prove every downstream action completed.

Connection requirements

Supply a public HTTPS endpoint, signing secret and expected response. Alertira signs the JSON probe with HMAC. Private network destinations are blocked.

Available

Slack

Bring confirmed incidents, escalations and recovery updates to your team.

  • Verify the connection with a visible test message.
  • Deliver incident and recovery notices to connected workspace or client channels.
Coverage limits

Slack is an alert destination. A successful delivery does not verify a customer's form or booking. Escalation is optional and configured separately.

Connection requirements

Connect an incoming webhook for the intended Slack channel, then run its connection test. Agency client connections stay scoped to the assigned client.

Available

HubSpot

Confirm form access and, when configured, that a new test submission arrived.

  • Check read access to your HubSpot forms.
  • Optionally match a new browser form submission to its exact HubSpot form and synthetic email.
Coverage limits

Reading HubSpot does not create or delete CRM data. A configured form monitor can create a synthetic lead by submitting your actual form; a connection check alone does not prove lead delivery.

Connection requirements

Provide a token with the required forms read scope. For submission receipts, select the matching form ID and same-client HubSpot connection in the monitor's confirmation settings.

Available

Calendly

Check that your booking page and event type are available to visitors.

  • Read the connected account and active event type, then check the public scheduling page.
  • Inspect bookable times in the next seven days; optionally require an available slot.
Coverage limits

No booking is created. A full calendar can be expected, so requiring available slots is a choice you make in the connection settings.

Connection requirements

Connect a Calendly API token and optionally choose the scheduling URL. The check uses read-only account, event-type and availability endpoints.

Available

Shopify

Check access to your shop and its public storefront, cart and checkout routes.

  • Read shop information through the connected Shopify Admin API.
  • Check responses from the storefront, cart page and checkout route, including safe redirects.
Coverage limits

No cart is changed, order created or payment attempted. Route availability does not prove that a shopper can complete a purchase.

Connection requirements

Connect the shop domain, permitted storefront URL and an Admin API token with access to the shop information query. Requests to public routes are read-only GETs.

Available

Google Analytics 4

Check that your tag appears in page source and your test event has a valid format.

  • Look for the configured measurement ID in public page source.
  • Validate an event locally and optionally with Google's non-reporting debug endpoint.
Coverage limits

This does not prove a real visitor's conversion was received in live GA4 reports. Tags inserted only by JavaScript may not appear in the source check.

Connection requirements

Provide the page URL, measurement ID and event settings. An optional Measurement Protocol API secret enables debug validation; it does not send a production conversion event.

One working monitor first

Start with the enquiry that matters most.

Try 25 monitors and 5 team seats for 14 days on Growth. Agency client workspaces and branded reports require the Agency plan.

Start free trial