# Geckoboard integrations: datasets

> Geckoboard is a dashboard tool that shows a team's key metrics on screens and in the browser, pulling data from business apps, spreadsheets, databases…

**Canonical page:** https://tray.ai/connectors/geckoboard-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Geckoboard is a dashboard tool that shows a team's key metrics on screens and in the browser, pulling data from business apps, spreadsheets, databases, and custom datasets. Tray.ai connects to Geckoboard through the HTTP Connector, so your workflows can call the Geckoboard API alongside the rest of your stack.

## Use cases

### Datasets

Read and delete datasets in Geckoboard from any Tray.ai workflow. The Geckoboard API covers calls such as find or create a dataset and delete a dataset.

- Find or create a dataset
- Delete a dataset

### Dataset records

Update, delete, and manage dataset records in Geckoboard from any Tray.ai workflow. The Geckoboard API covers calls such as append data to a dataset and replace all dataset data.

- Append data to a dataset
- Replace all dataset data
- Clear all dataset data

## Challenges Tray.ai solves

### Keeping Geckoboard credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Geckoboard credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Geckoboard API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Geckoboard API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Geckoboard?

Yes. Tray.ai connects to Geckoboard through the HTTP Connector, which calls the Geckoboard API directly. Any call the Geckoboard API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Geckoboard?

The Geckoboard API uses basic authentication. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Geckoboard connector?

Geckoboard runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Geckoboard connector from the Geckoboard API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/