# Invoiced integrations: customers and invoices

> Create a customer, create an invoice and create a payment in Invoiced, and start a workflow when Invoiced sends “Customer created”.

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

## Overview

Invoiced is accounts receivable software that sends invoices and statements, collects payments, and runs subscription billing. Tray.ai connects to Invoiced through the HTTP Connector, so your workflows can call the Invoiced API alongside the rest of your stack.

## Use cases

### Customers

Read, create, update, and delete customers in Invoiced from any Tray.ai workflow. The Invoiced API covers calls such as create a customer and update a customer.

- Create a customer
- Update a customer
- List all customers

### Invoices

Read, create, and update invoices in Invoiced from any Tray.ai workflow. The Invoiced API covers calls such as create an invoice and update an invoice.

- Create an invoice
- Update an invoice
- Send an invoice email

### Payments

Read, create, and update payments in Invoiced from any Tray.ai workflow. The Invoiced API covers calls such as create a payment and update a payment.

- Create a payment
- Update a payment
- Send a receipt

### Events

Read events in Invoiced from any Tray.ai workflow. The Invoiced API covers calls such as retrieve an event and list all events.

- Retrieve an event
- List all events

### Invoiced events

Start a Tray.ai workflow the moment something happens in Invoiced. Invoiced sends events such as customer created and invoice created to a Tray.ai webhook trigger.

- Customer created
- Invoice created
- Invoice viewed

## Challenges Tray.ai solves

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

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

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

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

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