Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

WordPress

Open-source website creation software

CategoryMarketing
Authenticationcustom
Version0.5.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect WordPress with Flows360

Open-source website creation software

Use the WordPress connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and 1 trigger.

Available actions

  • Create Post
  • Create Page
  • Update Post
  • Get Post Details
  • Custom API Call

Available triggers

  • New Post

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: WordPress
  • Package: @activepieces/piece-wordpress@0.5.0
  • Exact artifact digest: sha256:d12856fd352d27e37a73058279f9247bf5fee1fd337d7a7f2dba353c9938ffc5
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Post (create_post), Create new post on WordPress Classification: read.
  • Create Page (create_page), Create new page on WordPress Classification: read.
  • Update Post (update_post), Update an existing post on WordPress. Classification: read.
  • Get Post Details (get_post), Get a post from WordPress Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Post, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects6
Supported actions5
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Username Required
  • Password Required · protected credential
  • Website URL Required

Supported objects

ObjectReadWriteNotes
Create Post Yes No Create new post on WordPress
Create Page Yes No Create new page on WordPress
Update Post Yes No Update an existing post on WordPress.
Get Post Details Yes No Get a post from WordPress
Custom API Call Yes No Make a custom API call to a specific endpoint
New Post Yes No polling trigger declared by the pinned package.

Supported actions

Create Post · Read

Create new post on WordPress

create_post · Risk: low · Retry: safe

Inputs

  • title · string · Required, Title of the post about to be added
  • content · string · Required, Uses the WordPress Text Editor which supports HTML
  • slug · string · Optional
  • date · string · Optional, Post publish date (ISO-8601)
  • featured_media_file · object · Optional, URL of featured media
  • tags · array · Optional, Post tags
  • acfFields · object · Optional, Provide field name with value.You can find out field name from ACF plugin menu.
  • categories · array · Optional, Post categories
  • featured_media · string · Optional, Choose from one of your uploaded media files
  • status · string · Optional, Choose post status
  • excerpt · string · Optional, Uses the WordPress Text Editor which supports HTML
  • comment_status · boolean · Optional
  • ping_status · boolean · Optional
Create Page · Read

Create new page on WordPress

create_page · Risk: low · Retry: safe

Inputs

  • title · string · Required, Title of the page about to be added
  • content · string · Required, Uses the WordPress Text Editor which supports HTML
  • slug · string · Optional
  • date · string · Optional, Page publish date (ISO-8601)
  • status · string · Optional, Choose status
  • excerpt · string · Optional, Uses the WordPress Text Editor which supports HTML
  • comment_status · boolean · Optional
  • ping_status · boolean · Optional
Update Post · Read

Update an existing post on WordPress.

update_post · Risk: low · Retry: safe

Inputs

  • post · string · Required
  • title · string · Optional, Title of the post about to be added
  • content · string · Optional, Uses the WordPress Text Editor which supports HTML
  • slug · string · Optional
  • date · string · Optional, Post publish date (ISO-8601)
  • featured_media_file · object · Optional, URL of featured media
  • tags · array · Optional, Post tags
  • acfFields · object · Optional, Provide field name with value.You can find out field name from ACF plugin menu.
  • categories · array · Optional, Post categories
  • featured_media · string · Optional, Choose from one of your uploaded media files
  • status · string · Optional, Choose post status
  • excerpt · string · Optional, Uses the WordPress Text Editor which supports HTML
  • comment_status · boolean · Optional
  • ping_status · boolean · Optional
Get Post Details · Read

Get a post from WordPress

get_post · Risk: low · Retry: safe

Inputs

  • id · number · Required, The ID of the post to get
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Post · Poll

Triggers when a new post is published

Inputs

  • authors · string

Setup

Setup

  1. Add the WordPress connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Username (username), required.
  • Password (password), required; stored as a sensitive connection value.
  • Website URL (website_url), required.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-wordpress@0.5.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required WordPress connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-wordpress@0.5.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com