Connect an AI provider#

Reportworq's AI features do not embed a fixed model. Instead, an administrator configures one or more AI provider connections, each of which names a provider, holds its credentials and model selection, and carries an Enabled flag. Every AI feature, such as insights and the RWAIINSIGHT function, then resolves a model from the set of enabled connections. Configuring at least one enabled connection is the single prerequisite for all AI in the product.

When to use it. Do this once, during setup, before authors build AI-narrated reports or use the RWAIINSIGHT function. With no enabled connection, the AI features stay hidden or cannot run.

Before you start#

• Administrator access to Settings, in the AI Connections family of the integrations hub. See The integrations hub.
• Valid provider credentials for the provider you intend to use. The one exception is Reportworq AI, which uses your license entitlement rather than an API key.
• AI connections are workspace-scoped: each workspace has its own connections.

Add and enable a connection#

1. Go to Settings ▸ Integrations and choose Add integration.
2. In the AI Connections group, pick the provider tile. A new connection is created disabled, with provider defaults, and its editor opens.
3. Set a Name. This is how authors pick the connection later, and how the RWAIINSIGHT function resolves it, so make it recognizable.
4. Fill in the provider's required fields (see the table below).
5. Choose Test connection. Reportworq calls the provider and reports success or the provider's own error message.
6. Turn on Enable provider, then Save. Only enabled connections are used by downstream features. Save stays disabled until you have changed something.

Provider reference#

Notes and limits#

• OpenAI silently falls back to gpt-4o-mini when Model Id is blank. A new OpenAI connection defaults its Model Id to gpt-5.1, but if the stored Model Id is ever cleared to nothing, the connection does not error, it quietly runs on gpt-4o-mini at call time. That can surprise anyone reconciling model choice or billing against what the editor appears to show, so always keep an explicit Model Id set.
• Temperature ranges are imposed by the provider, not clamped in the form. The temperature box accepts any number; an out-of-range value is not blocked when you save, but the provider's API rejects it at call time. Stay within the ranges above (OpenAI and Azure OpenAI 0-2, Bedrock 0-1).
• Some providers are preview-gated or off in the current build.
  • Amazon Bedrock currently exposes only the Anthropic model family in the editor.
  • Azure AI Foundry exists in the code but is not registered, so it does not appear as a choice in the current build. Do not plan around it.
• Credentials are masked. API keys and AWS secret and session keys render in a masked field with autofill disabled, and are stored through the AI connection content store.
• Reportworq AI metering. The hosted connection shows monthly quota, used this month, remaining, this session, lifetime total, and the reset date, with a Check now action. Other providers are not metered centrally.

Going deeper. Every AI call made through these connections is recorded. See Audit logs. The internal prompts sent to the provider are editable in The AI prompt store.