WordPress integration

What it does

The WordPress integration lets you run editorial automations on behalf of any client whose WordPress site you manage. Connect a site once, then list and create posts, push updates to existing posts, manage pages, and watch for new or modified content without writing any code. Authentication uses a per-site WordPress Application Password so each client connection is independently revocable from the WordPress admin.

Connect a WordPress site

1. In TaskJuice, open Settings -> Connections and choose Add connection -> WordPress.
2. Enter the full site URL including https:// and without a trailing slash (for example https://blog.example.com). HTTPS is required for HTTP Basic authentication.
3. In the site's WordPress admin, open Users -> Profile and scroll to Application Passwords.
4. Enter a recognizable name (such as "TaskJuice") in the New Application Password Name field and click Add New Application Password. WordPress displays a 24-character secret once. Capture it before navigating away.
5. Paste the WordPress username of the user the Application Password belongs to into the WordPress username field, and paste the 24-character Application Password into the Application Password field. Spaces in the displayed secret are optional, TaskJuice strips them server-side.

The connection authorizes every REST capability the connected user holds on the site, scoped to their WordPress role (typically Editor, Author, or Administrator). Revoke the key from Users -> Profile -> Application Passwords at any time.

Triggers

• wp-rest/post-updated. Polls the site for posts created or modified since the previous cycle, using the modified_after query parameter as the watermark. Fires once per poll cycle with the batch of observed posts; drop a Loop node downstream to process each post individually.

Actions

• wp-rest/list-posts. List posts with filters for status, category, tag, author, search term, and published-after timestamp. Paginated by page number.
• wp-rest/get-post. Look up a single post by ID.
• wp-rest/create-post. Publish a new post with title, content (HTML or Gutenberg blocks), excerpt, slug, status, categories, tags, and an optional featured media attachment.
• wp-rest/update-post. Patch an existing post's title, content, excerpt, slug, status, or taxonomies.
• wp-rest/list-pages. List pages with filters for status, parent, and search term. Paginated by page number.

Known limitations

• WordPress enforces a maximum of 100 items per page on list endpoints. TaskJuice stops paginating after 100 pages by default; raise the ceiling on the action if a deeper sweep is needed.
• WordPress core ships no first-party webhook surface, so post and page changes are picked up by polling. The default poll interval is 5 minutes; new and updated posts surface on the next cycle.
• HTTP Basic authentication requires the site to be served over HTTPS. WordPress core ignores Application Passwords on plain HTTP.
• Application Password permissions match the WordPress role of the user who created the key. Publishing posts or editing other users' content requires that user to hold a role with publish_posts or edit_others_posts (Author, Editor, or Administrator).
• Some managed WordPress hosts (notably WP Engine and Pantheon) block or rewrite the Authorization header by default. If posts return 401 Unauthorized, ask the host to whitelist the header for the REST API endpoint.