> For the complete documentation index, see [llms.txt](https://docs.plumvoice.com/insight/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plumvoice.com/insight/data-integration/soap-integration.md).

# SOAP Integration

Users need to build their SOAP service so that it has a single plumEval method that accepts the above parameters and returns a string value that will be stored as the answer for the webservice question in your survey. Users can branch on this returned value using the webservice question's skip logic options; it is also possible to branch on a SOAP fault.

## **Handling a SOAP Fault**

The webservice question type for SOAP is architected so that if a SOAP webservice returns a SOAP fault, then Plum Insight stores the value 'SOAPFault' as the answer to the webservice question.

Users can utilize this value in the skip logic for the webservice question to branch on a SOAP fault returned from their service.

## **Handling Audio Files**

Comments provided over the phone by end-users for the comment question type are in the WAV format appear as Base64 encoded strings in the answers array. Users who want to save these recordings in their SOAP service should review the answers array for Base64 encoded strings. These strings can be decoded into WAV files of the audio recordings.


---

# 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.plumvoice.com/insight/data-integration/soap-integration.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.