# URL as destination

This option allows you writeback into a URL. Inforiver sends the entire writeback table as a JSON to a HTTP endpoint. The endpoint could be a Power Automate workflow that receives the writeback table via the Inforiver JSON where further data processing would take place before storing into a destination such as OneDrive, SharePoint, Dataverse, etc. There are other workflows possible using this method. 

After navigating to the add destination page enter,

* Endpoint URL
* Required headers and value

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

<pre><code>{"headers":{"Connection":"close",
<strong>"Accept-Encoding":"gzip,deflate",
</strong>"Host":"prod-17.westus.logic.azure.com",
"Content-Length":"583206",
"Content-Type":"application/json"},
"body":{
"data":"\"IrScenario\",\"Productkey\",\"FirstBrand\",\"Category\",\"IrWritebackTimestamp\"\n\
"Base\",\"1\",\"Contoso\",\"Audio\",\"01\",\"2023-04-21 04:05:32 (UTC)\"\n"}}
</code></pre>


---

# Agent Instructions: 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:

```
GET https://docs.inforiver.com/working-with-inforiver/12.-data-writeback/destinations/url-as-destination.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.