# Textmagic integrations: messages and contacts

> Send an SMS, add a contact and create a template in Textmagic, and start a workflow when Textmagic sends “Message delivery status changed”.

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

## Overview

Textmagic is a business text messaging service for sending SMS and MMS, two-way chats, scheduled and bulk messages, and email campaigns to contact lists. Tray.ai connects to Textmagic through the HTTP Connector, so your workflows can call the Textmagic API alongside the rest of your stack.

## Use cases

### Messages

Create messages in Textmagic from any Tray.ai workflow. The Textmagic API covers calls such as send an SMS and send bulk messages.

- Send an SMS
- Send bulk messages
- Schedule a message

### Contacts

Read, create, update, and delete contacts in Textmagic from any Tray.ai workflow. The Textmagic API covers calls such as add a contact and find contacts.

- Add a contact
- Find contacts
- Edit a contact

### Templates

Read, create, update, and delete templates in Textmagic from any Tray.ai workflow. The Textmagic API covers calls such as create a template and get a template.

- Create a template
- Get a template
- Update a template

### Chats

Read and delete chats in Textmagic from any Tray.ai workflow. The Textmagic API covers calls such as get chats and find chats.

- Get chats
- Find chats
- Delete a chat

### Lookup

Read lookup in Textmagic from any Tray.ai workflow. The Textmagic API covers calls such as look up a carrier and validate an email address.

- Look up a carrier
- Validate an email address

### Textmagic events

Start a Tray.ai workflow the moment something happens in Textmagic. Textmagic sends events such as message delivery status changed and inbound message received to a Tray.ai webhook trigger.

- Message delivery status changed
- Inbound message received

## Challenges Tray.ai solves

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

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

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

The Textmagic 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 Textmagic connector?

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