# Anchor integrations: contacts and proposals

> Create a contact, publish a proposal and add a service in Anchor, and start a workflow when Anchor sends “Proposal sent”.

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

## Overview

Anchor is billing software for accounting and service firms that turns signed proposals into agreements and automatically issues invoices and collects payments. Tray.ai connects to Anchor through the HTTP Connector, so your workflows can call the Anchor API alongside the rest of your stack.

## Use cases

### Contacts

Read and create contacts in Anchor from any Tray.ai workflow. The Anchor API covers calls such as list contacts and create a contact.

- List contacts
- Create a contact
- Get a contact

### Proposals

Read, create, and manage proposals in Anchor from any Tray.ai workflow. The Anchor API covers calls such as list proposals and get a proposal.

- List proposals
- Get a proposal
- Publish a proposal

### Agreements

Read, create, and manage agreements in Anchor from any Tray.ai workflow. The Anchor API covers calls such as list agreements and get an agreement.

- List agreements
- Get an agreement
- Add a service

### Invoices

Read invoices in Anchor from any Tray.ai workflow. The Anchor API covers calls such as list invoices and get an invoice.

- List invoices
- Get an invoice

### Billing

Create billing in Anchor from any Tray.ai workflow. The Anchor API covers calls such as add credit and submit charges.

- Add credit
- Submit charges

### Webhook subscriptions

Read and update webhook subscriptions in Anchor from any Tray.ai workflow. The Anchor API covers calls such as list subscriptions and subscribe to events.

- List subscriptions
- Subscribe to events
- Unsubscribe from events

## Challenges Tray.ai solves

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

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

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

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

### Can I get a dedicated Anchor connector?

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