OtherReal-timeUpdated May 2026

WordPress

WordPress (self-hosted) post management

WordPress on Tiny Command targets the self-hosted WordPress REST API (the /wp-json/wp/v2 surface every WordPress 4.7+ install exposes by default) — works against any WP instance that has the REST API enabled and a means of authentication. Five actions, no triggers (WordPress doesn't emit outbound webhooks in the core; plugins like WP Webhooks let you point at a Tiny Command webhook trigger for post-published, comment-created, etc., events): Create Post (with title, content as HTML or block-editor markup, excerpt, status, categories, tags, featured media), Update Post, Get Post, List Posts (with filters by status, category, tag, author, date range), Delete Post. The connection takes the WordPress site URL plus either an application password (recommended — set per-user in WP Admin → Users → Application Passwords) or HTTP basic. The application password approach is the modern path; it generates a strong per-integration password without exposing the user's real account password, and revokes individually.

Connect WordPress

0triggers

5actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything WordPress can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Create Post	Creates a new blog post on your WordPress site with title, content, status (draft/publish), categories, tags, and featured image. Use it to pipe AI-drafted articles or external CMS content into WordPress.	6 fields	View →
Delete Post	Deletes a WordPress post. By default moves it to trash; pass force=true to permanently delete. Use the soft-delete path for safety.	2 fields	View →
List Categories	Lists all post categories on the WordPress site with slug, name, and post count. Use to populate a category picker before posting.	0 fields	View →
List Posts	Lists recent WordPress posts, with filters for status, author, category, and date. Useful for newsletter generators or for syncing content elsewhere.	3 fields	View →
Update Post	Updates an existing WordPress post: title, content, status, categories, tags, or featured image. Used by content-refresh and AI-edit workflows.	5 fields	View →

Recipes

Pre-built WordPress workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

WordPress → Slack alerts

AI-triage every WordPress event, ping the right channel only when it matters.

WordPress → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

WordPress → Notion database

Turn WordPress into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect WordPress once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every WordPress field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the WordPress integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect WordPress to Tiny Command?

Open the Tiny Command workflow builder, drop in a WordPress node, and click Connect. Authorize WordPress once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What WordPress triggers does Tiny Command support?

Tiny Command focuses on outbound actions for WordPress today. Use Tiny Command's universal Webhook or Schedule trigger to start WordPress workflows, then run any WordPress action you need.

What WordPress actions can I run from a workflow?

5 WordPress actions are available out of the box, covering other operations like "Create Post". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the WordPress integration real-time?

WordPress actions execute synchronously inside your workflow. Tiny Command waits for WordPress's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use WordPress with Tiny Command?

No. Every WordPress trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any WordPress API endpoint directly.

How much does the WordPress integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The WordPress integration itself has no per-app surcharge.