> 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/inbound-api/using-the-inbound-api-connector-with-patchworks-services/adding-a-patchworks-service-for-an-inbound-api-connector/add-a-default-service.md).

# Add a default service

## Introduction <a href="#introduction" id="introduction"></a>

This page is **part 1** of of the instruction set for [adding a Patchworks service for an Inbound API connector](/product-documentation/patchworks-services/inbound-api/using-the-inbound-api-connector-with-patchworks-services/adding-a-patchworks-service-for-an-inbound-api-connector.md):

| Part # | Link to instructions                                                                                                                                                                                                                             |
| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **1**  | **Add a default service**                                                                                                                                                                                                                        |
| 2      | [Configure service settings](/product-documentation/patchworks-services/inbound-api/using-the-inbound-api-connector-with-patchworks-services/adding-a-patchworks-service-for-an-inbound-api-connector/configure-service-settings.md)             |
| 3      | [Set the service trigger schedule](/product-documentation/patchworks-services/inbound-api/using-the-inbound-api-connector-with-patchworks-services/adding-a-patchworks-service-for-an-inbound-api-connector/set-the-service-trigger-schedule.md) |
| 4      | [Define field mappings](/product-documentation/patchworks-services/inbound-api/using-the-inbound-api-connector-with-patchworks-services/adding-a-patchworks-service-for-an-inbound-api-connector/define-field-mappings.md)                       |
| 5      | ​[Activate the service](/product-documentation/patchworks-services/inbound-api/using-the-inbound-api-connector-with-patchworks-services/adding-a-patchworks-service-for-an-inbound-api-connector/activate-the-service.md)                        |

## The steps <a href="#prerequisites" id="prerequisites"></a>

Follow the steps below to add a default service.

**Step 1** \
Select **services** from the left-hand navigation menu:

![](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FHDsXl6T1fAn4CQZhVSJp%2Fadd%20default%20service%201.png?alt=media\&token=e5e83681-6485-4256-95d6-b84088180fce)

**Step 2** \
Click the **add new service** button:

![](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FiywXW4YNwai7NpFHPYH3%2Fadd%20default%20service%202.png?alt=media\&token=ff0716a5-7f9c-48c6-9436-33ca9fc2101c)

This option is also available from the bottom of any connector setup page, so if you’ve just finished [adding an Inbound API connector](/product-documentation/patchworks-services/inbound-api/using-the-inbound-api-connector-with-patchworks-services/adding-an-inbound-api-connector-with-a-custom-payload.md), you can go straight to service setup from there:​

![](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FhR6LVdwCXtVUpCupFPY7%2Fadd%20default%20service%202a.png?alt=media\&token=b190e770-d0ba-4746-9be7-225833fe1303)​

When you add a new service from a connector, this connector becomes the **source** automatically.

**Step 3** \
When prompted to choose a **source connector** (all configured connectors for your implementation are listed), select the **Inbound API** connector:

<div align="left"><img src="/files/oOWXF7wpjv0N3zcCDfoh" alt="" width="375"></div>

**Step 4**\
When prompted to choose a **destination connector**, select the connector that you want to receive incoming data from the API connector:

![](/files/s4lGhkiQ44CJkTEw7t5l)

{% hint style="info" %}
All configured connectors - excluding the one already selected for the **source** (i.e. the Inbound API connector) - are available for selection.
{% endhint %}

**Step 5**\
The **configure service settings** page is displayed - please see [configure service settings](/product-documentation/patchworks-services/inbound-api/using-the-inbound-api-connector-with-patchworks-services/adding-a-patchworks-service-for-an-inbound-api-connector/configure-service-settings.md) for guidance.


---

# 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/inbound-api/using-the-inbound-api-connector-with-patchworks-services/adding-a-patchworks-service-for-an-inbound-api-connector/add-a-default-service.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.
