Every WordPress plugin
your agent can talk to.

Read the value of a custom field for a given post.

Return all registered ACF field groups with their fields and metadata.

Write a new value to a custom field on a post.

Use when the user wants to register, add, or create a new customer/client. ALWAYS confirm first name, last name, and email with the user before calling this ability.

Use when the user wants to add, create, or set up a new bookable service. ALWAYS confirm the service name, duration, price, and assigned employees with the user before calling this ability.

Use when the user wants to register or enroll a customer in an event, class, or group session. ALWAYS confirm the event and customer with the user before calling. Use amelia/list-events for eventId and amelia/list-customers or amelia/add-customer for customerId.

Use when the user wants to cancel, remove, or undo a booking. ALWAYS ask the user explicitly to confirm before calling: "Are you sure you want to cancel booking ID {bookingId}? This cannot be undone."

Use when the user asks when they can book, what slots are free, or what times are available for a service. Returns available datetimes grouped by date. Requires serviceId from amelia/list-services.

Use when the user wants to book, schedule, or reserve an appointment for a customer. ALWAYS confirm service, employee, customer, and date/time with the user before calling. Use amelia/list-services, amelia/list-employees, amelia/list-customers, and amelia/check-availability first.

Use when the user wants to create, add, or set up a new event, class, or group session. ALWAYS confirm name, start/end date-time, price, and capacity with the user before calling this ability.

Use when the user asks about existing appointments, upcoming bookings, or wants to find a specific appointment to reschedule or cancel. Returns appointments with IDs, dates, service, provider, customer, and status. Supports filtering by date range, provider, service, customer, and status. Results are paginated (use page and limit; default 25 per page). When dates are omitted, only appointments from today through the next 90 days are returned.

Use when the user asks to look up a customer, find a client, or before booking on behalf of an existing person. Returns customer IDs required by amelia/create-appointment and amelia/book-event. Results are paginated (use page and limit; default 25 per page).

Use when the user asks about staff, employees, therapists, or who performs a service. Returns provider IDs required by amelia/create-appointment and amelia/check-availability. Results are paginated (use page and limit; default 25 per page).

Use when the user asks about events, classes, workshops, or group sessions. Returns event IDs, periods, capacity, and availability. Call this before amelia/book-event. Results are paginated (use page and limit). When dates are omitted, only events from today through the next 90 days are returned.

Use when the user asks what services are available, what can be booked, appointment types, or pricing. Returns bookable services with IDs, durations, and prices. Results are paginated (use page and limit; default 25 per page). Call this first before amelia/check-availability or amelia/create-appointment.

Discover all available WordPress abilities in the system. Returns a list of all registered abilities with their basic information.

Execute a WordPress ability with the provided parameters. This is the primary execution layer that can run any registered ability.

Get detailed information about a specific WordPress ability including its input/output schema, description, and usage examples.

Appends a Better Click To Share block to the end of a post. Use this after you have the exact tweet text to show (e.g. from suggest-tweetables).

Returns suggested tweet-length snippets from a post or raw content. Use these with insert-click-to-tweet. No AI; uses sentence boundaries and length filter.

Returns the privacy regulations covered by Cookiebot CMP on this site, plus the current scan status and plan type.

Returns the current Cookiebot CMP plugin configuration: whether a Domain Group ID is set, GCM v2 status, cookie blocking mode, banner state, and plugin version.

Installs and activates the Privacy Policy Generator plugin (privacy-policy-usercentrics). Idempotent — returns immediately if already active. After install, direct the user to admin_url to complete policy setup.

Sets the Domain Group ID (CBID). For Cookiebot accounts this is a UUID (XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX) found under Implementation in the Cookiebot Admin. For Usercentrics accounts this is a Settings ID (9 or 14 characters) found in the Usercentrics Admin. Changes take effect immediately.

Enables or disables Google Consent Mode v2. GCM v2 is required for Google Ads and Analytics in the EU/EEA and is enabled by default. Only disable if explicitly requested by the user.

Checks that the Domain Group ID is configured, Google Consent Mode v2 is enabled, and cookie blocking mode is set to auto. Returns an issues[] list — empty means all checks passed.

Read the Elementor data tree for a given post id.

Return the catalogue of registered Elementor widgets including atomic v4 widgets.

Patch settings on a single Elementor widget.

Adds an item to a menu: a page, post, or CPT item (object_id), a category or tag (taxonomy + object_id), or a custom URL. Supports parent item and position.

Assigns taxonomy terms to a custom post type item. Can replace or append terms.

Assigns a menu to a theme location (or clears the location with menu_id 0). Changes site-wide navigation. Opt-in required.

Purges the page cache for a single post/page (post_id) or the whole site (no post_id, requires manage_options). Detects the active cache plugin automatically: WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, or WP Fastest Cache. Call this after write abilities that modify post meta directly (update-seopress, update-post-meta, elementor-update-element, SEO fixes): those writes do not fire save_post, so cache plugins keep serving the OLD rendered HTML — audits and visitors see stale titles and meta descriptions until the cache is purged.

Creates a new blog category with name, slug, description, and parent category (optional).

Creates a PHP code snippet via the Code Snippets plugin. The snippet is always saved as inactive — it must be activated manually from wp-admin › Snippets. Validates PHP syntax, blocks dangerous functions, and fires an audit action hook after saving.

Creates a new item in a custom post type. Content is optional as some CPTs store data in custom fields instead.

Creates a new, empty navigation menu with the given name. Use ewpa/add-menu-item to populate it and ewpa/assign-menu-location to display it.

Creates a new WordPress page with title, content, status, and parent page (for hierarchy).

Creates a new blog post. Accepts title, HTML content, excerpt, categories, tags, featured image, and status. Defaults to draft.

Creates a new blog tag with name, slug, and description.

Deletes a custom post type item. By default moves to trash; use force_delete to permanently remove.

Permanently deletes a menu and all of its items, and clears it from any theme location it was assigned to. Destructive — opt-in required.

Sends a post to trash or permanently deletes it. Defaults to trash.

Creates an exact copy of any post, page, or custom post type item — including all post meta (ACF, SEO, featured image) and taxonomy terms. The duplicate is saved as draft by default. Returns the new post ID and edit URL.

Binds a single Elementor widget setting to a dynamic tag. source=post_title uses the native Post Title tag; source=meta uses a JetEngine dynamic field reading the given meta_key. Edits _elementor_data server-side, validates the tree, injects the __dynamic__ binding using Elementor own tag encoder, saves, and clears Elementor cache. Requires Elementor (Elementor Pro for post_title, JetEngine for meta).

Returns a compact, flattened tree of an Elementor page/template: every element with its id, depth, type, and a short text preview. Read-only. Use this to locate element ids before editing.

Updates the settings of a single Elementor element by id (static content or styles). Provided keys are merged into the element settings; other keys are preserved. Examples: {"title":"New heading"} for a heading, {"text":"Click"} for a button, {"editor":"<p>HTML</p>"} for a text-editor. Saves and clears Elementor cache. Batch mode: pass an edits[] array to update multiple elements in a single call.

Returns a list of all currently active plugins on the site, including name, version, and detected capabilities (multilanguage, SEO, WooCommerce, etc.).

Retrieves all blog categories with their ID, name, slug, description, and post count.

Retrieves blog comments with optional filters by status, post, and count. Useful for moderation and analysis.

Retrieves full details of a single custom post type item, including all meta fields, taxonomies, and content.

Retrieves a list of items from a specific custom post type with filtering, search, and taxonomy query support.

Retrieves all taxonomies associated with a custom post type, including their terms.

Fetches the site llms.txt file (the AI-crawler guidance file, llmstxt.org spec), detects which component serves it (SEOPress Pro, physical file, this plugin, third-party, or none), and validates it: H1 header present, blockquote summary, Markdown links, raw HTML entities, size. Returns the content plus a list of issues with severity, so an agent can diagnose why a Lighthouse "Agentic Browsing" audit fails.

Retrieves media library files (images, videos, documents) with filters by MIME type and search.

Returns every item of one menu with its hierarchy: id, title, url, target type (post_type, taxonomy, or custom), linked object, parent item, and position.

Retrieves all details of a specific page by ID, including full content, template, hierarchy, and SEO metadata.

Retrieves site pages with their title, status, content, and hierarchy (parent/child).

Retrieves all details of a specific post by ID, including full content, metadata, and featured image.

Reads any single post meta field by exact key. Useful for SEO plugins and custom fields not covered by dedicated sections (e.g. _genesis_title for The SEO Framework, _aioseo_title for AIOSEO). Requires edit_post capability on the target post.

Returns the full translation map for a post: language codes, post IDs, titles, and permalink for each available translation. Requires Polylang or WPML.

Retrieves a list of blog posts with optional filters by status, category, count, and order.

Retrieves all Rank Math SEO metadata for a post or page: title, description, keywords, robots, advanced robots, Open Graph, Twitter Card, schema, breadcrumb, cornerstone, and SEO score.

Retrieves all SEOPress metadata for a post or page: title, description, focus keyword, robots directives, canonical URL, Open Graph, and Twitter Card.

Retrieves the SEOPress content analysis for a post or page: every check (meta title, meta description, headings, internal links, structured data, image alt texts, etc.) with its impact level and recommendation text. Set refresh=true to run a fresh analysis of the rendered page before reading the results — recommended after updating content or metadata. Requires SEOPress 7.5+.

Retrieves all blog tags with their ID, name, slug, and post count.

Retrieves the list of site users with their ID, name, email, and role. Useful for assigning post authors.

Returns all fields with their current stored values for a given JetEngine Options Page slug. Requires JetEngine with the Options Pages module enabled.

Lists all registered JetEngine Options Pages with their field schema. Does not return field values. Requires JetEngine with the Options Pages module enabled.

Writes a new value to a single field of a JetEngine Options Page. Supports text, number, select, checkbox, repeater, and most other field types. UI-only types (html, tab, accordion, endpoint) are rejected. For repeater fields call ewpa/je-get-options-page first to see the repeater_fields structure, then pass an array of row objects. Requires JetEngine with the Options Pages module enabled.

Links two posts as translations of each other via Polylang or WPML. Both posts must already have a language assigned.

Lists every navigation menu with its id, slug, and item count, plus the theme menu locations and which menu each one displays.

Lists all custom post types registered on the site, with their configuration, supported features, and associated taxonomies.

Changes a comment status: approve, hold, mark as spam, or send to trash.

Permanently removes one item from a menu. Children of the removed item are kept and become top-level. Destructive — opt-in required.

Replies to an existing comment on a post or page. The reply is published as the current authenticated user.

Searches for text in a specific post content and replaces it with another. Useful for corrections and updates.

Assigns a language to an existing post via Polylang or WPML. Does nothing if no multilanguage plugin is active.

Returns a summary with the total posts, pages, categories, tags, comments, and users of the site.

Updates an existing comment. Allows changing the content, author name, author email, and the WordPress user associated with the comment.

Updates an existing custom post type item. Only provided fields are modified (partial update).

Writes the site llms.txt content (Markdown, llmstxt.org spec: H1 title, optional blockquote summary, H2 sections with link lists). Routes automatically: if SEOPress Pro is active it writes the SEOPress option (its dynamic placeholders like {{latest_posts:5}}, {{featured_products:3}}, {{site_name}} keep working); otherwise this plugin serves the content itself at /llms.txt. Refuses to act when a physical file or a third-party plugin already provides it. Content is validated before saving — an H1 first line is mandatory.

Updates one menu item: title, custom URL, parent item, or position. Fields not provided keep their current value.

Updates an existing post. Only the provided fields are modified, others remain unchanged.

Writes any post meta field by exact key. Use this when you know the exact meta key required by a specific SEO plugin or custom field (e.g. _genesis_title for The SEO Framework, _seopress_titles_title for SEOPress). Requires edit_post capability on the target post.

Updates Rank Math SEO metadata on a post or page (rank_math_focus_keyword, rank_math_title, rank_math_description, etc). Use this ability to set or change the focus keyword, SEO title, meta description, canonical URL, robots, Open Graph, Twitter Card, breadcrumb, schema snippet, cornerstone, and pillar content. Only the provided fields are modified.

Writes a structured-data schema block (e.g. FAQPage, Article, Product) to a Rank Math schema meta key. The schema_data object is sanitized and stored as a PHP-serialized array, exactly as Rank Math expects, so it renders as JSON-LD in <head>. Use this to add or replace a schema block on any post or page.

Updates SEOPress metadata on a post or page (_seopress_titles_title, _seopress_titles_desc, etc). Use this to set or change the SEO title, meta description, focus keyword, canonical URL, robots directives, and Open Graph / Twitter Card fields. Only the provided fields are modified.

Downloads an image from an external URL and registers it in the WordPress media library. Optionally assigns it as featured image for a post. Returns the attachment ID and local URL.

Retrieves all Yoast SEO metadata for a post or page: title, description, focus keyphrase, canonical URL, robots (noindex/nofollow/advanced), Open Graph, and Twitter Card.

Fetches and parses the Yoast SEO sitemap index for this site, returning the list of all sitemap URLs and their last modification date.

Updates Yoast SEO metadata on a post or page (_yoast_wpseo_title, _yoast_wpseo_metadesc, etc). Use this to set or change the SEO title, meta description, focus keyphrase, canonical URL, robots, and Open Graph / Twitter Card fields. Only the provided fields are modified.

Create a wp.me short link for a given URL.

Return submitted responses for a Jetpack form.

Get the configured WhatsApp phone number for current context

Generate WhatsApp "click to chat" URL with phone and pre-filled message

Set the call to action text for the Joinchat chat window globally or for current context

Set the pre-filled WhatsApp first message globally or for current context

Set the WhatsApp phone number globally or for current context

Activate plugins on a MainWP child site.

Activate a theme on a MainWP child site.

Create a new MainWP client. Possible errors: mainwp_invalid_input, ability_invalid_permissions

Add a new MainWP child site.

Create a new MainWP tag.

Check connectivity status of a MainWP child site.

Check connectivity status of multiple MainWP child sites. Operations with >200 sites are automatically queued.

Count sites associated with a MainWP client. Possible errors: mainwp_client_not_found, ability_invalid_permissions

Count total number of MainWP clients. Possible errors: ability_invalid_permissions

Count total MainWP child sites with optional filtering.

Deactivate plugins on a MainWP child site.

Delete a MainWP client. Requires confirm: true or dry_run: true. Possible errors: mainwp_client_not_found, mainwp_confirmation_required, mainwp_invalid_input, ability_invalid_permissions

Delete plugins from a MainWP child site. Requires confirmation. Supports dry-run mode.

Delete themes from a MainWP child site. Requires confirmation. Supports dry-run mode.

Delete a MainWP child site. Requires confirmation. Supports dry-run mode.

Delete a MainWP tag. Requires confirmation or supports dry-run mode.

Disconnect a MainWP child site.

Disconnect multiple MainWP child sites. Operations with >200 sites are automatically queued.

Get list of abandoned plugins on a child site. Returns plugins detected during last sync. Data freshness depends on sync frequency.

Get list of abandoned themes on a child site. Returns themes detected during last sync. Data freshness depends on sync frequency.

Retrieve status of a queued batch operation (sync, update, reconnect, disconnect, check, suspend). Returns progress, results, and errors. Possible errors: mainwp_job_not_found.

Get cost tracker entries for a MainWP client. Requires Cost Tracker module. Possible errors: mainwp_client_not_found, mainwp_module_not_available, ability_invalid_permissions

Get sites associated with a MainWP client. Possible errors: mainwp_client_not_found, ability_invalid_permissions

Get detailed information about a single MainWP client. Possible errors: mainwp_client_not_found, ability_invalid_permissions

Get non-MainWP changes detected on a child site. Requires Logs module.

Get client assigned to a MainWP child site.

Get costs associated with a MainWP child site. Requires Cost Tracker module to be active.

Get list of plugins installed on a child site.

Get security status for a MainWP child site including vulnerability counts, security issues, and issue categories detected during last sync.

Get list of themes installed on a child site.

Get available updates for a single site with optional filtering by update type.

Get detailed information about a single MainWP child site.

Get basic site info (id, url, name only) for fast bulk retrieval. Use list_sites_v1 for full details with filtering, or get_site_v1 for complete single-site information.

Get list of clients associated with a tag.

Get list of sites associated with a tag.

Get detailed information about a single MainWP tag.

Add or remove WordPress core from the ignored updates list for a single site.

Add or remove plugins from the ignored updates list for a single site.

Add or remove themes from the ignored updates list for a single site.

List MainWP clients with pagination and filtering. Possible errors: mainwp_invalid_input, ability_invalid_permissions

List updates that have been marked as ignored.

List MainWP child sites with pagination and filtering. Returns basic site information including ID, URL, name, and connection status.

List MainWP tags with pagination and filtering. Returns tag information including ID, name, color, and sites count.

List available updates across MainWP child sites with filtering and pagination.

Reconnect a disconnected MainWP child site.

Reconnect multiple MainWP child sites. Operations with >200 sites are automatically queued.

Execute updates on one or more MainWP child sites. Operations with >200 sites are automatically queued for background processing.

Add or remove items from the ignored updates list for a site.

Suspend a MainWP client. Possible errors: mainwp_client_not_found, ability_invalid_permissions

Suspend a MainWP child site.

Suspend multiple MainWP child sites. Operations with >200 sites are automatically queued.

Trigger synchronization for one or more child sites. Operations with >200 sites are automatically queued for background processing.

Unsuspend a MainWP client. Possible errors: mainwp_client_not_found, ability_invalid_permissions

Unsuspend a MainWP child site.

Execute ALL available updates (core, plugins, themes, translations) across all sites or specified sites. WARNING: This is a broad operation. For targeted updates, use run_updates_v1 with specific types[] and site_ids_or_domains[]. Operations with >200 sites are queued.

Update an existing MainWP client. Possible errors: mainwp_client_not_found, mainwp_invalid_input, ability_invalid_permissions

Update WordPress core for a single site.

Update plugins for a single site. Optionally specify slugs to update only specific plugins.

Update themes for a single site. Optionally specify slugs to update only specific themes.

Update translations for a single site. Optionally specify slugs to update only specific translations.

Update settings for a MainWP child site.

Update an existing MainWP tag.

Retrieve the full course structure tree: all sections with their lessons and quizzes in order.

Atomically save the entire course structure (sections, lessons, quizzes). Replaces the existing structure — provide the full desired tree.

Create a new course category. Requires name. Optionally accepts slug, description, and parent (ID of a parent category for hierarchical nesting). Returns the created category with its ID and course count.

Permanently delete a course category. Requires id (category ID). Taxonomy terms have no trash state — deletion is immediate and irreversible. Returns the deleted category object.

Retrieve a single course category by its ID. Requires id (category ID). Returns the category object including name, slug, description, parent ID, and course count.

Retrieve a paginated list of course categories. Optionally filter by search term or parent ID. Returns data array with name, slug, description, parent, and course count per category, plus pagination metadata.

Update an existing course category. Requires id (category ID). Optionally accepts name, slug, description, or parent. Returns the updated category object.

Retrieve all content items (sections, lessons, quizzes) belonging to a course.

Create a new course with title, description, pricing, access mode, and category assignments.

Move a course to trash. Use force=true to permanently delete.

Create a new course difficulty level (e.g. Beginner, Intermediate, Advanced). Requires name. Optionally accepts slug and description. Returns the created difficulty object with its ID.

Permanently delete a course difficulty level. Requires id (difficulty ID). Deletion is immediate and irreversible. Returns the deleted difficulty object.

Retrieve a single course difficulty level by its ID. Requires id (difficulty ID). Returns the difficulty object including name, slug, description, and course count.

Retrieve a paginated list of course difficulty levels. Optionally filter by search term. Returns data array with name, slug, description, and course count per difficulty, plus pagination metadata.

Update an existing course difficulty level. Requires id (difficulty ID). Optionally accepts name, slug, or description. Returns the updated difficulty object.

Retrieve a single course by ID, including all its metadata and settings.

Retrieve a paginated list of courses. Supports filtering by status, category, instructor, and search term.

Post a new question or answer in a course Q&A thread. Requires course_id and content. Omit parent to create a top-level question; set parent to a question ID to post an answer. Returns the created entry with its ID and status.

Move a course Q&A entry to trash. Requires id (Q&A entry ID). Trashed entries can be recovered with masteriyo/course-qa-restore. Use force=true to permanently delete. Returns the deleted entry.

Retrieve a single course Q&A entry by its ID. Requires id (Q&A entry ID). Returns the entry including content, author, status, course_id, and parent (set when the entry is an answer to another question).

Retrieve a paginated list of course Q&A entries. Optionally filter by course_id or status (approved, hold, spam). Returns data array of Q&A entries with content, author, and course context, plus pagination metadata.

Restore a trashed course Q&A entry to its previous status. Requires id (Q&A entry ID). Only applies to entries currently in the trash. Returns the restored entry object.

Update an existing Q&A entry content.

Restore a trashed course back to its previous published or draft state.

Submit a new course review with rating and comment.

Delete a course review permanently.

Retrieve a single course review by its ID. Requires id (review ID). Returns the review including reviewer name, rating (1–5), comment body, status (approved, hold, spam), and course_id.

Retrieve a paginated list of course reviews, optionally filtered by course or status.

Update an existing course review (approve, reject, or edit content).

Create a new course tag. Tags are flat (no hierarchy). Requires name. Optionally accepts slug and description. Returns the created tag object with its ID.

Permanently delete a course tag. Requires id (tag ID). Deletion is immediate and irreversible. Returns the deleted tag object.

Retrieve a single course tag by its ID. Requires id (tag ID). Returns the tag object including name, slug, description, and course count.

Retrieve a paginated list of course tags. Optionally filter by search term. Returns data array with name, slug, description, and course count per tag, plus pagination metadata.

Update an existing course tag. Requires id (tag ID). Optionally accepts name, slug, or description. Returns the updated tag object.

Update an existing course. Supply only the fields to change; others remain unchanged.

Enroll a student in a course. Requires course_id and user_id. Optionally accepts status (active, inactive). Returns the created enrollment object with its ID.

Unenroll a student from a course. Requires id (enrollment ID). Optionally accepts force (boolean, permanently removes the record when true). Returns the deleted enrollment object.

Retrieve a single course enrollment record by its ID. Requires id (enrollment ID). Returns the enrollment object including user_id, course_id, status, and date_start.

Retrieve a paginated list of course enrollments. Optionally filter by course_id, user_id, or status. Returns data array and pagination metadata (total, total_pages, page, per_page).

Update an existing course enrollment. Requires id (enrollment ID). Optionally accepts status (active, inactive). Returns the updated enrollment object.

Duplicate a lesson, including its content, into the same section.

Create a new lesson inside a section.

Move a lesson to trash (use force=true to permanently delete).

Retrieve a single lesson by ID including content and video settings.

Retrieve a paginated list of lessons, optionally filtered by course or section.

Restore a trashed lesson back to draft state. Requires id (lesson ID). Only applies to lessons currently in the trash. Returns the restored lesson object.

Update an existing lesson content, title, or video URL.

Create a new course purchase order. Requires customer_id and course_ids (array of course IDs). Optionally accepts payment_method and coupon_code. Returns the created order object with its ID and total.

Delete an order. Requires id (order ID). Optionally accepts force (boolean, permanently removes the order when true). Returns the deleted order object.

Retrieve a single order by its ID. Requires id (order ID). Returns the full order object including status, total, customer details, and line items.

Retrieve a paginated list of course orders. Optionally filter by status, customer_id, or date range. Returns data array and pagination metadata (total, total_pages, page, per_page).

Update an existing order. Requires id (order ID). Optionally accepts status (pending, completed, cancelled, refunded). Returns the updated order object.

Retrieve a course progress record by its ID. Requires id (progress ID). Returns the progress object including user_id, course_id, status (started, progress, completed), and completion percentage.

Update a student's course progress record. Requires id (progress ID). Accepts status (started, progress, completed). Returns the updated progress object.

Create a new question for a quiz with type, answers, and correct answer settings.

Permanently delete a question from a quiz.

Retrieve a single question by ID including answer choices.

Retrieve a paginated list of questions, optionally filtered by quiz.

Update an existing question text, type, or answer choices.

Retrieve the full question list for a quiz in builder format.

Save the ordered list of questions for a quiz. Provide the complete desired question structure.

Duplicate a quiz including its questions into the same section.

Create a new quiz inside a section.

Move a quiz to trash (use force=true to permanently delete).

Retrieve a single quiz by ID including pass mark and time limit settings.

Retrieve a paginated list of quizzes, optionally filtered by course or section.

Update an existing quiz settings, title, or pass mark.

Retrieve all lessons and quizzes belonging to a section.

Create a new section inside a course.

Move a section to trash (use force=true to permanently delete).

Retrieve a single section by ID.

Retrieve a paginated list of sections, optionally filtered by course.

Update an existing section title or order.

Read all Masteriyo LMS settings. Accepts no required input. Returns the full settings object including general, payments, emails, course, quiz, and advanced configuration groups.

Write Masteriyo general settings (styling, pages, course listing options). Accepts a partial general settings object; only provided keys are updated.

Write Masteriyo quiz settings (questions per page, passing grade, attempt limits, review visibility). Accepts a partial quiz settings object; only provided keys are updated.

Register a new user account. Requires username, email, and password. Optionally accepts display_name and roles. Returns the created user object with its ID.

Delete a user account from the LMS. Requires id (user ID). Optionally accepts force (boolean). Returns the deleted user object.

Retrieve a single user profile by their ID. Requires id (user ID). Returns the user object including display_name, email, roles, and profile metadata.

Retrieve a paginated list of Masteriyo users (students and instructors). Optionally filter by role, search term, or enrollment status. Returns data array and pagination metadata.

Update an existing user's profile. Requires id (user ID). Optionally accepts display_name, email, or profile fields. Returns the updated user object.

Adds the Nexter Blocks Accordion block (tpgb/tp-accordion) with full support for all style, layout, animation, transform, and advanced settings.

Adds the Nexter Blocks Blockquote block (tpgb/tp-blockquote) with full support for all style, typography, spacing, border, background, shadow, animation, transform, and advanced settings. BEHAVIOR WHEN USER REQUESTS ALL SETTINGS: When the user says "apply all settings", "all available settings", "with all options", or similar — you MUST actively populate EVERY parameter with contextually appropriate values. Do not leave any field empty or at its default. Invent values that make visual sense for the content topic: - Choose colors that complement the quote content and topic - For transforms: use subtle but visible values that suit the mood (slight rotation, gentle scale, small offset, mild skew) - For animation: pick an entrance animation fitting the content tone - For spacing: use consistent, balanced padding and margin - For borders and shadows: choose styles that frame the quote elegantly - For typography: enable it and choose a preset or size that fits the quote importance - Always populate: textNormalColor, textHoverColor, authorNormalColor, authorHoverColor, quoteColor, quoteIcon, style, contentAlignment, enableTypography, catBgColor, catBgHoverColor, enableCatShadow, enableCatShadowHover, borderNormal, borderHover, borderRadius, HvrborderRadius, boxPadding, boxMargin, scrollAnimation, animDuration, animDelay, animEasing, globalBgColor, globalBgHoverColor, globalBorder, globalBorderHover, globalBRadius, globalBRadiusHover, globalBShadow, globalBShadowHover, globalMargin, globalPadding, globalPosition, globalClasses, globalId, globalZindex, transitionDuration, transitionFunction, transitionOrigin, rotateDeg, rotateDegHover, offsetX, offsetXHover, scaleValue, scaleValueHover, skewX, skewXHover, flipHorizontal, flipVertical, flipHorizontalHover, flipVerticalHover

Adds the Nexter Blocks Breadcrumbs block (tpgb/tp-breadcrumbs) with full support for style presets, home icon, separator icon, visibility toggles, taxonomy terms, text styling, spacing, backgrounds, borders, shadows, schema markup, animations, transforms, and advanced settings. This is a dynamic block — breadcrumb links are generated automatically based on the current page context.

Adds the Nexter Blocks Button block (tpgb/tp-button) with 23 style presets, icon support, hover effects, typography, colours, backgrounds, borders, shadows, shake animation, content hover effects, modal popup, animations, transforms, and advanced settings. Typography is set via top-level params (enableTypography, fontFamily, fontType, fontWeight, textDecoration, typoSize) — pass them directly here, do not route them through settings.texTyp. This is a dynamic block — HTML is rendered server-side.

Adds the Nexter Blocks Core Button block (tpgb/tp-button-core). A streamlined, modern button block with icon support (Font Awesome or image), typography, text shadow, colour, background (solid/gradient), border, border radius, box shadow, padding, alignment, animations, transforms, and advanced settings. This is the simplified counterpart to tpgb/tp-button — use this for clean, modern buttons. ⚠️ NEXTER BUILD RULE — Nexter blocks render from their SAVED block HTML, not from attributes alone. Add and nest ONLY via nexter-blocks/add-tpgb-* abilities: to place this button inside a container, pass that container's block_id as parent_block_id. NEVER build, rebuild, or edit a page that contains Nexter blocks with generic page-builder tools (e.g. assemble-page, patch-tree, html-to-builder, write-builder-content, place-widget) — they store attribute-only blocks with no inner HTML, so the button renders blank. When finished, call nexter-blocks/verify-page to confirm no Nexter block is blank.

Adds the Nexter Blocks Code Highlighter block (tpgb/tp-code-highlighter) with PrismJS syntax highlighting, 40+ languages, 8 themes, copy/download buttons, line numbers, line highlighting, scrollbar customisation, and full style/animation/transform controls. This is a dynamic block.

Adds the Nexter Blocks Container block (tpgb/tp-container) — a layout container that segments pages into rows. Supports flex and grid layouts, content width (wide/full), min-height, gutter spacing, flex direction/align/justify/wrap, background, border, box shadow, shape dividers, wrapper link, margin, padding, z-index, overflow, custom tag, responsive visibility, and custom CSS. This is a dynamic block that accepts inner blocks (nested content). ⚠️ NEXTER BUILD RULE — Nexter blocks render from their SAVED block HTML, not from attributes alone. Build and nest ONLY via nexter-blocks/add-tpgb-* abilities: create this container first, then add each child by passing this container's returned block_id as the child's parent_block_id. NEVER build, rebuild, or edit a page that contains Nexter blocks with generic page-builder tools (e.g. assemble-page, patch-tree, html-to-builder, write-builder-content, place-widget / place-section / place-container) — they store attribute-only blocks with no inner HTML, which makes every Nexter block render blank. When finished, call nexter-blocks/verify-page to confirm no Nexter block is blank.

Adds the Nexter Blocks Inner Container block (tpgb/tp-container-inner) — a column wrapper used inside tp-container. Supports width, min-height, flex layout, background, border, box shadow, margin, padding, wrapper link, responsive visibility, and custom CSS. This block accepts inner blocks (nested content).

Adds the Nexter Blocks Countdown block (tpgb/tp-countdown) with 3 style presets (Simple, Flipdown, Progressbar), target date/time, expiry actions, custom labels, per-unit colours/backgrounds/borders, counter/label typography, progress bar stroke/trail settings, and full animation/transform/advanced controls. This is a dynamic block.

Adds the Nexter Blocks Creative Image block (tpgb/tp-creative-image) with image selection by URL or media ID, alignment, width control, float alignment, image size, caption toggle, scroll reveal animation, scrolling image effect, mask image shape, scroll parallax, lightbox popup, link wrapper, CSS filters (normal/hover), border, border radius, box shadow, and full animation/transform/advanced controls. This is a dynamic block.

Adds the Nexter Blocks Dark Mode block (tpgb/tp-dark-mode) — a light/dark theme toggle switcher with 3 style presets, icon customisation (light/dark icons), cookie persistence, OS theme matching, position control (relative/absolute/fixed), and full styling controls for switch track, dot, and before/after text labels. This is a dynamic block.

Adds the Nexter Blocks Data Table block (tpgb/tp-data-table) — a feature-rich table with custom headers and body rows, search, sort, filter, mobile responsive modes, alignment per cell, stripe effect, per-state colours (normal/row-hover/cell-hover) for both header and body, borders, button cells, icon/image cells, and full styling controls. This is a dynamic block. IMPORTANT: Pass `headers` as a simple array of column header strings and `rows` as a 2D array where each inner array is a row of cell values. The ability will automatically build the required internal structure with row/cell markers.

Adds the Nexter Blocks Draw SVG block (tpgb/tp-draw-svg) — an animated SVG drawing block with pre-built icons or custom SVG upload, stroke/fill colour control, draw animation types (delayed, sync, oneByOne), duration, hover/scroll triggers, alignment, max width, and link wrapper. This is a dynamic block.

Adds the Nexter Blocks Flipbox block (tpgb/tp-flipbox) — a card that flips horizontally or vertically on hover to reveal back content. Supports icon/image/SVG front display, title with custom tag, description, back-side button with link, carousel back content, comprehensive styling for front/back states (typography, colours, backgrounds, borders, shadows, overlays), icon styling (size, colours, shadows), and full animation/transform/advanced controls. This is a dynamic block.

Adds the Nexter Blocks Form Block (tpgb/tp-form-block) — a contact/lead form container. Supports layout styles, email actions (To/CC/BCC/Subject), auto-response message, redirect on submit, meta data collection, comprehensive styling for labels, inputs, placeholders, buttons, checkboxes/radios, select dropdowns, success/error messages, loader, form alignment, row/column gaps, and full animation/transform/advanced controls. This is a dynamic block that accepts form field inner blocks (name, email, textarea, checkbox, radio, select, submit button, etc.).

Adds a checkbox group field inside a Nexter Form Block. Must be placed inside tpgb/tp-form-block using parent_block_id.

Adds an email input field inside a Nexter Form Block. Must be placed inside tpgb/tp-form-block using parent_block_id.

Adds a hidden input field inside a Nexter Form Block. Useful for passing context values with submissions. Must be placed inside tpgb/tp-form-block using parent_block_id.

Adds a multi-line textarea field inside a Nexter Form Block. Must be placed inside tpgb/tp-form-block using parent_block_id.

Adds a text input field for names inside a Nexter Form Block. Must be placed inside tpgb/tp-form-block using parent_block_id.

Adds a number input field inside a Nexter Form Block. Must be placed inside tpgb/tp-form-block using parent_block_id.

Adds a select dropdown field inside a Nexter Form Block with custom options. Must be placed inside tpgb/tp-form-block using parent_block_id.

Adds a radio button group field inside a Nexter Form Block. Must be placed inside tpgb/tp-form-block using parent_block_id.

Adds the submit button inside a Nexter Form Block. Every form needs exactly one submit button. Must be placed inside tpgb/tp-form-block using parent_block_id.

Adds the Nexter Blocks Google Map block (tpgb/tp-google-map) — an interactive Google Map with multiple location pins, map type (roadmap/satellite/hybrid/terrain), zoom level, map controls (zoom/pan/fullscreen/street view/scale/map type), scroll wheel/drag behaviour, custom map styles, and full styling controls. Supports lat/long coordinates or address-based location pins with custom pin icons. This is a dynamic block. NOTE: Requires a Google Maps API key to be configured in Nexter settings.

Adds a NEXTER BLOCKS Heading block (tpgb/tp-heading). Use this — NOT the WordPress core heading block — whenever the user asks to add a heading on a Nexter Blocks site. Typography is set via top-level params (enableTypography, fontFamily, fontType, fontWeight, textDecoration, lineHeight, letterSpacing, typoSize) — pass them directly here, do not route them through settings.tTypo. Also supports colours, stroke, shadow, blend mode, animations, transforms, spacing, background, border, and advanced position/visibility controls. ⚠️ NEXTER BUILD RULE — Nexter blocks render from their SAVED block HTML, not from attributes alone. Add and nest ONLY via nexter-blocks/add-tpgb-* abilities: to place this heading inside a container, pass that container's block_id as parent_block_id. NEVER build, rebuild, or edit a page that contains Nexter blocks with generic page-builder tools (e.g. assemble-page, patch-tree, html-to-builder, write-builder-content, place-widget) — they store attribute-only blocks with no inner HTML, so the heading renders blank. When finished, call nexter-blocks/verify-page to confirm no Nexter block is blank.

Adds the Nexter Blocks Heading Title block (tpgb/tp-heading-title) — a COMPOSITE heading that combines a main title, optional sub-title, and extra title (pre-title) with separators, animations (letter/word split), and rich styling. Different from tpgb/tp-heading which is a simple single heading. Use this for hero section titles, section headers with sub-text, decorative headings with icon separators, or animated text reveals. Supports 15+ style variants, character/word limits with ellipsis, split-text animations (words/chars/lines), separator customisation (line/icon/image), per-element typography & colours (title/subTitle/extraTitle), gradient text, text stroke, backgrounds, borders, shadows, and full animation/transform/advanced controls. This is a dynamic block.

Adds the Nexter Blocks Hover Card block (tpgb/tp-hovercard) — a flexible HTML structure builder that creates hoverable card layouts by composing nested HTML tags (div, a, span, p, h1-h6) with content types (text, image, custom HTML, or container-only). Each card is built from a list of "items" where each item is either an open tag, close tag, or content element. Supports per-element positioning, typography, shadows, backgrounds, borders, and link wrappers. This is a dynamic block. USAGE: Pass a "cards" array of item objects. Each item represents one HTML element: - { openTag: "div", content: "none" } → starts a div container - { openTag: "a", aLink: {url: "..."}, content: "none" } → starts an anchor - { openTag: "h3", content: "text", cntText: "Title" } → opens h3 with text - { content: "text", cntText: "Some text" } → standalone text - { content: "img", imageUrl: "..." } → an image element - { closeTag: "close" } → closes the most recent open tag IMPORTANT: Every openTag must have a matching closeTag in the correct order (nested properly).

Adds the Nexter Blocks Icon Box block (tpgb/tp-icon-box) — a decorative icon display block supporting Font Awesome icons or SVG icons with view styles (default/stacked/framed), link wrapper, colour/size/rotation/padding/border controls, and full animation/transform/advanced settings. Lighter-weight than tpgb/tp-flipbox — for simple decorative icon placements. This is a dynamic block.

Adds the Nexter Blocks Image block (tpgb/tp-image) — a standard image display block with caption support (default or custom), link wrapper, size/width/height control, object-fit, opacity, CSS filters (normal + hover), border, border radius, box shadow, caption typography/colour/background/alignment, lazy-load toggle, and position controls. Lighter and simpler than tpgb/tp-creative-image — use this for straightforward image placements. This is a dynamic block.

Adds the Nexter Blocks Info Box block (tpgb/tp-infobox) — a versatile feature/service card with icon/image/SVG/text icon, title, description, pin badge, optional CTA button, link wrapper, and extensive styling. Supports 10+ style variants (style-1 through style-10+), listing/carousel layouts, icon display styles (none/stacked/framed), gradient text/icons, overlays, separator lines, full colour/typography/spacing/border/shadow control for all elements, and full animation/transform/advanced settings. This is a dynamic block.

Adds the Nexter Blocks Interactive Circle Info block (tpgb/tp-interactive-circle-info) — an interactive circular display where items arranged around a circle reveal associated content on hover/click. Supports 5+ style presets, multiple items with icon/image, title, description, CTA button, auto-rotation, continuous rotation, entry/exit animations, full styling for normal/hover/active states for circles, icons, content panel, button, and indicator line. This is a dynamic block.

Adds the Nexter Blocks Message Box block (tpgb/tp-messagebox) — an alert/notification/callout box with title, optional description, optional icon (prefix/suffix), dismiss button, arrow pointer, and comprehensive styling for icon, dismiss button, title/description, and box. Use for alerts, warnings, success messages, info callouts, or announcements. This is a dynamic block.

Adds the Nexter Blocks Navigation Builder block (tpgb/tp-navigation-builder) — a complete menu builder with horizontal/vertical/side layouts, multi-level menu items (with submenu depth), icons per item, hover/click activation, sticky menu, responsive hamburger/dropdown, custom toggle styles, and comprehensive styling for menu items (normal/hover/active), submenus, and responsive views. Can pull from existing WordPress menu by name or build a custom menu via items array. This is a dynamic block.

Adds the Nexter Blocks Number Counter block (tpgb/tp-number-counter) — an animated counter that counts up from a start value to a target value when scrolled into view. Perfect for showcasing statistics, achievements, or metrics. Supports 2 style presets (icon+counter side-by-side), numeration format, pre/post symbols (like $ or %), icon/image/SVG, link wrapper, and comprehensive styling. This is a dynamic block.

Adds the Nexter Blocks Post Author block (tpgb/tp-post-author) — automatically displays the current post's author details including name, role, bio, avatar, and social links. Ideal for blog post bylines or author bio sections at the end of articles. Supports 3+ style presets, show/hide each element, and comprehensive styling. This is a dynamic block.

Adds the Nexter Blocks Post Comment block (tpgb/tp-post-comment) — displays the WordPress comments list with nested replies AND a comment submission form. Automatically pulls comments for the current post. Supports custom labels, comprehensive styling for user avatars, names, metadata (date), reply buttons, input fields, and submit button. Use at the bottom of blog posts. This is a dynamic block.

Adds the Nexter Blocks Post Content block (tpgb/tp-post-content) — displays the current post's content, excerpt, or archive term description. Supports character/word limits with ellipsis, comprehensive text/container styling. Ideal for dynamic post templates where the content area auto-populates based on the current post. This is a dynamic block.

Adds the Nexter Blocks Post Image block (tpgb/tp-post-image) — automatically displays the current post's featured image in default mode (inline image) or background mode (applies to section/body/container). Supports image size, alignment, max width, background positioning, border/shadow styling, lightbox popup. Use in post templates. This is a dynamic block.

Adds the Nexter Blocks Post Listing block (tpgb/tp-post-listing) — a powerful post grid/list/metro with filters, pagination, excerpt, meta info (author/date/category), featured image with hover effects, and read more button. Supports multiple layouts (grid/list/metro), custom post types, taxonomy filters, order/offset, category filter UI, and extensive styling for every element. Use for blog listings, portfolios, product grids. This is a dynamic block.

Adds the Nexter Blocks Post Meta block (tpgb/tp-post-meta) — displays post metadata: date, category, author, comments count, and reading time. Each element can be individually toggled, styled (colours, icons, prefixes), and customised with separators. Ideal for blog post info bars below titles. This is a dynamic block.

Adds the Nexter Blocks Post Title block (tpgb/tp-post-title) — displays the current post title with optional prefix/suffix, link wrapper, custom HTML tag, character/word limit, and comprehensive styling for title and prefix/suffix text. Use in post templates or at the top of articles. This is a dynamic block.

Adds the Nexter Blocks Pricing List block (tpgb/tp-pricing-list) — a single pricing row/menu item with title, description, price tag, feature tags (size/options), and optional image. Ideal for menus (food/drink), service lists, product catalogs. Supports 3 style presets, dotted line between title and price, multiple hover effects, image shapes/masks, and comprehensive styling. This is a dynamic block.

Adds the Nexter Blocks Pricing Table block (tpgb/tp-pricing-table) — a full pricing plan card with title/subtitle, icon, price with pre/post text, strike-through previous price, features list (WYSIWYG content or stylish list), CTA button, ribbon/badge, and extensive styling for each element. Use for SaaS pricing, membership plans, service packages. This is a dynamic block.

Adds the Nexter Blocks Pro Paragraph block (tpgb/tp-pro-paragraph) — an advanced text/paragraph block with optional title, multi-column text, drop cap styling (letter-style or boxed), link colours, text shadows, typography controls, and custom HTML tags. Use for magazine-style articles, blog intros, or rich text sections. This is a dynamic block.

Adds the Nexter Blocks Progress Bar block (tpgb/tp-progress-bar) — an animated skill/progress indicator with 3 layout types: horizontal progress bar, circle/pie chart, and radial progress. Supports title, subtitle, number display, icon/image, customizable colours (fill/empty/separator), height variants, and full animation/transform/advanced settings. This is a dynamic block.

Adds the Nexter Blocks Progress Tracker block (tpgb/tp-progress-tracker) — a scroll-based progress indicator showing how much of the page/content has been viewed. Supports 3 display types (horizontal bar at top/bottom, vertical bar on left/right, circular indicator in corner), optional pin points for chapter/section markers, percentage text, and comprehensive styling. This is a dynamic block.

Adds the Nexter Blocks Search Bar block (tpgb/tp-search-bar) — a powerful AJAX-powered search form with live suggestions, filters, result preview cards, taxonomy filters, pagination/load-more, custom post types, and extensive styling for input field, select dropdowns, submit button, and results area. This is a dynamic block.

Adds the Nexter Blocks Site Logo block (tpgb/tp-site-logo) — dynamic site-wide logo with single or double (normal + hover) display modes, image or SVG source, sticky-header logo variant, width control per breakpoint, alignment, link target (home/custom/none), schema markup, and ARIA label. This is a dynamic block.

Adds the Nexter Blocks Smooth Scroll block (tpgb/tp-smooth-scroll) — a site-wide smooth-scrolling effect controller with configurable animation time, step size, time multiplier, wheel normalisation, easing curve, infinite scroll, smooth navigation, custom cubic-bezier easing, and viewport selector. This block has no visible output — it just applies the scroll effect to the page.

Adds the Nexter Blocks Social Embed block (tpgb/tp-social-embed) — embeds posts/videos/pages/buttons from Facebook (posts/videos/comments/like-button/page/share-button), Twitter (timeline/tweet/buttons/collection/list), Instagram (posts/profile), YouTube (single video/playlist/username), Vimeo (video), and Google Maps (place/directions/streetview/search/view). Each network has its own dedicated parameter set; only fill in the ones for the chosen embedType. This is a dynamic block.

Adds the Nexter Blocks Social Icons block (tpgb/tp-social-icons) — a list of social-media icons with 16 visual styles, per-icon network/icon/image/URL/title/colors/tooltip, hover-style presets (faded/etc), alignment, gap, padding, sizing, border, radius, shadow, title typography, and Tippy tooltip controls. Provide an array of `socialIcons` to fully control each item; otherwise the default Facebook/YouTube/Twitter set is used. This is a dynamic block.

Adds the Nexter Blocks Stylish List block (tpgb/tp-stylist-list) — bullet/icon list with per-item icon (FA, image, SVG), URL, hint/pin badge, and tooltip; supports vertical/horizontal layout, read-more toggle (collapse N items + show-all/less), separator, advanced icon styling (size/border/radius/bg/shadow normal+hover), text styling (typo, padding, border/radius/bg/shadow normal+hover), pin/hint badge styling (placement, typo, bg, padding, dimensions), Tippy tooltip controls, hover-inverse fade effect. This is a dynamic block.

Adds the Nexter Blocks Switcher block (tpgb/tp-switcher) — a 2-state toggle that swaps between two content panels. Each panel can be plain text/HTML (`source = content`) or a saved Gutenberg template (`source = editor`). Comes with 2 visual styles, optional FA icons on each label, alignment, label spacing, toggle size, switch-track and indicator colours (active/inactive), label typography & colours per state, description typography & colours per state, and shadow on the indicator. This is a dynamic block.

Adds the Nexter Blocks Tabs Tours block (tpgb/tp-tabs-tours) — multi-tab/tour navigation panel where each tab has a title, optional inline content or saved Gutenberg template, optional inner & outer FA icon (or image). Supports horizontal/vertical layout, nav position (top/bottom/left/right), swiper effect, equal-width navs, columned vertical nav, mobile-accordion fallback, active-tab default, full styling for nav buttons (normal+active), nav bar wrapper (normal+hover), tab content area, underline indicator, and per-icon controls. This is a dynamic block.

Adds the Nexter Blocks Team Member block (tpgb/tp-team-listing) — grid/carousel team showcase. Each member has photo, name, designation, category, custom URL, and 7 social channels (website, FB, IG, Twitter, LinkedIn, Mail, Phone). Supports grid/messy/slider layouts, columns per breakpoint, alignment, title tag, name typography & colors (normal+hover), designation typography & colors, social icon size/bg-size/colors (normal+hover), image margin/padding/radius/bg/filter/shadow (normal+hover), card box padding/border/radius/bg/shadow (normal+hover), content padding. This is a dynamic block.

Adds the Nexter Blocks Testimonials block (tpgb/tp-testimonials) — grid or carousel of customer testimonials. Each item has author name, designation, content/quote, author title overlay, and avatar image. Supports 3 visual styles, columns per breakpoint, content height limit (with hover/always scrollbars or read-more truncation), full styling for box (margin/padding/border/radius/bg/shadow normal+hover), title/author/designation/content typography & colors (normal+hover), avatar max-width/radius/shadow (normal+hover), Read-more button styling, scroll bar styling, and carousel pagination dots colour controls. This is a dynamic block.

Adds the Nexter Blocks Video block (tpgb/tp-video) — embeds a YouTube, Vimeo, or self-hosted MP4 video with custom thumbnail/banner mode, optional popup (lightbox) playback, custom play-icon image, video title & description overlay (with typography & colour), continuous animations (pulse/rotate/drop_waves) for the play icon, video container border/radius/shadow + hover, transform, schema markup, and provider-specific options (autoplay, mute, loop, controls, modest branding, privacy mode, Vimeo title/portrait/byline, etc.). This is a dynamic block.

Creates a new button preset in the global preset store. The preset becomes immediately available in the inspector picker on every button block (tp-button-core, tp-button, tp-post-comment, etc.) and the plus-button-presets.css :root variables refresh on the next page load.

Removes a button preset from the global preset store. Existing button blocks that referenced this preset will keep their stamped var() refs in the post HTML — those refs simply stop resolving, so the block falls back to its default values until edited.

Returns a procedural guide for creating a structured Nexter Blocks documentation post in WordPress. Call this whenever the user asks to create, write, build, or publish documentation / a tutorial / a how-to post for an existing Nexter Blocks feature or block — e.g. "create a doc post for [block name]", "write a Nexter doc page", "build a documentation post", "make a tutorial post for [block]". The returned guide enforces the canonical section order (Breadcrumb → Key Takeaways → TOC → Intro → CTA → Required Setup → Video → Activation → Key Features → Dynamic Sections → Styling), uses only Nexter Blocks widgets (never Elementor), leaves image placeholders for manual screenshot upload, and skips optional sections cleanly when their inputs are absent. Skipping this step leads to inconsistent doc structure, missing sections, and accidental use of non-Nexter blocks.

Returns a procedural guide for converting a layout image into a Nexter Blocks Gutenberg page. Call this whenever the user provides a screenshot, mockup, or design image and asks to recreate, build, match, convert, or "make this" as a WordPress page using nexter-blocks/* abilities — but only AFTER nexter-blocks/get-performance-skill has been called for the session, so the build respects the performance budget. The returned guide instructs how to analyze the image (palette, typography, spacing), plan the block tree, build in the correct outer-to-inner order, and verify the result. Skipping this step typically reduces visual fidelity to under 60%.

Returns a procedural guide that enforces performance-conscious rules for every Nexter Blocks page build. CALL THIS FIRST — before nexter-blocks/get-image-to-page-skill, nexter-blocks/inspect-page, or any nexter-blocks/add-tpgb-* ability — at the very start of every session that will create, edit, or recreate a Gutenberg page with Nexter Blocks. The guide enforces an image-weight budget, a Google-Fonts cap, animation/effect limits, correct lazy-loading defaults, and Core Web Vitals (LCP, CLS, INP) checks. Skipping this step is the leading cause of slow pages: heavy hero images, four font families, and four blocks with scroll animations on the same screen.

Returns every font family available on THIS site — web-safe System fonts, fonts activated via the WordPress Font Library / theme.json, and third-party custom fonts (BSF Custom Fonts, Use Any Font) — with, for each family, how to reference it in a Nexter Blocks block and whether it will actually render on the front end. CALL THIS whenever the user asks to use "my font", a "brand font", or any site-installed typeface, instead of guessing a Google Font. CRITICAL: a Font Library family with zero active variants (weights/styles) does NOT emit any @font-face and will silently fall back — such families are returned with will_render=false and a warning; do not apply them until the user activates a variant in Appearance → Fonts. Usage rule per family (also given inline as the "use" field): System font → pass fontFamily only; installed custom/Font-Library/theme/BSF/Use-Any-Font family → pass BOTH fontFamily AND customFont set to the family name (this makes Nexter use the already-enqueued font instead of trying to load it from Google); a genuine Google Font not installed here (e.g. from nexter-blocks/inspect-page) → pass fontFamily only and leave customFont empty so Nexter @imports it.

Returns the full attribute object for one button preset, identified by its preset_key (e.g. "btnpreset_12345678").

Returns the authoritative recipe for applying fontWeight and textDecoration on any Nexter Blocks typographic block. CALL THIS RIGHT AFTER nexter-blocks/get-performance-skill — before nexter-blocks/inspect-page or any nexter-blocks/add-tpgb-* ability — whenever the build involves a non-default font weight, any text decoration, or any typography setting beyond plain fontFamily. Every typography-bearing add-tpgb-* ability now accepts fontWeight ("100"…"900") and textDecoration (none / underline / overline / line-through) as proper TOP-LEVEL parameters — pass them directly. For multi-typo-group blocks (infobox, pricing-table, accordion, etc.) the top-level values apply uniformly to every typography group on the block. Use the settings raw override (camelCase keys are preserved) or sprout/update-element only when different groups must have different settings. The guide also pins the exact tTypo JSON shape — fontWeight nested inside fontFamily, textDecoration sibling of fontFamily — and lists the AI mistakes (weight outside fontFamily, font-weight key, partial typo objects) to avoid. When the user references a site-installed / brand font, the guide directs you to call nexter-blocks/get-site-fonts FIRST to discover which fonts actually exist and will render (never guess), and to pass installed fonts with BOTH fontFamily and customFont set.

Fetches a public URL and returns the typography (Google Fonts families, weights), inline-style colors, page title, OG metadata, and every asset URL found in the HTML — images (including srcset variants), CSS background-images, <video>/<source> URLs, and YouTube/Vimeo iframe embeds. CALL THIS FIRST whenever the user provides a URL and asks to recreate the page or match its style — the returned data is concrete CSS, not a guess from pixels, and dramatically improves font/color/asset fidelity. Pair with nexter-blocks/get-image-to-page-skill (or nexter-blocks-pro/get-image-to-page-skill).

Lists every saved button preset in the active store. Returns the preset key, human name, and a small visual summary (text colour, background colour, border radius) for each entry.

Updates an existing button preset. Only the fields you pass are changed — anything you omit is preserved. Pass `name` to rename. Pass any visual-style field (bgColor, padding, …) to overwrite that one attribute on the preset.

Re-parses a post's stored block tree and reports whether every Nexter block (tpgb/*) still carries content. Nexter blocks render from their SAVED block HTML, so a block that was written attribute-only (self-closing, no inner HTML and no inner blocks) renders BLANK — this happens when a page is built or rewritten with a generic page-builder tool instead of the nexter-blocks/add-tpgb-* abilities. Run this after any Nexter build: if "ok" is false, the listed blank_blocks were stripped of their content and must be rebuilt with nexter-blocks/add-tpgb-* (never with assemble-page / patch-tree / html-to-builder / write-builder-content / place-widget).

Adds an action to a form (email, redirect, success message, etc.). Each action executes after form submission. SAVE ACTIONS: Save actions (type: "save") work correctly when created via this ability - they properly save form submissions to the database. You do not need to set any special parameters for save actions beyond type and label. The system automatically handles all required configuration including parent_id association. CRITICAL ACTION FIELD NAMES: Different action types use different field names for their content: "email" actions use "message" or "email_message", but "successmessage" actions use "success_msg" (NOT "message"). Using the wrong field name will cause the action to fail silently. CRITICAL MERGE TAG FORMATTING: When using merge tags like {field:key} or {calc:name} in email messages (message/email_message parameters) or success messages (success_msg parameter), always add a space before { and after }. Example: "Dear {field:name} ," not "Dear {field:name},". Merge tags that touch other characters will fail to render. EMAIL NOTIFICATIONS: Admin email notification is automatically included in default actions. For user confirmation emails, add an additional email action with "to":"{field:email_field_key}" and customize the subject and message. SUCCESS MESSAGES: Customize success messages in successmessage action type using the success_msg parameter. Default message is "Your form has been successfully submitted." - customize to match your form's purpose. FIELD KEY CONSISTENCY: When using merge tags like {field:key}, use the EXACT field key from the form. If you don't know the field keys, use ninjaforms/get-form first to retrieve all field information. Field keys typically follow the pattern "descriptive_name_1234567890123" with a 13-digit timestamp. Incorrect field keys will cause merge tags to fail silently.

Adds a calculation to a form. Calculations can be used in calc fields and conditional logic. Each calculation requires "name" (unique identifier used in {calc:name} merge tags), "formula" (equation using {field:key} references and operators +, -, *, /, ()), and optionally "decimal_places" for result precision. Equation syntax: {field:field_key} for field values, {calc:name} for other calculation results, standard math operators. Note: Merge tags inside formulas do NOT need spacing (parsed differently than text content). Display calculation results using HTML fields with properly spaced merge tags: {"type":"html","default":"<h3>Result: $ {calc:total} </h3>"}. Store results in hidden fields if needed for submission records. FIELD KEY CONSISTENCY: When creating calculation formulas with {field:key} references, use the EXACT field keys from the form. If you don't know the field keys, use ninjaforms/get-form first to retrieve all field information. Field keys typically follow the pattern "descriptive_name_1234567890123" with a 13-digit timestamp. Incorrect field keys will cause calculations to fail or return zero.

Adds a field to an existing Ninja Forms form. Use the form_id returned by ninjaforms/create-form to add fields. Call this ability multiple times to add multiple fields to a form. POSITIONING: order is a one-based insertion position, not a final sort hint. Existing fields at that position and below move down. For requests like "before Message" or "between Email and Message", call ninjaforms/get-form first and use the current order of Message. If order is omitted, the field is inserted immediately before Submit. CRITICAL MERGE TAG FORMATTING: When adding HTML fields (type: html) that display calculations or field values using merge tags like {field:key} or {calc:name}, always add a space before { and after }. Example: "<h3>Total: $ {calc:total} </h3>" not "<h3>Total: ${calc:total}</h3>". Merge tags that touch other characters will fail to render. CRITICAL CALCULATION DISPLAY: For calculator forms, use HTML field type (NOT textbox) to display calculation results for real-time updates. Use ONE merge tag per HTML field. Example: Add separate fields like {"type":"html","label":"Monthly Payment","default":"<h3>$ {calc:monthly} </h3>"} and {"type":"html","label":"Total Cost","default":"<p>$ {calc:total} </p>"} rather than combining multiple calculations in one field. Keep HTML simple with basic tags (h3, p, strong). Complex nested structures with multiple merge tags will not update in real-time. PERSONALLY IDENTIFIABLE FIELDS: Email, phone, and address field types MUST include "personally_identifiable":true in field settings for GDPR compliance. SPAM PROTECTION: hCaptcha and reCAPTCHA fields must have "label_pos":"hidden" (the widget itself is sufficient) and should NOT be marked as required (set "required":false) - spam protection fields should never display required asterisks. Place spam protection fields before the submit button. REQUIRED FIELDS: Set "required":true for required fields, "required":false for optional fields. Default is false if not specified. FORM ORGANIZATION: Use HTML fields with bold text for section headers: {"type":"html","default":"<p><b>Section Name</b></p>"}. Use HR (divider) fields between major sections. Group related fields together. TWO-COLUMN LAYOUTS: First field in two-column set: "container_class":"one-half first". Second field: "container_class":"one-half". After the pair, return to full width or start another two-column set. PLACEHOLDER POLICY: Default to empty placeholder ("placeholder":""). Only add placeholder text when the field purpose is ambiguous or users need format examples. DO NOT add placeholders for standard fields like Name, Email, Phone, Number, or Address where the label is self-explanatory. FIELD-TYPE-SPECIFIC SETTINGS: Star rating fields (type: "starrating") require the "number_of_stars" setting (typically set to "5"). Without this setting, the stars will not render on the form. Example: {"type":"starrating","label":"Overall Satisfaction","required":true,"number_of_stars":"5"}.

Creates a new Ninja Forms form with specified settings. Optionally include fields array to create a complete form in one call. Returns a form_id that can be used with ninjaforms/add-field to add more fields later. Automatically adds a submit button and default actions (Success Message, Admin Email, Record Submission) unless custom actions are specified. DEFAULT SAVE ACTION: The default "Record Submission" save action is automatically created and configured correctly - form submissions will be saved to the database. No workarounds or manual fixes are needed. The save action is properly initialized with all required settings including parent_id association. CRITICAL MERGE TAG FORMATTING: When using merge tags like {field:key} or {calc:name} in success_message or any text content, always add a space before { and after }. Example: "Thank you, {field:name} !" not "Thank you, {field:name}!". Merge tags that touch other characters will fail to render. CRITICAL CALCULATION DISPLAY: For calculator forms, use HTML field type (NOT textbox) to display calculation results. Use ONE merge tag per HTML field for real-time updates. Example: {"type":"html","default":"<h3>Total: $ {calc:total} </h3>"} not multiple calculations in one field. Keep HTML simple with basic tags (h3, p, strong). Avoid complex nested divs with multiple merge tags as they will not update in real-time. CALCULATION STRUCTURE: For calculator forms, define all calculations in the calculations array. Each calculation must have: "name" (string identifier), "eq" (equation using merge tags), and optionally "dec" (decimal places). Equation syntax: use {field:field_key} for field references, {calc:name} for calculation references, and operators +, -, *, /, (). Note: Merge tags inside equations do NOT need spacing (they are parsed differently than text content). Display results using HTML fields with properly spaced merge tags. Store calculation results in hidden fields if needed for submission records. FIELD KEY CONSISTENCY: When creating forms with fields, calculations, and actions in one call, ensure field keys match exactly across all components. If you specify "key":"email_1234567890123" in the fields array, use that exact key in calculations {"eq":"{field:email_1234567890123}"} and actions/success_message merge tags {field:email_1234567890123}. Field keys typically follow the pattern "descriptive_name_1234567890123" with a 13-digit timestamp. Inconsistent keys will cause merge tags and calculations to fail silently.

REQUIRED PARAMETERS: This ability requires BOTH form_id and action_id - you cannot delete an action by providing only the action_id. If you don't know the form_id or action_id, use ninjaforms/list-actions first. Permanently deletes an action from a form. This action cannot be undone. CRITICAL: Before executing this ability, you MUST ask the user for explicit confirmation and WAIT for their positive response. Do not proceed with deletion unless the user explicitly confirms. If the user wants to temporarily disable an action instead of permanently deleting it, use ninjaforms/update-action with active: 0. IMPORTANT: If the user is attempting to delete a "save" type action (Record Submission), you MUST warn them: "With this action removed, submissions of this form will no longer be saved to the WordPress database or available under Ninja Forms > Submissions. Are you sure you want to proceed?" Wait for explicit confirmation before proceeding.

Permanently deletes a calculation from a form. This action cannot be undone. CRITICAL: Before executing this ability, you MUST ask the user for explicit confirmation and WAIT for their positive response. Do not proceed with deletion unless the user explicitly confirms.

Permanently deletes a form and all associated data including fields, actions, submissions, and metadata. This action cannot be undone. CRITICAL: Before executing this ability, you MUST ask the user for explicit confirmation and WAIT for their positive response. Do not proceed with deletion unless the user explicitly confirms.

Deletes a submission. By default moves to trash; use permanent=true for hard delete. IMPORTANT: Trashed submissions are stored for 30 days before being permanently deleted by WordPress. During this 30-day window, there is no UI method available to restore trashed submissions - recovery requires using the AI Assistant or programmatic database access. After 30 days, trashed submissions are permanently deleted and cannot be recovered. CRITICAL: Before executing this ability, you MUST ask the user for explicit confirmation and WAIT for their positive response. Do not proceed with deletion unless the user explicitly confirms.

Creates an exact copy of a form including all fields, actions, and calculations. The duplicated form will have " (Copy)" appended to its title.

Embed a form in a post or page. This is a TWO-STEP process: STEP 1 (Discovery): Call with form_id and optionally post_title or post_id. If page exists, returns content for you to show user. Ask user which embed method (shortcode/block/metabox) and where to place it. If page not found, ask user to confirm creation. STEP 2 (Execution): Call with embed_method and placement details. For shortcode/block: parse returned content_blocks, present to user, ask for placement (before/after block X, at beginning/end). For metabox: no placement needed. The ability handles page search/creation automatically - you just guide the user through method and placement choices.

Export a form to a .nff file (Ninja Forms export format containing form settings, fields, and actions). CRITICAL: You MUST write the returned content to a local file with .nff extension - do NOT just return the JSON to the user. After calling this ability: (1) Ask the user where to save the file (e.g., Downloads folder, Desktop), (2) Use your file writing tool to save the content to that location with a .nff extension using the suggested filename from the response, (3) Confirm to the user that the .nff file has been saved. The user expects a downloadable .nff file, not raw JSON text.

Exports submissions to a CSV file. Always use CSV format for end users (JSON is only for advanced technical use cases). CRITICAL: You MUST write the returned content to a local file - do NOT just return the CSV text to the user. After calling this ability: (1) Ask the user where to save the file (e.g., Downloads folder, Desktop), (2) Use your file writing tool to save the CSV content to that location with an appropriate .csv filename (e.g., contact-form-submissions.csv), (3) Confirm to the user that the CSV file has been saved. The user expects a downloadable .csv file, not raw text.

Retrieves complete form configuration including all settings, fields, actions, and calculations. Returns full form data that can be used to understand the form structure or prepare for updates.

Retrieve global Ninja Forms plugin settings including date format, currency, reCAPTCHA keys, and advanced options. IMPORTANT: You MUST present the actual VALUES of the settings to the user in a readable format organized by settings category. Use the "settings_by_group" field from the response which dynamically organizes settings by their actual category headers in the Ninja Forms Settings UI (e.g., "General Settings", "reCaptcha Settings", "hCaptcha Settings", "Turnstile Settings", "Advanced Settings"). Present each category as a header followed by its settings. CRITICAL: Do NOT present the "Other" category or any settings within it - skip this category entirely when displaying settings to users. For each setting, show the setting name and its current value. CRITICAL: Use these display labels when presenting settings (never use the database field names): "allow_tracking" must be displayed as "Allow Telemetry", "load_legacy_submissions" must be displayed as "Show Legacy Submissions Page". For API keys (reCAPTCHA, hCaptcha, Turnstile), clearly indicate if they are configured (e.g., "hCaptcha Site Key: [configured]" or "hCaptcha Site Key: [not set]"). For boolean/checkbox settings, present as "Checked" or "Unchecked" based on the value (1/true = Checked, 0/false = Unchecked) - do not interpret the semantic meaning as this can vary by setting. For settings with value "[Action Available]", present them using the format "[Action Available] - {descriptive text}" with the following descriptions: delete_on_uninstall: "Delete all Ninja Forms data when plugin is uninstalled", allow_tracking: "Allow anonymous telemetry to help improve Ninja Forms", trash_expired_submissions: "Automatically move expired form submissions to trash", remove_maintenance_mode: "Use if any of your forms are still in 'Maintenance Mode' after performing any required updates". CRITICAL: If the user attempts to interact with the "Delete All Data" action (delete_on_uninstall), you MUST stop immediately, present this warning: "ALL Ninja Forms data will be removed from the database and the Ninja Forms plug-in will be deactivated. All form and submission data will be unrecoverable." Then wait for explicit user confirmation before proceeding with any deletion-related actions.

Enable or disable public link for a form and return the URL. Public links allow anonymous access to the form without embedding. PRETTY URL FORMAT: This ability generates public links using the modern pretty URL format: /ninja-forms/{slug} where {slug} is a randomly generated 6-character alphanumeric code (lowercase letters and numbers). Example: /ninja-forms/k3caev. This matches the UI behavior and uses WordPress rewrite rules for clean, shareable URLs. The ability automatically generates both the short slug (public_link_key) and stores the full URL (public_link). IMPORTANT: After enabling the public link, you MUST provide the public_link URL from the response to the user so they can share it. Present the URL clearly and explain that they can share this link directly (via email, social media, etc.) and anyone can access the form without needing to visit a specific page on their website.

Retrieves detailed data for a single submission including all field values.

Retrieves field values for a submission. Optionally includes field labels and types.

Retrieves all submissions for a form with optional filtering.

Import a form from .nff file content. Accepts JSON string or array containing form settings, fields, and actions.

Lists all actions configured for a form.

Lists all calculations configured for a form.

Returns all available Ninja Forms field types with their basic information. Useful for discovering what field types can be added to forms.

Retrieves a list of all Ninja Forms forms with their metadata. Optionally filter by title and include field/action details.

Manually trigger action processing for an existing submission. Currently only supports email actions.

Removes a field from a form with mandatory data protection workflow. CRITICAL: This ability can ONLY process ONE field at a time. Even if the user requests removing multiple fields, you must process them individually with full confirmation workflow for each. REQUIRED WORKFLOW (MUST FOLLOW EXACTLY): STEP 1 - Check for Submission Data: When this ability is called, it automatically checks if the field has submission data. STEP 2 - Stop and Inform User: If the field has submission data, the ability will NOT proceed with removal. Instead, it returns field name, number of submissions with data, WARNING about permanent deletion, and request for user confirmation to proceed. Do NOT proceed until user explicitly confirms. STEP 3 - Export Data Automatically: Once user confirms, call this ability again. It will automatically export all field data to CSV and return export file location, sample data preview, and required confirmation phrase. STEP 4 - Require Typed Confirmation: User must type EXACTLY: "DELETE [FIELD_NAME] DATA FROM [COUNT] SUBMISSIONS". Do NOT accept "yes", "ok", "confirmed", or any variation. STEP 5 - Execute After Valid Confirmation: Call this ability a third time with the exact confirmation phrase. Only then will the field be removed. HANDLING BULK REQUESTS: If user requests removing multiple fields (e.g., "Remove all unused fields"): identify all fields, tell user you will process each individually, process FIRST field through complete workflow (Steps 1-5), after completion move to second field, repeat full workflow for each field, NEVER batch process. NEVER: process multiple fields in one call, skip warnings and confirmation, proceed without export, accept vague confirmations, or assume user intent. This ability prevents accidental data loss. Follow the workflow exactly, even if it seems repetitive.

Changes the order of fields in a form. Accepts an array of field_id => order mappings or a simple array of field IDs in the desired order.

REQUIRED PARAMETERS: This ability requires BOTH form_id and action_id - you cannot update an action by providing only the action_id. If you don't know the form_id or action_id, use ninjaforms/list-actions first. PARAMETER FORMAT: Provide settings as top-level parameters, NOT nested in a 'settings' object. Correct: {"form_id": 70, "action_id": 229, "to": "test@example.com", "subject": "New Subject"}. Incorrect: {"form_id": 70, "action_id": 229, "settings": {"to": "test@example.com"}} - this will report 'Updated 0 setting(s)' even though the action saves. Updates an existing action's settings. Use the "active" parameter to enable (active: 1) or disable (active: 0) an action without deleting it. When a user asks to "turn off", "disable", or "deactivate" an action, use this ability with active: 0 instead of deleting the action. Only use delete-action when the user explicitly requests permanent removal. IMPORTANT: If the user is attempting to disable (active: 0) a "save" type action (Record Submission), you MUST warn them: "With this action disabled, submissions of this form will no longer be saved to the WordPress database or available under Ninja Forms > Submissions. Are you sure you want to proceed?" Wait for explicit confirmation before proceeding. CRITICAL ACTION FIELD NAMES: Different action types use different field names for their content: "email" actions use "message" or "email_message", but "successmessage" actions use "success_msg" (NOT "message"). Using the wrong field name will cause the action to fail silently. CRITICAL MERGE TAG FORMATTING: When updating email messages (message/email_message parameters) or success messages (success_msg parameter) with merge tags like {field:key} or {calc:name}, always add a space before { and after }. Example: "Total: $ {calc:price} " not "Total: ${calc:price}". Merge tags that touch other characters will fail to render. FIELD KEY CONSISTENCY: When using merge tags like {field:key}, use the EXACT field key from the form. If you don't know the field keys, use ninjaforms/get-form first to retrieve all field information. Field keys typically follow the pattern "descriptive_name_1234567890123" with a 13-digit timestamp. Incorrect field keys will cause merge tags to fail silently.

Updates an existing calculation's settings. Modify the calculation "formula" (equation using {field:key} references and operators +, -, *, /, ()), "decimal_places" for result precision, or formatting options. Equation syntax: {field:field_key} for field values, {calc:name} for other calculation results, standard math operators. Note: Merge tags inside formulas do NOT need spacing (parsed differently than text content). After updating, ensure calculation results are displayed using HTML fields with properly spaced merge tags: {"type":"html","default":"<h3>Result: $ {calc:total} </h3>"}. Store results in hidden fields if needed for submission records. FIELD KEY CONSISTENCY: When updating calculation formulas with {field:key} references, use the EXACT field keys from the form. If you don't know the field keys, use ninjaforms/get-form first to retrieve all field information. Field keys typically follow the pattern "descriptive_name_1234567890123" with a 13-digit timestamp. Incorrect field keys will cause calculations to fail or return zero.

REQUIRED PARAMETERS: This ability requires BOTH form_id and field_id - you cannot update a field by providing only the field_id. If you don't know the form_id, use ninjaforms/list-forms or ninjaforms/get-form first to identify it. Updates an existing field's settings. Only provided settings will be updated, all others remain unchanged. Supports all field configuration options available in the Ninja Forms dashboard. CRITICAL CALCULATION DISPLAY: When updating HTML fields that display calculations, use ONE merge tag per field for real-time updates. Example: {"default":"<h3>Total: $ {calc:total} </h3>"} works in real-time. Avoid multiple merge tags in one HTML field like "<div><p>{calc:a}</p><p>{calc:b}</p></div>" as this will not update in real-time. Keep HTML simple with basic tags (h3, p, strong). TWO-COLUMN LAYOUTS: First field in two-column set: "container_class":"one-half first". Second field: "container_class":"one-half". After the pair, return to full width or start another two-column set. PLACEHOLDER POLICY: Default to empty placeholder. Only add placeholder text when field purpose is ambiguous or users need format examples. DO NOT add for standard fields (Name, Email, Phone, Number, Address) where label is self-explanatory.

Updates an existing form's settings. Only provided settings will be updated, all others remain unchanged. Supports all form configuration options available in the Ninja Forms dashboard.

Update one or more global Ninja Forms plugin settings. Supports all settings including date format, currency, spam protection keys, and advanced options.

Updates field values in an existing submission. Does not trigger actions.

Save a reusable playbook on this site from a sequence of Respira tool calls, so the workflow can be run again later as a single ability (respira-playbooks/<id>). Use it when the user says "turn this into a playbook", "save this workflow", or "make this reusable". Required: id (lowercase slug starting with a letter; letters, numbers, hyphens), label (human name), steps (an ordered array of steps, each naming a Respira ability and its arguments; later steps may reference earlier outputs). Optional: description, input_schema (JSON Schema of the inputs the playbook accepts), returns. The server validates the structure and rejects cycles or unknown abilities with a specific error. The playbook is callable on the next request.

Delete a saved playbook from this site. Use it to remove an abandoned experiment or a playbook created with a wrong id. This removes only the saved workflow definition; it never touches pages, posts or any content the playbook previously edited.

Read one saved playbook in full, including its steps, input schema and run count. Use it before updating a playbook so the edit is based on what is actually stored rather than what you remember writing.

Invoke an inhaled WordPress Abilities API ability, or a Playbook this agent authored, through the Respira safety wrapper. The wrapper snapshots the target post if the call looks like a write, runs the underlying ability, logs the call to the audit trail, and returns a structured envelope with a rollback URL when a snapshot was taken. The ability must (a) be registered on the site via wp_register_ability, AND (b) be inhaled (the admin toggled it on at wp-admin > Respira, in the Abilities entry of the plugin's own left nav, i.e. admin.php?page=respira-for-wordpress#abilities) — except abilities under the respira-playbooks/ namespace, which bypass the inhale gate because create_playbook already ran the destructive-tool refusal validator on them. Otherwise the call returns a structured 403/404 with instructions, an admin_url, and the closest registered ability names so the caller can self-correct. Pass ability="vendor/ability-name" and args={...}. IMPORTANT: the wire field is `args`, NOT `input`. A playbook step that reads {{input.x}} is reading the args object under the name the playbook executor binds it to.

List the reusable playbooks saved on this site. A playbook is a saved, named workflow (an ordered sequence of Respira tool calls) that can be run again later as a single ability. Returns each playbook's id, label, description, and run count.

File a structured bug report or feedback to the Respira maintainer from inside the chat, with this site's context attached. Use it when a tool failed, an edit produced the wrong output, a step timed out, or behaviour differed from the docs. Required: title (8-120 chars), brief (one paragraph, 20-280 chars), steps_to_reproduce (the exact steps or tool calls, 12+ chars). Optional: severity (blocker, major, minor, cosmetic), expected, actual, error_messages (verbatim), last_tool, contact_email. It never sends prompts, tool arguments, or page content. Only the fields you pass plus the site URL, builder, and plugin version.

Update a saved playbook in place: fix a mistyped step, correct template or capture syntax, rename it, or change its input schema. Takes the same fields as create_playbook and replaces the stored definition, so send the complete playbook rather than a partial patch. The server re-validates the structure and rejects cycles or unknown abilities, exactly as it does on create. Use this when a playbook was authored wrongly, instead of creating a near-duplicate under a new id.

Find products under a stock threshold and produce badge data (e.g. "Only 3 left") for product cards.

Add a note to an order. Private by default; customer_note: true emails the customer.

List on-sale products with computed discount percentages and badge data for product cards.

Add a note to a subscription. Private by default; customer_note: true emails the customer.

Orders and revenue that arrived through agent cart links over a period, with a per-source breakdown.

Quality-score a single product page: images, gallery, description depth, price, category.

Analyze the shop page through the page-builder layer: product grids, hierarchy score, issues, recommendations.