---
title: "Sandalwood: Ignition Connector"
slug: "sandalwood-ignition-connector"
updated: 2025-09-01T10:35:20Z
published: 2025-09-01T10:35:20Z
---

> ## 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.

# Sandalwood: Ignition Connector

Additional Configuration Required

          

This connector is a good starting point that implements a core set of the service's most common functions. You should expect to extend it by adding functions for the specific endpoints your workflow requires. Additionally, some configuration may be required in Ignition to establish a connection with Tulip. Please review our [connector framework](/r230/docs/connectors) to learn more about how to build and modify connectors in Tulip.

          
          

To download the app, visit: [Library](https://library.tulip.co/connectors/sandalwood--ignition-connector)

## Introduction

Sandalwood designs and executes strategic programs for manufacturers which reduce work-related risks to quality, productivity, and employee health. By providing knowledge, research, technology and resources, Sandalwood supports its clients in a comprehensive manner, delivering the best results.

## Purpose

Utilizing the Ignition to Tulip connector is crucial as it facilitates the integration of data between the two platforms. By leveraging this connector, users can directly access Ignition tags and queries within Tulip, maximizing the use of Tulip's advanced features while harnessing the wealth of data stored in Ignition. This integration improves workflows, enhances data-driven decision-making, and fosters collaboration across teams by centralizing critical information within the Tulip platform.

## API Doc

The following Connector Function highlighted in this document have leveraged [Sandalwood API Docs.](https://sandalwood.com/systems-integration/ignition-rest-api/)

## Pre-Requisites

Sign up for an account at Sandalwood and establish a custom project on your Ignition gateway. More information about this can be found in this [Documentation](https://inductiveautomation.com/exchange/2622/overview#).

## Tulip Connection Details

The following information would need to be configured on Tulip's HTTP connector.

Running On: Cloud Connector Host Host: Ignition Gateway IP Address Port: Ignition Gateway Port Number TLS: No Authentication: None

## Example Prebuilt Connector Functions

#### Get All Tag Paths

Get a list of all tag paths, providers, and folders inside the Ignition Gateway

#### Get Group Tag Paths

Search for tag paths by entering a tag provider, or folder returned data will show all tags that live in specified location.

#### Get Named Queries

Grab all Named Queries, Parameters, and Query Statements on the Ignition Gateway.

#### Get Simple Health

Used as a simple heartbeat to the Ignition Gateway returns the gateway time in UTC format.

#### Get System Health

Get performance metrics on the Ignition Gateway.

#### Get Tag Value Units

Grab multiple tag values with engineering units, high value, low value.

#### Get Tag Values

By providing tag paths we can gather tag values to display

#### Get Tag Values Tulip Friendly Output

Enter tag paths to return data in a Tulip Friendly output values can be stored as array or objects within Tulip.

#### Run Named Queries

Allows you to run any named query from the Ignition Gateway inside of tulip!

## Next Steps

- Learn more about [Sandalwood here](https://sandalwood.com/)
- Learn more about connectors [*here*](https://support.tulip.co/docs/what-are-connectors)

**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.