> For the complete documentation index, see [llms.txt](https://docs.sharelogic.com/unifi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharelogic.com/unifi/4.3/troubleshooting/integration-responses/unable-to-identify-message-name-from-request.md).

# Unable to identify message name from request

{% hint style="danger" %}
`Unable to identify message name from request`
{% endhint %}

Unifi needs to know what message it is dealing with before it can perform any processing. Identifying the message is one of the first operations it undertakes. If you receive this error, then Unifi has been unable to identify the message name from the inbound request.

Check the following:

* there should be a message name in the inbound request e.g. CreateIncident, UpdateChange, AddAttachment
* compare the inbound request structure with the identify message script on the integration. This script is how Unifi extracts the message name. If the script isn't aligned with the inbound payload structure, this error will be generated


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sharelogic.com/unifi/4.3/troubleshooting/integration-responses/unable-to-identify-message-name-from-request.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.