Connector functions are configured requests defined on connectors that apps can utilized for sending and receiving data to the source of the connector. They abstract over the specifics of SQL or HTTP to present a standard input and output signatures composed of known variable types. For example a function 'Get Work Orders' might have a signature such as:
INPUTS:
1. Status (string)
2. Customer (string)
OUTPUTS:
1. Array of work orders
- Delivery date (date)
- Part ID (string)
- Part count (number)
App editors can use these functions in apps without worrying about complex issues such as authentication, networking, how to write queries, HTTP headers, etc. Defining how the inputs are used to retrieve the data, is different for SQL and HTTP connectors.
All HTTP and SQL response payloads are limited to:
- 20mb for Cloud Connector Host
- 50mb for On-Prem Connector Host
If exceeded, a "400 PayloadSizeLimitReachedError" error will be returned.
| Name | Description |
|---|
| Name | The name of the connector |
| Is Saved | Once a connector function is saved the inputs and outputs can be modified only if the connector function is not being used by an App |
| Where Used | List of apps using a particular connector function |
| Inputs | The composition of variable types an app must provide to call the connector function. Data types include: Text, Integer, Float, Boolean, Datetime. |
| Outputs | The composition of variable types an app can expect to receive from the connector function. Data types include: Text, Integer, Float, Boolean, Datetime and arrays of these data types. |
| Activation Status | A boolean that determines whether the connector function is active or deactivated |
| Description | A text description provided by the user who created the function (optional) |
| Field | Description |
|---|
| Use multiple rows | A boolean value that indicates whether the expected output is a single object matching the defined outputs, or an array of objects matching the defined ouput. |
| Query | The SQL query used to retrieve the data. The query can utilize connector inputs in its definition. More on SQL queries |
| Field | Description |
|---|
| HTTP Request Method | One of: GET, HEAD, POST, PUT, PATCH, DELETE more info |
| Authentication | If the authentication is unset at the connector level, it can be set at the function level. |
| Request Headers | A list of request header key/value pairs. These values can utilize input values. |
| URL Path | The path portion of the HTTP request. The path can utilize input values. |
| Query Parameters | A list of key/value pairs that are added to the query portion of the request URL. These values can utilize input values. |
| Request Body | The request body can be one of four types: JSON, form URL-encoded, plain text or XML. The request body can utilize input values. |
| Response Body | Whether the response body is JSON or XML. This setting determined how extracts are used to determine output values. |
| Outputs extractors | For HTTP connectors each output must also define the extractor for retrieiving the data from the body, header or cookie of the HTTP response. |
| Encoding Settings | For HTTP connectors, function input for text data type can have a custom encoding schema which allows escaping non reserved characters. |
| Name | Description |
|---|
| Name | The name of the connector |
| Read only | Read-only connector functions are used by published apps which cannot be modified. Users with the right permissions can test the read only connector function. This states the app and the version of the app using the read-only connector function |
| Inputs | The composition of variable types an app must provide to call the connector function. Data types include: Text, Integer, Float, Boolean, Datetime. |
| Outputs | The composition of variable types an app can expect to receive from the connector function. Data types include: Text, Integer, Float, Boolean, Datetime and arrays of these data types. |
| Activation Status | A boolean that determines whether the connector function is active or deactivated |
| Description | A text description provided by the user who created the function (optional) |
