Settings is where you tell the plugin how to reach the AI providers and outside services your workflows use. There are two ways to power AI, and you can use either or both.
- Bring your own key (Local). Add your own provider API keys. Runs stay on your WordPress site, use your key directly, and are free of platform credits. This is the default and needs no account.
- Keyless credits (Cloud). Connect a free account and let the hosted engine run steps with our keys, metered in credits. Handy when you would rather not manage keys, or need cloud execution. See BYOK keys vs keyless credits.
AI provider keys
Under Settings, enable a provider and paste its key. Supported providers include:
- OpenAI for GPT models and embeddings.
- Perplexity for the AI Research node’s Sonar models.
- OpenRouter for a single key that reaches many models from different providers through one interface, including Claude and others.
- Fal.ai for image, video, and audio generation in the Media Generator node.
Each provider row links to where you generate that key. Pick a default provider so new AI nodes start with a sensible choice.
Other service keys
Some nodes call outside services and need their own key:
- Firecrawl for the Web Scraper node.
- LlamaParse for document parsing, used by the Document Parser node and by knowledge base file uploads.
- Unsplash for the Unsplash image search node.
Knowledge base and agent settings
Settings also holds the Knowledge Base connection (your Supabase project) and the AI Agents (MCP) opt-in, each on its own tab.
How your keys are stored
Keys are encrypted at rest in your WordPress database using authenticated AES-256-GCM encryption. In Local mode your keys never leave your site: the plugin calls the provider directly from your server. The diagnostic log you can download from Settings never includes any key. See Security and privacy for the full picture.
Connecting Google and other apps
Google Sheets, Google Drive, and thousands of other services are connected through one-click sign-in on the Connect an App node, not through manual API setup in this screen.