ChatGPT

Use Postsiva Social Media Manager in ChatGPT to list accounts, generate content, publish posts, read analytics, and reply to comments. Requires Pro plan with gpt_app_enabled.

Connect (recommended)

Open the Postsiva GPT

Open Postsiva Social Media Manager in ChatGPT, or create your own Custom GPT (steps below).

Connect your workspace

Click Connect to Postsiva, sign in, and select the workspace ChatGPT should manage.

Start chatting

Ask for connected accounts, drafts, schedules, or analytics — for example:

What social accounts are linked to my workspace?

Overview

User chats with your Custom GPT
ChatGPT calls POST /unified/gpt-actions/{tool_name} with JSON bodies
User authenticates once via Connect to Postsiva (OAuth)
Actions run against the selected workspace

Full API reference: GPT Actions

Create your own Custom GPT

Open GPT Builder

ChatGPT → Explore GPTs → Create → Configure

Import OpenAPI schema

Actions → Import from URL:

https://backend.postsiva.com/openapi/chatgpt-actions.json

This registers all Postsiva tools as Actions (publish, get_accounts, idea_to_content, etc.).

Configure authentication

Authentication type: OAuth

Field	Value
Client ID	From Postsiva (contact support or app settings if provided)
Client Secret	Matching secret
Authorization URL	`https://backend.postsiva.com/auth/oauth/authorize`
Token URL	`https://backend.postsiva.com/auth/oauth/token`
Scope	As defined in Postsiva OAuth config

Alternative for internal/testing: API Key with Authorization: Bearer psk_live_YOUR_KEY (not recommended for public GPTs).

Set instructions

Example system instructions:

You are a Postsiva social media assistant.

Rules:
- Always confirm before publishing live posts or replying to comments publicly.
- Use get_accounts first when platform connection is unclear.
- idea_to_content, content_to_image, and media_to_content do NOT publish — follow with publish when the user wants to go live.
- Scheduling times must be ISO 8601 UTC (e.g. 2026-07-10T14:30:00Z).
- If the user wants to disconnect ChatGPT from Postsiva, call disconnect_gpt_connector.
- You cannot search the web — do not claim live web results.

Test connection

Click Connect to Postsiva in the GPT preview, sign in, select workspace, then ask:

What social accounts are linked to my workspace?

OAuth flow (Connect to Postsiva)

ChatGPT redirects to GET /auth/oauth/authorize
User signs in at /auth/oauth/login (email/password or Google)
User selects workspace at /auth/oauth/select-workspace
ChatGPT receives access token (Bearer JWT with workspace_id)
Subsequent Actions send Authorization: Bearer <token>

Discovery: GET https://backend.postsiva.com/.well-known/oauth-protected-resource Disconnect: User asks GPT to disconnect, or you call:

POST /unified/gpt-actions/disconnect_gpt_connector
Authorization: Bearer <oauth_jwt>
Body: {}

See GPT Actions — disconnect.

disconnect_gpt_connector revokes the ChatGPT session only. Social accounts stay connected. Use manage_platform_connection with action=disconnect to unlink a network.

Available Actions

Same 12 tools as MCP, excluding web_search_duckduckgo:

Action	Use when user asks to…
`get_accounts`	See connected platforms or one profile
`get_queued_posts`	View scheduled posts or drafts
`get_user_posts`	List recent posts
`get_unified_analytics`	View engagement totals
`get_comments`	Read comments on posts
`reply_to_comment`	Post a public reply
`manage_platform_connection`	Connect or disconnect OAuth
`idea_to_content`	Turn a topic into post copy
`content_to_image`	Generate images from text
`media_to_content`	Write captions from image/video URL
`analyze_media`	Describe what’s in media
`publish`	Post, draft, or schedule content
`disconnect_gpt_connector`	Log out ChatGPT from Postsiva

Argument schemas are in the imported OpenAPI file.

Example conversations

Generate and draft

User: Write LinkedIn and Threads posts about our new API docs, then save LinkedIn as a draft.

GPT calls: idea_to_content → publish with draft: true for LinkedIn. Schedule

User: Schedule this for Friday 10am UTC on Instagram: [caption]. Image: [url]

GPT calls: publish with post_type=image, scheduled_time, and media fields. Analytics

User: How did my posts perform this month?

GPT calls: get_unified_analytics, optionally get_user_posts with refresh_stats=true.

GPT Actions vs MCP

	Custom GPT (Actions)	ChatGPT MCP (web)	Claude.ai	Cursor / Claude Code
URL / surface	`/unified/gpt-actions/*`	`https://mcp.postsiva.com/web/mcp`	`https://mcp.postsiva.com/web/mcp`	`https://mcp.postsiva.com/mcp`
Auth	OAuth (Connect to Postsiva)	API key as `?api-key=` query (or OAuth)	OAuth only (API key will not work)	API key as `X-API-Key` header
Upload	See Actions / browser flows	Iframe widget on web MCP	Iframe widget	curl + `file_path`
Web search	No (host search)	No (host search)	No (host search)	No (host search)

ChatGPT MCP — API key query param

https://mcp.postsiva.com/web/mcp?api-key=psk_live_YOUR_KEY

Also accepted: ?apikey= / ?api_key=. Do not use this pattern for Claude.ai. For Claude custom connectors, see Claude.

Privacy and data

Actions run against one workspace selected at OAuth time
Post content and analytics pass through ChatGPT’s conversation context — review OpenAI’s data policies for your use case
Do not embed psk_live_ keys in public GPT instructions

Troubleshooting

Issue	Solution
Actions grayed out	Re-import OpenAPI; check Pro plan
401 on every call	Reconnect via Connect to Postsiva
”Plan upgrade” message	Workspace needs `gpt_app_enabled` (Pro)
GPT tries to web search	Remind in instructions — tool not available
Wrong workspace	Disconnect OAuth, reconnect, pick correct workspace

Alternative: API key testing

For private GPTs or development, set Authentication to API Key:

Authorization: Bearer psk_live_YOUR_KEY

All Actions resolve workspace from the key. No OAuth UI required.

Never publish a Custom GPT that exposes your personal API key in instructions or shared links.

GPT Actions API

Endpoint reference

Plans

Pro requirements

Claude connector

MCP in Claude

MCP overview

Developer agent integration

Get started

Features

REST API

MCP

Platforms

Guides

Integrations

Errors

Reference

Connect (recommended)

Overview

Create your own Custom GPT

OAuth flow (Connect to Postsiva)

Available Actions

Example conversations

GPT Actions vs MCP

ChatGPT MCP — API key query param

Privacy and data

Troubleshooting

Alternative: API key testing

Next

GPT Actions API

Plans

Claude connector

MCP overview

​Connect (recommended)

​Overview

​Create your own Custom GPT

​OAuth flow (Connect to Postsiva)

​Available Actions

​Example conversations

​GPT Actions vs MCP

​ChatGPT MCP — API key query param

​Privacy and data

​Troubleshooting

​Alternative: API key testing

​Next

GPT Actions API

Plans

Claude connector

MCP overview

Connect (recommended)

Overview

Create your own Custom GPT

OAuth flow (Connect to Postsiva)

Available Actions

Example conversations

GPT Actions vs MCP

ChatGPT MCP — API key query param

Privacy and data

Troubleshooting

Alternative: API key testing

Next