> For the complete documentation index, see [llms.txt](https://docs.justransform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.justransform.com/development/connections/creating-a-connector.md).

# Creating a Connector

Before creating a connector, it is important to understand the architecture and components required before creating a connection.

1. To create a new connection within Justransform, click "**+**" within the Connections Module.&#x20;

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

The primary components of any connector created include the following:

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

**Connection Name:** Any common string uniquely identify your connection

**Emails to subscribe for failures**: List of email addresses to be notified in case of any exception occurred during the message transmission.

**Number of Outbound Concurrent Messages:** The system default is ‘0' which indicates the platform to use the platform default number of threads to be used. Unless you have specific license enabled, leave the value to '0'

**Retry on Failure(HH:MM:SS) and Interval**: The retry behaviour can be specified by specifying the the time and the interval of the retry. the default value of 00:00:00 will retry immediately

**Inbound Sync Response:** Use this ONLY for REST, SOAP, Oracle CMK and OTM based connection. you can specify a **Sync Response** message to be returned to the sender. The code to generate the response can manually entered or by loading [Scripts](https://justransform.atlassian.net/wiki/spaces/JTHELP/pages/2719884/Scripts) [Toolbar - Map Chain](https://justransform.atlassian.net/wiki/spaces/JTHELP/pages/18219434/Toolbar+-+Map+Chain) or a [Mapper](https://justransform.atlassian.net/wiki/spaces/JTHELP/pages/33057/Mapper)

2. Click **Save**.


---

# 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.justransform.com/development/connections/creating-a-connector.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.
