AI Connect for WordPress Documentation

Overview

AI Connect for WordPress is a visual AI tool builder for WordPress websites. It is designed to help site owners create frontend AI tools without hardcoding every request, response, and form manually.

The core idea is simple: create a tool, connect it to a provider, define the inputs users can fill in, map those inputs into a request, map the provider response into output elements, then publish the tool with a shortcode.

What AI Connect is designed for

• Frontend AI tools on WordPress pages
• AI-powered forms and generators
• Provider-based request workflows
• Custom API-powered tools
• Shortcode publishing
• Response mapping into visible result elements
• Protected server-side API key handling

Lite, Pro, and Ultimate

AI Connect for WordPress is planned around different usage levels so beginners can start with a simpler workflow while advanced users can build more serious AI-powered tools.

Requirements

AI Connect for WordPress is designed for normal WordPress websites. Requirements may depend on the selected provider and product edition.

• WordPress installed
• Administrator access to the WordPress dashboard
• A supported AI provider or API endpoint
• Provider API credentials when required
• A page where the AI tool shortcode can be published
• HTTPS recommended for production websites

For live websites, always test your AI tool workflow before publishing it for real users.

Getting Started

A typical AI Connect workflow starts in the WordPress admin area and ends with a shortcode published on a public page.

1. Create a new AI tool in the WordPress dashboard.
2. Choose or configure the provider for that tool.
3. Add the frontend input fields users will complete.
4. Map input variables into the request template.
5. Define how the provider response should be displayed.
6. Test the tool from the admin test workflow.
7. Copy the shortcode.
8. Place the shortcode on a WordPress page.
9. Test the frontend tool as a real visitor.

Providers

AI Connect is designed around a provider-based architecture. Each AI tool can be connected to a provider, and that provider controls how the request is sent and how the result is received.

Provider examples

• Custom API endpoint
• Replicate-style model APIs
• Hugging Face-style inference APIs
• OpenAI-compatible APIs
• Gemini-style APIs
• Claude-style APIs

Tool Builder

The Tool Builder is the central place where an AI tool is configured. It connects the form, provider, request template, response mapping, and published shortcode together.

Common tool settings

• Tool name
• Tool description
• Provider selection
• Input fields
• Request template
• Response path or result mapping
• Frontend result layout
• Shortcode output

The goal is to let site owners create practical AI tools without editing theme files or writing a custom integration for every idea.

Inputs and Variables

Inputs are the fields that users complete on the frontend. These values can be inserted into the provider request through variables.

Example input fields

• Prompt
• Topic
• Audience
• Tone
• Style
• Image URL
• Custom text field
• Select/dropdown field

Example variable usage

A frontend field named prompt can be mapped into a request template using a variable.

Request Template

The request template defines what is sent to the provider. It can include static values, dynamic variables, model settings, and tool-specific parameters.

What a request template may include

• Model or endpoint information
• User input variables
• Prompt instructions
• Generation settings
• Output format preferences
• Provider-specific parameters

Response Mapping

Response mapping tells AI Connect where the useful provider output is located and how it should appear on the frontend.

Common output examples

• Generated text
• Generated image URL
• Prediction output array
• JSON field value
• Status message
• Error message

Example response paths

Different providers return different response shapes, so each tool should be tested with the provider it uses.

Shortcode Publishing

AI Connect is designed to publish tools with shortcodes. A shortcode can be placed inside a WordPress page, landing page, product page, or documentation page.

Example shortcode concept

The shortcode renders the configured frontend form, handles the submission workflow, and displays the mapped result according to the tool settings.

Security and API Keys

AI Connect is designed so sensitive provider credentials are handled server-side. API keys should not be printed in frontend HTML, JavaScript, or public page source.

Important security principles

• Keep API keys server-side.
• Do not expose provider secrets in frontend code.
• Validate frontend submissions before sending provider requests.
• Use nonces and capability checks in admin workflows.
• Protect against unsafe external requests.
• Show safe, readable errors instead of exposing raw secrets.

Troubleshooting

The frontend tool does not return a result

• Check that the provider is configured correctly.
• Confirm the API key or provider credential is valid.
• Test the tool from the admin test workflow.
• Check the request template for missing variables.
• Check the response path or result mapping.

The response is empty or incomplete

• Confirm the provider returns the expected response format.
• Check whether the response path points to the correct field.
• Try a simpler request template.
• Review any provider error message.

The frontend form does not look right

• Check the page builder or theme CSS.
• Confirm the shortcode is placed in the correct page area.
• Clear cache and test in a private browser window.
• Test with a default theme if needed.

The provider request fails

• Check the API credential.
• Confirm the provider account has access to the selected model or endpoint.
• Confirm billing or usage limits if required by the provider.
• Make sure the website can make outgoing HTTPS requests.

Frequently Asked Questions

Support

If you need help with AI Connect for WordPress, contact Clugins support and include your product version, WordPress version, active theme, relevant plugins, provider name, error message, screenshots, and steps to reproduce the issue.