WordPress Integration
'Connect WordPress to Supervity, manage posts, pages, media, comments, and taxonomy in operators and workflows.'
This guide explains how to connect WordPress to Supervity, what data is available after connection, how operators can use WordPress data and actions within workflows, and how to remove the integration when needed.
Overview
The Supervity WordPress integration allows your workspace to securely connect WordPress as a governed platform capability.
Once connected, operators and workflows can use WordPress data and actions to publish posts, modify site pages, moderate comments, upload media files, structure categories and tags, and check registered users.
With the WordPress integration, Supervity can:
- Manage blog articles (get posts, get post details, create posts, update posts, and delete posts)
- Administer site pages (get pages, get page details, create pages, update pages, and delete pages)
- Organize site media (get media items, upload media, and delete media files)
- Moderate comments (get comments, create comments, update comments, and delete comments)
- Classify content (get categories, create categories, get tags, and create tags)
- Query user lists (get users and get user details)
- Retrieve global site settings (get site details)
All WordPress access is governed through Supervity's security, permissions, and audit controls.
Prerequisites
Before connecting WordPress, ensure you have:
- An active Supervity workspace
- A WordPress account (either a WordPress.com account or a self-hosted WordPress site)
- Permission to authorize third-party applications on the WordPress site
Adding the WordPress Integration
Follow these steps to connect WordPress to Supervity. If you encounter any issues during setup, refer to the Troubleshooting section of this guide.
Step 1: Open Integrations
Log in to Supervity. From the left navigation bar, click the Integrations icon.
This opens the Integrations page, where all available integrations are listed. Connected integrations and available integrations can both be managed from this page.
Step 2: Select WordPress
Locate WordPress in the available integrations list. Click Connect.
Step 3: Enter Site Base URL
In the connection dialog, you will see an optional Site Base URL field:
- For WordPress.com: Use the default
public-api.wordpress.com. - For Self-Hosted Sites: Enter the base URL of your WordPress installation
(e.g.,
yoursite.com,www.yoursite.com, orblog.yoursite.com).
Click Connect to proceed.
Step 4: Authorize Access
You will be redirected to the secure WordPress authorization page. Review the requested permissions and click Allow to grant Supervity access to your WordPress site.
Supervity uses WordPress's standard OAuth 2.0 authorization flow. Your WordPress login password is never shared with or stored by Supervity.
Step 5: Complete Connection
After authorization, you will be redirected back to Supervity. The WordPress integration will appear as Connected on the Integrations page. Your workspace can now securely access WordPress capabilities according to the permissions granted.
Having trouble? See the Troubleshooting section for step-by-step help with common setup issues.
How WordPress Works in Supervity
After connection, WordPress becomes available as a governed platform tool.
Operators can use WordPress capabilities when planning and executing tasks, while workflows can automate actions using WordPress data.
Common use cases include:
- Auto-publishing generated blog posts or marketing announcements
- Synchronizing landing page copies with ongoing campaigns
- Auditing site comments to screen and remove spam
- Uploading and archiving brand assets inside the WordPress Media Library
- Tracking published content and assigning post authors automatically
Using WordPress in Operators
Connected WordPress capabilities become available to operators automatically. Operators determine when WordPress data or actions are required to complete a task and execute accordingly, while remaining governed by workspace permissions, security controls, and approval policies.
What Operators Can Do with WordPress
Operators can perform the following actions using WordPress:
- Get lists of posts and pages, and retrieve specific post or page details
- Create new posts or pages, update content, and delete entries
- Get media library lists, upload files, and delete media files
- Get lists of comments, create replies, update comment status, and delete comments
- Get and create taxonomy categories and tags
- Retrieve lists of site users and get specific user profiles
- Fetch site-wide metadata and configurations
Typical Operator Use Cases
| Use Case | Example |
|---|---|
| Article Publishing | Automatically draft, format, and publish blog posts |
| Site Updates | Create or modify pages with updated content or product info |
| Media Asset Management | Upload graphics, files, and images to the WordPress Media Library |
| Comment Moderation | Fetch recent comments and screen them for moderation workflow |
| Taxonomy Organization | Create and apply categories/tags to organize site content |
| User Auditing | Retrieve details of registered site users for audit logs |
Features & Prerequisites
For each WordPress capability available in Supervity, the following describes the use case and the prerequisites required before use.
Post Operations
Use Case: Get posts, get post details, create new posts, update existing posts, or delete posts.
Prerequisites:
- WordPress site connected to Supervity
- Connected user account must have appropriate roles (e.g., Contributor, Author, Editor, or Administrator) depending on the desired action (e.g. Contributors can create drafts but cannot publish)
Page Operations
Use Case: Get pages, get page details, create pages, update landing page copy, or delete pages.
Prerequisites:
- WordPress site connected to Supervity
- Connected user account must have appropriate roles (Editor or Administrator privileges are typically required to create or modify pages)
Media Operations
Use Case: Get media items, upload media files, or delete media from the library.
Prerequisites:
- WordPress site connected to Supervity
Comment Operations
Use Case: Get comments, create comments/replies, update comment details, or delete comments.
Prerequisites:
- WordPress site connected to Supervity
Category Operations
Use Case: Get categories or create categories to classify content.
Prerequisites:
- WordPress site connected to Supervity
Tag Operations
Use Case: Get tags or create tags to organize posts.
Prerequisites:
- WordPress site connected to Supervity
User Operations
Use Case: Get users or get user profiles to assign authors or check registered site accounts.
Prerequisites:
- WordPress site connected to Supervity
Site Operations
Use Case: Get site details and configurations.
Prerequisites:
- WordPress site connected to Supervity
Permissions Requested
Supervity only requests the permissions required for enabled WordPress capabilities.
Depending on the features used in your workspace, permissions may include:
| Permission Type | Purpose |
|---|---|
| User Profile | Associate WordPress user account details and credentials |
| Posts & Pages | Read, draft, publish, modify, and delete posts and pages |
| Media | View, upload, and manage files in the Media Library |
| Comments | Read, write, approve, and delete comments on posts and pages |
| Site & Taxonomy | Access site configurations, categories, tags, and basic metadata |
| Offline Access | Maintain integration connectivity without requiring constant re-authentication |
Supervity follows least-privilege principles and only accesses data necessary to provide requested functionality.
Authentication & Security
The WordPress integration uses OAuth 2.0 authentication.
Security controls include:
- Encrypted credential storage (AES-256)
- Scoped access policies
- Token refresh and rotation support
- Immediate revocation capabilities
- Workspace-level governance controls
- Complete audit logging
- TLS 1.3 for all connection pipelines
All WordPress access remains subject to Supervity security policies and role-based permissions.
Managing the Integration
View Connection Status
From the left navigation bar, click the Integrations icon.
For WordPress you can view:
- Connection status
- Base URL of the connected site
- Last usage information
- Associated workflows and operators
Reconnect WordPress
If WordPress authorization expires: Open the Integrations page from the left navigation bar. Select WordPress. Click Reconnect. Complete authorization again through the WordPress portal.
Existing workflows and operators do not need to be recreated.
Removing the WordPress Integration
You can remove the WordPress connection from your Supervity workspace at any time directly from within the Supervity platform.
Steps to Remove
Log in to Supervity. From the left navigation bar, click the Integrations icon. Locate and select WordPress from the integrations list. Click Disconnect. Confirm the action when prompted.
Implications of Removal
Once removed:
- Supervity immediately loses all access to your WordPress site and associated data
- No new WordPress data will be read or processed after removal
- All active WordPress connections within your Supervity workspace are terminated
- Scheduled or active workflows that depend on WordPress will stop executing
- WordPress-dependent workflow steps will fail safely with clear error messages
- Existing workflow definitions within Supervity are not deleted — only the active connection is terminated
- Historical execution logs remain available for auditing purposes
Disconnecting WordPress does not delete workflow definitions, operators, or previously generated outputs.
How Your Data Is Handled After Removal
Data Handling on Removal:
- Supervity immediately loses access to your WordPress account upon removal
- No new WordPress posts, pages, or comments will be collected or processed after disconnection
- Temporary files processed during workflow execution are deleted after execution completes
- WordPress access tokens and all account-related data are permanently deleted from Supervity's platform within 15 minutes of disconnection — no background access continues after removal
Auditing & Observability
All WordPress activity performed through Supervity is logged.
Audit records include:
- Which operator requested access
- Which workflow executed the action
- Timestamp of execution
- Success or failure status
- Relevant inputs and outputs (sensitive values are redacted)
This supports compliance, troubleshooting, governance, and operational visibility.
Troubleshooting
If you encounter issues at any stage, refer to the steps below. For issues not covered here, contact the Supervity support team.
Self-Hosted Site Connection Failed
Likely Cause: Incorrect base URL, or HTTP connection instead of HTTPS.
Resolution:
- Ensure the WordPress site has SSL configured and uses the
https://protocol. - Verify that the base URL is correct and does not include unnecessary subfolders unless WordPress is installed in a subdirectory.
- Verify that the WordPress REST API is enabled and accessible. You can test
this by visiting
https://yoursite.com/wp-json/in a browser.
Authorization Failed During Setup
Likely Cause: Incorrect WordPress account used, or corporate tenant policies restricting third-party applications.
Resolution:
- Ensure you are signed in to the correct WordPress account.
- Verify with your organization's IT administrator that your account is allowed to authorize third-party applications (Admin Consent may be required).
- Return to Supervity → Integrations → WordPress and click Connect to retry.
- If the issue persists, contact your IT administrator.
Access Forbidden (403 errors)
Likely Cause: Connected WordPress user account does not have sufficient permissions for the requested action (e.g., trying to write pages as a Contributor).
Resolution:
- Verify the connected account has the appropriate role (Author, Editor, or Administrator) on the target site.
- Reconnect the integration using an account with higher permissions.
Frequently Asked Questions
Q: Can I connect multiple WordPress sites to Supervity?
Yes. Each connected account is authenticated independently. You can configure and connect multiple WordPress sites in your workspace settings.
Q: Does Supervity store my WordPress password?
No. Authentication is handled completely via standard OAuth 2.0. Supervity only receives and stores securely encrypted access tokens.
Q: What happens if I update my WordPress site theme or layout?
Updating themes, templates, or CSS does not affect the REST API. Your Supervity workflows and operators will continue working normally.
Q: Will I need to reconfigure my workflows after reconnecting WordPress?
No. If you reconnect WordPress due to token expiry, existing workflows and operators will continue working without reconfiguration.
Q: What happens to my workflows if I disconnect or remove WordPress?
Workflow definitions are not deleted when WordPress is disconnected or removed. However, any workflow steps that depend on WordPress will fail safely with clear error messages until WordPress is reconnected.
Q: How do I authorize the Supervity WordPress integration?
Log in to Supervity at Supervity, navigate to the Integrations page from the left navigation bar, locate WordPress, and click Connect. You will be redirected to WordPress's authorization page where you can review and approve the requested permissions. After authorization, you will be redirected back to Supervity automatically. See the Adding the WordPress Integration section above for full step-by-step instructions.
Q: Who do I contact if I have an issue with the integration?
Contact the Supervity support team. See the Support section below for full contact details, support hours, and SLA information.
Support
If you need assistance with the WordPress integration, visit the Support page.
Support Hours
- Monday to Friday, 9:00 AM – 6:00 PM IST
- Requests submitted outside business hours will be addressed on the next business day
First Response SLA
- All support requests receive an initial response within 24 business hours
Contact Information
| Contact Type | Details |
|---|---|
| Support | Support & Contact |
| Sales Inquiries | sales@supervity.ai |
| Contact Form | https://www.supervity.ai/contact-us |
| Website | https://www.supervity.ai |
| Privacy Policy | https://supervity.ai/privacy-policy |
| Terms of Service | https://www.supervity.ai/terms-of-service |
| Acceptable Use Policy | https://supervity.ai/acceptable-use-policy |
When Contacting Support, Please Provide
- Workspace name
- Site base URL
- Relevant workflow or operator information
- Error messages or screenshots when available
This helps the support team investigate and resolve issues more quickly.