Configuration
Everything is set from the console's Configuration page — stored on the server, effective next cycle, no redeploy. Secrets are stored write-only and never shown back.
AI / Reasoning
Which LLM does the reasoning. PowerExecutor routes through LiteLLM, so any provider works — cloud or local.
| Field | What to enter |
|---|---|
| Provider | e.g. openai, anthropic, deepseek, ollama. Combined with the model as provider/model. Leave blank only if your Model already includes the prefix (e.g. deepseek/deepseek-chat). |
| Model | The model name, e.g. deepseek-chat, claude-sonnet-4-6, llama3.1. |
| API key | Key for the provider. Blank for local models. |
| API base URL | Provider or local endpoint, e.g. https://api.deepseek.com or http://ollama:11434. |
Several models, specialized per task (advanced)
Below the AI fields you can register multiple models — e.g. a tiny local model for simple tasks and a commercial one for complex reasoning — and assign which model handles which task ("Reasoning" is active today; more task types are coming). Each model has its own provider, name, API base and key (keys are write-only). If no models are registered, the single AI settings above are used for everything.
Connection — <product>
The credentials PowerExecutor uses to log in to the product it operates. Pick the product with the selector in the Configuration header — the fields are declared by that product's adapter spec (see Adapters & products), so they differ per product. For PowerMarketing:
| Field | What to enter |
|---|---|
| Username | PowerMarketing login username (e.g. admin). |
| Password | The real PowerMarketing admin password. |
| Brand id | Which brand to operate. Blank = the first brand the account can access. A brand must exist in PowerMarketing. |
Operations
| Field | What to enter |
|---|---|
| Action budget / day | Max real actions per day (safety cap). |
| Enabled products | Comma-separated products the daily scheduler operates. |
| Cycle hour (UTC) | The UTC hour the daily cycle runs. |
Saving
Saving is a consequential action, so it needs the Supervisor PIN. If a PIN is set on the server, the console asks for it when you save and remembers it for the session (in memory only — never stored in the browser).