> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/patchworks-services/working-with-services/the-anatomy-of-a-service/service-destination.md).
# Service destination
## Introduction
The **destination** tab shows settings for the destination connector associated with this service - for example:
## Working with destination settings
Settings on this page are summarised below:
| Field | Summary |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Destination system | The system that is defined as the destination for this service (e.g. Peoplevox). When this service runs, data is pushed to this system. |
| Environment |
When a connector is added, you can choose whether it is to be used in a live environment, or for testing (also known as staging).
The environment is set at the connector level and cannot be changed here. If you need to use a different environment than the one specified here, make sure that a connector exists with the required environment setting and add a new service to use it.
|
| Time zone | Primarily used for time-based filters (e.g. syncing orders created after a given date/time). Patchworks uses UTC but a specific time zone can be applied here if needed. |
{% hint style="info" %}
If you make any changes to these settings, remember to save changes using the **save** button at the bottom of the page.
{% endhint %}
---
# 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://doc.wearepatchworks.com/product-documentation/patchworks-services/working-with-services/the-anatomy-of-a-service/service-destination.md?ask=&goal=
```
`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.