# Vena Solutions integrations: ETL templates

> Create a job, export intersection values and export a Vena Table in Vena Solutions. Connect Vena Solutions to the rest of your finance stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/vena-solutions-integrations/
**Categories:** Finance
**Connects through:** HTTP Connector

## Overview

Vena is a financial planning and analysis platform built around Excel, used for budgeting, forecasting, consolidation and reporting on a central data model. Tray.ai connects to Vena Solutions through the HTTP Connector, so your workflows can call the Vena Solutions API alongside the rest of your stack.

## Use cases

### ETL templates

Read etl templates in Vena Solutions from any Tray.ai workflow. The Vena Solutions API covers calls such as list ETL templates and get an ETL template.

- List ETL templates
- Get an ETL template

### ETL jobs

Read, create, and delete etl jobs in Vena Solutions from any Tray.ai workflow. The Vena Solutions API covers calls such as start a job with data and start a job with a file.

- Start a job with data
- Start a job with a file
- Create a job

### Model data

Read model data in Vena Solutions from any Tray.ai workflow. The Vena Solutions API covers calls such as export intersection values and export the model hierarchy.

- Export intersection values
- Export the model hierarchy

### Vena Tables

Read vena tables in Vena Solutions from any Tray.ai workflow. The Vena Solutions API covers calls such as list Vena Tables and get a Vena Table.

- List Vena Tables
- Get a Vena Table
- Export a Vena Table

## Challenges Tray.ai solves

### Keeping Vena Solutions 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 Vena Solutions 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 Vena Solutions 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 Vena Solutions 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 Vena Solutions?

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

### How does Tray.ai authenticate with Vena Solutions?

The Vena Solutions 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 Vena Solutions connector?

Vena Solutions runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Vena Solutions connector from the Vena Solutions 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/