# Airship integrations: push notifications

> Send a push notification, create or update a named user and schedule a notification in Airship.

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

## Overview

Airship is a customer engagement platform for sending push notifications, in-app messages, SMS and email to mobile app and web audiences. Tray.ai connects to Airship through the HTTP Connector, so your workflows can call the Airship API alongside the rest of your stack.

## Use cases

### Push notifications

Create and delete push notifications in Airship from any Tray.ai workflow. The Airship API covers calls such as send a push notification and validate a push notification.

- Send a push notification
- Validate a push notification
- Delete an inbox message

### Named users

Read, create, and update named users in Airship from any Tray.ai workflow. The Airship API covers calls such as list named users and create or update a named user.

- List named users
- Create or update a named user
- Associate a named user

### Schedules

Read, update, and delete schedules in Airship from any Tray.ai workflow. The Airship API covers calls such as schedule a notification and list schedules.

- Schedule a notification
- List schedules
- Update a schedule

### Segments

Read, create, update, and delete segments in Airship from any Tray.ai workflow. The Airship API covers calls such as list segments and create a segment.

- List segments
- Create a segment
- Update a segment

## Challenges Tray.ai solves

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

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

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

The Airship API uses basic authentication, a bearer token, 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 Airship connector?

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