## **🎯 What This Article Covers**

Some customers want to trigger a Search Atlas site audit automatically when an external form is submitted — for example, using a GoHighLevel form connected to a Make scenario that calls the Search Atlas API. This article clarifies what is and is not supported so you can design your automation correctly from the start.

## **🚫 Unsupported Workflow: End-User-Triggered Audits via External Forms**

Triggering a site audit on behalf of an end user through an external form submission is **not a supported workflow**. Specifically, the following scenario is not available:

- A prospect or client fills out a form (for example, in GoHighLevel).
- The form submission triggers a Make scenario.
- The Make scenario calls the Search Atlas API to initiate a site audit for that user's domain.
- The completed report is retrieved and sent to a third-party AI tool (such as Claude) for editing.
- The edited report is emailed to the end user automatically.

Even though this flow may appear technically plausible based on API documentation, it is outside the intended use of the audit system and will not function as expected. Attempting to build this workflow will result in errors, incomplete data, or unsupported behavior that our support team cannot troubleshoot.

## **✅ Supported Workflow: Account Owner Initiates Audits from the Dashboard**

Site audits in Search Atlas must be initiated by the **account owner** from inside the platform. This is the only supported method for starting a new audit. Log in to your Search Atlas account and navigate to the site audit area of the dashboard to configure and run an audit for a project under your account. This ensures audits are run with the correct account permissions, accurate project configuration, and full access to all reporting features.

## **⚙️ What the API Does and Does Not Support**

The Search Atlas API is designed to support account owners and their internal tools — not end-user-facing automation flows. Here is a general breakdown based on the intended design of the system:

- **Supported:** Retrieving audit data for projects already created and run under your own account.
- **Supported:** Reading report results programmatically to feed into your own dashboards or internal tools.
- **Supported:** Managing projects and accessing data on behalf of your own account.
- **Not supported:** Initiating new audits on arbitrary domains submitted by third-party users via external forms or automation triggers.
- **Not supported:** Acting as a middleman API layer that processes external user requests and triggers audits dynamically on demand.

If you are building an automation and need to confirm which specific API endpoints are available for reading audit data or managing projects, refer to the Search Atlas API documentation available within your account, or contact our team for guidance on what is achievable within the supported scope.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.