How to Install and Use Postiz in OpenClaw

Open your terminal and run the ClawHub install command for the Postiz skill. ClawHub downloads the skill package, validates its integrity against the ClawHub registry, and registers it with your local OpenClaw instance. The installation takes a few seconds and ends with a confirmation message showing the required configuration keys. The Postiz skill requires one environment variable: POSTIZ_API_KEY. You will set this in a later step — the skill installs successfully without it but will show an error if you try to use it before the key is configured. If you see a `clawhub: command not found` error, your OpenClaw PATH may need updating. Check your OpenClaw installation directory (typically `/usr/local/bin/clawhub` on macOS/Linux) and ensure it is included in your shell's PATH variable. Reinstalling OpenClaw from openclaw.ai will also repair a broken ClawHub installation.

1clawhub install postiz

Log in to your Postiz account at app.postiz.com (or your self-hosted Postiz URL if you're running your own instance). Navigate to Settings — this is usually accessible from the bottom of the left sidebar or the top-right user menu. In the Settings panel, look for the 'API Keys' or 'Integrations' section. Click 'Create new API key' or 'Generate key'. Give it a descriptive name like 'OpenClaw Integration' so you can identify it later. Postiz generates the key immediately — copy it to your clipboard now, as you may not be able to view it again without regenerating. For self-hosted Postiz installations, the API key section is in the same location within your instance's settings panel. The API key format and behavior are identical regardless of whether you use cloud or self-hosted Postiz. Keep this key private. It grants full API access to your Postiz account, including the ability to post on your behalf to all connected social media accounts. If you suspect the key has been compromised, revoke it immediately in the Postiz settings and generate a new one.

Add your Postiz API key to OpenClaw's configuration. The recommended approach is to add it to your OpenClaw `.env` file or use the `clawhub config set` command, which stores it securely in OpenClaw's local configuration store. Open your OpenClaw configuration directory — this is typically `~/.openclaw/` on macOS/Linux or `%APPDATA%\openclaw\` on Windows. Add the POSTIZ_API_KEY (and optionally POSTIZ_URL for self-hosted installations) as shown in the code block below. If you prefer the command-line approach, use `clawhub config set` to set each variable without opening a text editor. After setting the variables, run `clawhub reload` to apply the configuration change without restarting OpenClaw. For self-hosted Postiz, the POSTIZ_URL variable tells the skill where to send API requests. For cloud Postiz users, the skill defaults to `https://api.postiz.com` and no URL configuration is needed.

1# Option A: Add to ~/.openclaw/.env
2POSTIZ_API_KEY=your-postiz-api-key-here
3POSTIZ_URL=https://api.postiz.com  # omit for cloud; set to your instance URL for self-hosted
4
5# Option B: Set via clawhub config command
6clawhub config set POSTIZ_API_KEY your-postiz-api-key-here
7clawhub config set POSTIZ_URL https://api.postiz.com
8
9# Verify configuration
10clawhub config get POSTIZ_API_KEY
11
12# Reload config
13clawhub reload

Open OpenClaw chat and test the Postiz skill with a simple scheduling request. The skill activates when OpenClaw determines you want to publish or schedule social media content — you can reference Postiz explicitly or simply describe what you want to post and where. For your first test, schedule a simple post to one platform a few hours in the future. This lets you verify the connection is working without immediately publishing anything live. You can cancel or reschedule the post from the Postiz dashboard after confirming it was created successfully. The Postiz skill will confirm the scheduled post with details including the platform, content preview, scheduled time, and post ID. You can use the post ID to reference, modify, or cancel the post later from OpenClaw chat. RapidDev has documented common Postiz skill configurations for teams managing content across five or more social accounts simultaneously — reach out if you need help optimizing multi-account scheduling workflows.

The Postiz skill supports several advanced scheduling patterns that go beyond basic post creation. You can specify posting times for multiple platforms in a single prompt, request that Postiz automatically space out posts for optimal engagement, check your current queue for gaps, and delete or reschedule existing posts. **Optimal timing**: Postiz knows the best posting times per platform based on your audience analytics. Ask OpenClaw to schedule posts at 'optimal time' for each platform rather than specifying exact times — Postiz will select the window most likely to maximize reach based on your historical data. **Queue management**: Ask OpenClaw to list your upcoming posts, identify days with no scheduled content, or fill gaps automatically with content you specify. **Platform-specific content**: Each social platform has different character limits, media requirements, and audience expectations. When writing prompts, specify how you want content adapted per platform — OpenClaw can rewrite the same core message in platform-appropriate style before passing it to Postiz.

1# Optional: Configure default platforms in skill config
2# ~/.openclaw/skills/postiz.yaml
3postiz:
4  default_platforms:
5    - linkedin
6    - twitter
7    - facebook
8  timezone: America/New_York
9  optimal_timing: true  # let Postiz choose best time per platform