Overview #

The Post Node enables automatic creation and updating of WordPress posts, pages, and custom post types within your workflows. This node supports core WordPress fields, Advanced Custom Fields (ACF), and WooCommerce product data, making it perfect for content automation, product management, and dynamic post creation.

Prerequisites #

Before using the Post Node, you must:

1. Have appropriate WordPress user permissions (publish_posts capability)
2. For ACF fields: Have Advanced Custom Fields plugin installed and fields configured
3. For WooCommerce fields: Have WooCommerce plugin installed and activated
4. Have the post type you want to work with registered and accessible

Features #

• Multiple Post Types: Create any registered post type (posts, pages, products, etc.)
• Rich Text Editing: Toggle between WYSIWYG and plain text for content fields
• Field Groups: Organized sections for Core, ACF, and WooCommerce fields
• Dynamic Field Mapping: Map data from previous nodes to any field
• Post Scheduling: Schedule posts for future publication
• Expandable Fields: Resizable text areas for better content editing
• Field Detection: Automatically detects and loads available fields for chosen post type

Setting Up a Post Node #

1. Add Post Node: Drag the Post node from the sidebar to your workflow
2. Select Post Type: Choose your desired post type from the dropdown
3. Configure Fields:

• Core fields appear automatically
• ACF fields load if available for the post type
• WooCommerce fields appear for product post types

1. Map Data:

• Use the input handler below each field to map data from previous nodes
• Toggle WYSIWYG editor for supported content fields
• Set post status and scheduling options in the Settings tab

Best Practices #

• Use meaningful node names for better workflow organization
• Test with draft status before publishing automatically
• Consider using condition nodes to validate content before posting
• Group related fields using the collapsible sections
• Use WYSIWYG editor for content-heavy fields only

Troubleshooting #

Common issues and solutions:

1. Fields Not Appearing:

• Verify plugin dependencies (ACF, WooCommerce) are active
• Check user permissions for post type
• Confirm field configuration in WordPress admin

1. WYSIWYG Editor Issues:

• Clear browser cache
• Check for JavaScript conflicts
• Verify React Quill initialization

1. Post Creation Failures:

• Verify required fields are mapped
• Check user capabilities
• Confirm post type is registered
• Review WordPress error logs

Limitations #

• Maximum content length based on WordPress database limits
• WYSIWYG editor limited to basic formatting options
• File uploads handled separately through Media node
• Some ACF field types may have limited support
• Scheduled posts require WP Cron to be functional

Security Considerations #

• Sanitizes all input data before database insertion
• Respects WordPress user capabilities
• Validates post type permissions
• Handles HTML content securely
• Prevents unauthorized post creation

Field Support #

Core WordPress Fields #

• Title
• Content (WYSIWYG/Plain Text)
• Excerpt
• Featured Image (via Media node)
• Status (Publish/Draft/Private/Future)
• Publication Date
• Author

ACF Fields Support #

• Text
• Textarea
• WYSIWYG
• Select
• Number
• Email
• URL
• Image (via Media node)
• File (via Media node)
• Date/Time
• True/False
• Link
• Post Object
• Page Link
• Relationship
• Taxonomy

WooCommerce Fields (Product Post Type) #

• Regular Price
• Sale Price
• SKU
• Stock Status
• Stock Quantity
• Virtual
• Downloadable
• Tax Status
• Tax Class
• Shipping Class
• Product Categories
• Product Tags
• Product Attributes
• Product Image (via Media node)
• Product Gallery (via Media node)

Performance Considerations #

• Use plain text editor for simple fields
• Load field data asynchronously
• Cache post type and field configurations
• Minimize unnecessary WYSIWYG editor instances
• Handle large content fields efficiently

This documentation will help users understand and effectively utilize the Post Node in their workflows. Keep it updated as new features are added or existing ones are modified.