# Arlo integrations: contacts and registrations

> Create a contact and update a registration in Arlo, and start a workflow when Arlo sends “Contact created”.

**Canonical page:** https://tray.ai/connectors/arlo-integrations/
**Categories:** Human resources
**Connects through:** HTTP Connector

## Overview

Arlo is training management software for course providers, covering events, registrations, contacts, online activities and orders. Tray.ai connects to Arlo through the HTTP Connector, so your workflows can call the Arlo API alongside the rest of your stack.

## Use cases

### Contacts

Read, create, and update contacts in Arlo from any Tray.ai workflow. The Arlo API covers calls such as list contacts and create a contact.

- List contacts
- Create a contact
- Get a contact

### Registrations

Read and update registrations in Arlo from any Tray.ai workflow. The Arlo API covers calls such as list registrations and get a registration.

- List registrations
- Get a registration
- Update a registration

### Events

Read events in Arlo from any Tray.ai workflow. The Arlo API covers calls such as list events and get an event.

- List events
- Get an event

### Arlo events

Start a Tray.ai workflow the moment something happens in Arlo. Arlo sends events such as contact created and contact updated to a Tray.ai webhook trigger.

- Contact created
- Contact updated
- Registration created

## Challenges Tray.ai solves

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

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

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

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

### Can I get a dedicated Arlo connector?

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