# Ghost integrations: posts, pages and tags

> Create a post, create a page and create a tag in Ghost, and start a workflow when Ghost sends “Post published”.

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

## Overview

Ghost is an open source publishing platform for blogs, newsletters and paid memberships, used by independent writers and media businesses. Tray.ai connects to Ghost through the HTTP Connector, so your workflows can call the Ghost API alongside the rest of your stack.

## Use cases

### Posts

Read, create, update, and delete posts in Ghost from any Tray.ai workflow. The Ghost API covers calls such as list posts and get a post.

- List posts
- Get a post
- Create a post

### Pages

Read, create, update, and delete pages in Ghost from any Tray.ai workflow. The Ghost API covers calls such as list pages and create a page.

- List pages
- Create a page
- Update a page

### Members

Read, create, and update members in Ghost from any Tray.ai workflow. The Ghost API covers calls such as list members and get a member.

- List members
- Get a member
- Create a member

### Tags

Read, create, update, and delete tags in Ghost from any Tray.ai workflow. The Ghost API covers calls such as list tags and create a tag.

- List tags
- Create a tag
- Update a tag

### Newsletters

Read, create, and update newsletters in Ghost from any Tray.ai workflow. The Ghost API covers calls such as list newsletters and create a newsletter.

- List newsletters
- Create a newsletter
- Update a newsletter

### Offers

Read, create, and update offers in Ghost from any Tray.ai workflow. The Ghost API covers calls such as list offers and create an offer.

- List offers
- Create an offer
- Update an offer

## Challenges Tray.ai solves

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

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

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

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

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