# Vitally integrations: tasks and notes

> Create a task, create a note and create or update an account in Vitally. Connect Vitally to the rest of your customer service stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/vitally-integrations/
**Categories:** Customer service
**Connects through:** HTTP Connector

## Overview

Vitally is a customer success platform that pulls product usage and account data together so teams can track customer health, run playbooks and manage renewals. Tray.ai connects to Vitally through the HTTP Connector, so your workflows can call the Vitally API alongside the rest of your stack.

## Use cases

### Accounts

Read, create, update, and delete accounts in Vitally from any Tray.ai workflow. The Vitally API covers calls such as list accounts and get an account.

- List accounts
- Get an account
- Create an account

### Users

Read, create, update, and delete users in Vitally from any Tray.ai workflow. The Vitally API covers calls such as list users and search users.

- List users
- Search users
- Create a user

### Tasks

Read, create, update, and delete tasks in Vitally from any Tray.ai workflow. The Vitally API covers calls such as list tasks and create a task.

- List tasks
- Create a task
- Update a task

### Notes

Read, create, update, and delete notes in Vitally from any Tray.ai workflow. The Vitally API covers calls such as list notes and create a note.

- List notes
- Create a note
- Update a note

### Analytics events

Create, delete, and manage analytics events in Vitally from any Tray.ai workflow. The Vitally API covers calls such as track product activity and create or update an account.

- Track product activity
- Create or update an account
- Create or update a user

## Challenges Tray.ai solves

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

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

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

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

### Can I get a dedicated Vitally connector?

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