--- title: "Tech Partner Collection" slug: "tech-partner-collection" updated: 2023-12-19T20:34:55Z published: 2023-12-19T20:34:55Z canonical: "support.tulip.co/tech-partner-collection" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.tulip.co/llms.txt > Use this file to discover all available pages before exploring further. # Tech Partner Collection *Get started with our tech partner integrations with this collection of curated technology partner content* ## Purpose Tulip is an open ecosystem. As an open ecosystem, we believe in providing openness and accessibility when it comes to innovating solutions. To do this, we support connectivity to a wide range of partners and devices. We work with technology partners to equipt users with different technology and tools to develop powerful solutions for their diverse frontline processes. This collection provides a high-level walkthrough of some of the use cases and integrations we've developed with our partners. ## Ways Technology Partners Integrate with Tulip Technology partners integrate in a variety of ways with Tulip, such as: - **Connector Functions (SQL or HTTP)**: Some technology partners enable streamlined integrations via our Connector and Connector Function capabilities. [*Check out our connector articles for more information*](https://support.tulip.co/docs/connectors) - **Edge Integration**: Technology partners may offer advanced connectivity at the edge. We tap into this via third party or Tulip edge devices. - **Machine Connectivity**: Whether it is via our Machine API, MQTT, or OPC-UA, we enable a connection to a variety of machines and devices to support the tools you have. [*Check out our edge connectivity docs for more information*](https://support.tulip.co/docs/edge-connectivity) - **Custom Widgets**: Technology partners can integrate via [custom widgets](https://tulip.co/developer/custom-widgets/) to transform the Tulip experience. [*Check out our custom widgets overview for more information*](https://support.tulip.co/docs/custom-widgets-overview) ## Example Technology Partner Use Cases Technology partners come together to drive a variety of use cases beyond core Tulip functionality such as: - **Machine Monitoring**: Using tech partners, such as[Litmus Automations](https://tulip.co/partners/litmus/), enables connecting to thousand of machines and aggregating machine metrics with simplicity. This streamlines monitoring hundreds, if not thousands, of machines - **Scheduling and Order Execution**: So many business processes are reliant on Enterprise Resource Planning (ERP) software. Content, such as our [*NetSuite integration bundle*](https://tulip.co/library-search/?desc=netsuite), make it easier to pass data to and from NetSuite. This data communication results in a clearer source of truth for scheduling and order execution use cases, as well as inventory details. - **Quality Inspection**: Technology partners, such as [LandingAI](http://tulip.co/partners/landingai), [Instrumental](https://tulip.co/partners/instrumental/), and [Elementary](https://tulip.co/partners/elementary/), enable additional vision inspection use cases to showcase the art of the possible for a variety of industries. - **Product Lifecycle Management**: Product Lifecycle Management (PLM) systems are fundamental to many businesses' day to day processes. PLMs can provide centralized management of bills of material, revisions, and effectivity dates. Integrating these systems with Tulip streamlines enabling frontline operations teams to use this same source of truth as they perform their tasks. See more with our [*duro integrations*](https://tulip.co/library-search/?desc=duro) and our [*onshape integrations*](https://tulip.co/library-search/?desc=onshape) These technology partners can also work in harmony across a single end-to-end use case. See below for an end-to-end quality example: ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28261%29.png) In the above example, Tulip acts as a core frontline operations platform to ingest machine and tooling information, integrate with ERP data, interact with vision inspection, and output this information to a data cloud for further analysis. Together, Tulip and technology partners can work together to provide a powerful end-to-end solutions for your unique challenges. ## Featured Technology Partner Content on the Library ### **[Unified Namespace Example](https://tulip.co/library/videos/unified-namespace-example-with-highbyte/)** [![](https://tulip.widen.net/content/ylibkvzlc4)](https://tulip.co/library/videos/unified-namespace-example-with-highbyte) This video walks through a simple example of a unified namespace [powered by MQTT, HiveMQ](https://tulip.co/library/videos/mqtt-powered-by-hivemq/), and HighByte. The concept is a growing trend for connecting devices and contextualizing their information across the entire enterprise. Our partnership with HighByte also extends to [unit tests and overview videos](https://tulip.co/library-search/?desc=highbyte&attributes=technology-partners) as well ### **[Data Pipeline Example](https://tulip.co/library/videos/end-to-end-data-pipelines-example/)** [![](https://tulip.widen.net/content/ay6x7zctof)](https://tulip.co/library/videos/end-to-end-data-pipelines-example/) The Data Pipeline example video walks through a variety of ways to send data from Tulip to other databases, Data Warehouses, and more. This example can be accomplished via Fivetran, Tulip Automations, and Snowflake. The accompanying [Fivetran integration video](https://tulip.co/library/videos/fivetran-integration/) and [Knowledge Base Article](https://support.tulip.co/docs/en/fivetran-integration) provide additional details. ### **[SAP Integration](https://tulip.co/library/videos/sap-integration-with-bow-stern/)** [![](https://tulip.widen.net/content/xbbmnkh1yi)](https://tulip.co/library/videos/sap-integration-with-bow-stern/) This example video walks through Bow&Stern's SAP integration platform: Low Touch SAP Integration. Integrating with ERPs can be complicated; partners such as Bow&Stern simplify this. ### **[NetSuite Integration](https://tulip.co/library/connectors/netsuite-integration/)** [![](https://tulip.widen.net/content/f7ktrd7guj)](https://tulip.co/library/connectors/netsuite-integration/) This NetSuite integration includes templates for many standard Enterprise Resource Planning (ERP) integrations, such as updating inventory and tracking order completions. This connector takes out a lot of the manual work in ERP integrations. ### [**Banner Lighting Integration**](https://tulip.co/library/apps/banner-unit-test/) [![](https://tulip.widen.net/content/yjxs3nlyst)](https://tulip.co/library/apps/banner-unit-test/) Integrating with devices can be difficult; it can require experience with edge devices and NodeRed workflows. The Banner lighting integration unit test contains everything you need for testing and connecting Banner devices to streamline getting up to speed with these devices. ### [**Snowflake Connector**](https://tulip.co/library/connectors/snowflake-connector/) [![](https://tulip.widen.net/content/f3h0djjvay)](https://tulip.co/library/connectors/snowflake-connector/) Snowflake integratation via their SQL REST API can require several layers of authentication. The Snowflake connector and related support article walk through this step by step, courtesy of Spaulding Ridge. ### [**Wearables Integration: ProGlove**](https://tulip.co/library/apps/proglove-functional-example/) [![](https://tulip.widen.net/content/prcqhumaws)](https://tulip.co/library/apps/proglove-functional-example/) ProGlove enables an augmented operations experience for barcode scanning and more. This unit test walks through how to get started step by step. ## Further Reading *[In addition to the featured content listed above, continue to check out all library content tagged to technology partners for more solutions](https://tulip.co/library-search/?attributes=technology-partners)* **Connectors** **Connectors** enable real-time connectivity between your Tulip solution and a transactional system (e.g. an ERP). The output of a Connector Function can be used in Tulip Apps, Automations, and Functions. - **HTTP Connectors** utilize HTTP API endpoints. - **SQL Connectors** can enable connectivity with certain SQL databases. - **MQTT Connectors** can connect to MQTT brokers for machine monitoring. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/connector.gif) **Connector Function** **Connector Functions** are individual operations to interact with an HTTP or SQL Datasources. Connector Functions can have inputs and outputs, and can be called from: Triggers, Functions, Automations, and AI Agents. Once pulled, data can be used throughout your applications.