# Gupshup integrations: messages and templates

> Send a text message and update profile details in Gupshup, and start a workflow when Gupshup sends “Inbound message”.

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

## Overview

Gupshup is a conversational messaging platform that lets businesses send WhatsApp, SMS and other channel messages to customers at scale. Tray.ai connects to Gupshup through the HTTP Connector, so your workflows can call the Gupshup API alongside the rest of your stack.

## Use cases

### Messages

Create messages in Gupshup from any Tray.ai workflow. The Gupshup API covers calls such as send a text message and send a media message.

- Send a text message
- Send a media message
- Send a template message

### Templates

Read templates in Gupshup from any Tray.ai workflow. The Gupshup API covers calls such as list templates for an app and get a template.

- List templates for an app
- Get a template

### Business profile

Read and update business profile in Gupshup from any Tray.ai workflow. The Gupshup API covers calls such as get business details and update profile details.

- Get business details
- Update profile details
- Update profile photo

### Blocked users

Read and manage blocked users in Gupshup from any Tray.ai workflow. The Gupshup API covers calls such as block a user and unblock a user.

- Block a user
- Unblock a user
- List blocked users

### Gupshup events

Start a Tray.ai workflow the moment something happens in Gupshup. Gupshup sends events such as inbound message and message status update to a Tray.ai webhook trigger.

- Inbound message
- Message status update
- Template status update

## Challenges Tray.ai solves

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

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

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

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

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