# Ometria integrations

> Call the Ometria API from any Tray.ai workflow with the HTTP Connector.

**Canonical page:** https://tray.ai/connectors/ometria-integrations/
**Categories:** Marketing
**Connects through:** HTTP Connector

## Overview

Ometria is a customer data and marketing platform for retailers, combining contact, order and product data to run personalised email and messaging campaigns. Tray.ai connects to Ometria through the HTTP Connector, so your workflows can call the Ometria API alongside the rest of your stack.

## Use cases

### Push

Read push in Ometria from any Tray.ai workflow. The Ometria API covers calls such as push objects and list push errors.

- Push objects
- List push errors

### Contacts

Read contacts in Ometria from any Tray.ai workflow. The Ometria API covers calls such as list contact collections and list contacts.

- List contact collections
- List contacts
- Get a contact

### Orders

Read orders in Ometria from any Tray.ai workflow. The Ometria API covers calls such as list orders and get an order.

- List orders
- Get an order

### Products

Read products in Ometria from any Tray.ai workflow. The Ometria API covers calls such as list products and get a product.

- List products
- Get a product

### Lists

Read lists in Ometria from any Tray.ai workflow. The Ometria API covers calls such as list lists and get a list.

- List lists
- Get a list
- Get list changes

### Custom fields

Read, create, update, and delete custom fields in Ometria from any Tray.ai workflow. The Ometria API covers calls such as list custom fields and create a custom field.

- List custom fields
- Create a custom field
- Update a custom field

## Challenges Tray.ai solves

### Keeping Ometria 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 Ometria 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 Ometria 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 Ometria 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 Ometria?

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

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

The Ometria API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Ometria connector?

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