A connector is a configuration that defines how an app can read and write to an external data store through the functions defined by that connector. Only users with the connector admin role can create, edit and delete connectors. Tulip supports two types of data sources for connectors:

  • HTTP Connector - A datasource that is accessed through the https protocol.
  • SQL Connector - A database that is accessed with an SQL query.

Connectors and application lifecycle

Because connectors connect Tulip to outside data sources, it is important that users are able to set up multiple Connector Environments based on the publication lifecycle of the app version implementing a given connector. For example, if the app writes to the data source, a user would want the development version of an app to connect to a different database than the published version of the app. If the connector only implements read only functions, the connection might be the same for development and production versions. Tulip allows for 3 different ways to configure environments for a connector:

  1. Production Only - the same connection configuration is used for development versions, published version, and pending version.
  2. Production & Development - Production is used for published apps, and the development and pending version of apps use the development configuration.
  3. Production, Staging & Development - Production is use for published apps, development is used for development, and staging is used for apps that are pending approval.


NameThe name of the connector. Usually this will be the name of the data source the connector is connecting to.
DescriptionAn optional blurb of text telling other users the intended use or other key info about the connector.
ImageAn optional image representing the connector
Where UsedList of Apps using a connector
Activation StatusA boolean that determines whether the connector function is active or deactivated
Connector Environments Configuration1 of the 3 options for connector environment configuration
List of connector functionsThe connector functions for this connector


QA-T127Connectors : 01 - Clone, Edit, Delete, Restore Connectors
QA-T147SQL Connectors : 01 - Add a SQL Connector
QA-T148SQL Connectors : 02 - Add Function to SQL Connector
QA-T239HTTP Connectors : 01 - Add an HTTP Connector
QA-T240HTTP Connectors : 02 - Add several functions to HTTP Connector
QA-T567Dev Mode - Environment and Player Settings
QA-T581Connectors : 02 - Environment Configuration
QA-T656Workspaces : 08 - Connectors across the workspaces
QA-T725HTTP Connectors : 04 - Extractors for Non-Json Formats and Cookies
QA-T726SQL Connectors : 03 - Verify different SQL Servers
QA-T727HTTP Connectors : 03 - OAuth 2 Admin/Operator
QA-T728HTTP Connectors : 05 - Non-2xx Responses
QA-T729HTTP Connectors : 06 - HTTP Connector Functions perform the same with TLS on/off
QA-T731HTTP Connectors : 07 - OAuth 2 send request data as JSON
QA-T793Connectors : 03 - Filtering and searching connectors
QA-T794Connectors : 04 - "Where Used" app links
QA-T795Connectors : 05 - "Where Used" app links on different workspaces
QA-T796Connectors : 06 - Connector functions search and "Where Used" app links
QA-T802Connectors versioning : 01 - Connectors in published apps
QA-T810HTTP Connectors : 03 - OAuth 2 Admin/Operator
QA-T840HTTP Connectors : 08 - URL encoding function


PLAT-8763 (406)Ability to consume by pre-configured unit of measure (UoM) quantities such as weight, volume, etc.
PLAT-8779 (58)Allow integration of advanced IIoT end-points for interaction with equipment and collaboration with devices
PLAT-8781 (57)Allow integration of simple IIoT end-points for data input and capture
PLAT-8793 (836)Ability to retrieve information from external a system of record so that Apps can get the required information for execution fo a specific process step.
PLAT-8840 (456)Ability to define and dispatch work orders for the different segments of the manufacturing operation.
PLAT-8858 (215)Ability to receive production order from a system of record with associated material list
PLAT-8869 (856)Continuous signing sessions require two signature components for first signing but only one (secret) component for subsequent signings
PLAT-8870 (100)Ability to retrieve, examine, and view batch/lot and material attributes used in the processing step (e.g. potency), from external source.
PLAT-8908 (396)Ability to track and list materials for a work order for reconciliation.
PLAT-8909 (394)Ability to track unloading of material from a load-carrier
PLAT-8911 (393)Ability to track loading of material to a load-carrier and its location within the load carrier. Ie. material in a well, plate, flask, tank, tote, etc.
PLAT-8913 (392)Ability to track materials handled in load-carriers.
PLAT-8923 (405)Ability to manage and track material consumption as part of a process step. Material consumption may include processing, weighing, dispensing, etc.
PLAT-8925 (390)Ability to track materials associations using the material tracking model. Ie. track physical material in tray location, trays in batches (Cohorts).
PLAT-8927 (389)Ability to track material movement history. Ie. path of material in the production process
PLAT-8928 (388)Ability to track material inventory and its physical location.
PLAT-8954 (857)Ability to print configured labels for sample materials
PLAT-8969 (428)Ability to adjust batch/lot and material quantities related to sample plan execution
PLAT-8971 (354)Ability to track material association to work order and production order at all levels of material tracking hierarchy
PLAT-8976 (350)All material tracking history will include context of material hierarchy levels
PLAT-8979 (363)Ability to track and maintain forward and backwards batch/lot and material genealogy at all level of the material tracking hierarchy. Ie view, analyse and query material genealogy
PLAT-8981 (357)Ability to track material consumption and use at all levels of the material tracking hierarchy.