> For the complete documentation index, see [llms.txt](https://knowledgebase.fabricdata.com/xytech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.fabricdata.com/xytech/webhooks/tips-and-troubleshooting.md).

# Tips and Troubleshooting

### Email Notification of a failure

If you want to be notified by email or an alert pop-up when a webhook fails to send or receives an error response, you can set up an additional Event Trigger on the Export Adaptor Log with a condition set to trigger on receiving an error response status code (or whatever is the most appropriate trigger condition for your integration).

### Troubleshooting

**Trigger Condition Report** While testing an Event Trigger, it’s recommended to validate the trigger conditions by using the Event Trigger Report run from the modified record to check whether the trigger condition is met prior to saving the record. You can find this on the Action Menu - Document

**Test by Creating a Mock Web Service using Postman** There are many ways to create a mock Web service for testing. One of the easiest is to use tools such as Postman (<https://www.postman.com/>) or WireMock (<https://wiremock.org/>).

### Known Issues

#### URL Parameters not populated using GET method (v11.0)

In some scenarios, when configuring an Export Adaptor to include a URL parameter with a value that's a document field, the parameter fails get populated.&#x20;

A workaround that forces the parameter to be populated correctly, is to additionally add the field to the Alert Template of the Event Trigger. The Alert Template does not need to be configured to actually send the alert (by omitting any alert users). e.g.&#x20;

<figure><img src="/files/vlNEHysGg1AkIABKYcPs" alt=""><figcaption></figcaption></figure>

This issue is not present from v11.1 onwards.


---

# 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://knowledgebase.fabricdata.com/xytech/webhooks/tips-and-troubleshooting.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.