AI agent service connections
Run supported AI features through AiFlow or a configured external agent service while INSIDE manages conversation delivery.
What it is
Harness selects the service that runs an AI agent's work. INSIDE can use its built-in AiFlow execution or a configured external service such as Salesforce Agentforce. Replies still return through INSIDE's conversation and delivery handling.
Who uses it and why
Users with Settings and permission to manage AI, or Developer, choose an account prepared by Powerfront for their AI feature. Developers work with Powerfront to connect an external agent service and decide which INSIDE tools it may use.
Operators and visitors continue using the conversation. They do not choose the harness for each reply.
Where to find it
Powerfront manages Harness at Settings › AI › Accounts and external service configuration at Settings › AI › Connections.
You select the feature's Account at Settings › AI › Features, using Settings with permission to manage AI, or Developer.
How it works
- The selected account determines how supported Ask AI, Copilot and Autopilot work runs, unless the feature already has a specific override.
- INSIDE sends the request to the selected service and receives its answer.
- Where configured, the service can call permitted INSIDE functions. Access is limited to the tools authorised for that run.
- INSIDE applies its configured processing to the result before returning it to the relevant conversation or operator.
An external service may return only a final answer rather than a streamed draft. Selecting a different harness does not make all services support the same functions.
Configure it
Ask Powerfront to prepare the AI account and connection for the execution service you want. For Salesforce Agentforce, this includes the Salesforce connection, agent configuration and any permitted INSIDE tool access.
Then select the prepared Account on the relevant feature and save.
New accounts default to AiFlow. Older accounts without a saved selection use AiFlow when a model provider is configured, otherwise Legacy. External requests default to a five-minute timeout. Powerfront can change the timeout and configure an optional fallback to AiFlow.
Settings
| Setting | Where | Applies to | Default | Who can change it | What it does |
|---|---|---|---|---|---|
| Harness | Settings › AI › Accounts | website | AiFlow for new accounts; older accounts without a selection use AiFlow when a model provider is configured, otherwise Legacy | Powerfront | Selects how the account runs AI work, including a configured Salesforce Agentforce service. |
| Account | Settings › AI › Features | website | Not set: an account must be selected before saving | Settings role, Developer role | Selects the AI account used by the feature, including its configured harness. |
Permissions
| Permission | Lets you |
|---|---|
| Settings | Select an account on AI features when AI is allowed under Settings Permissions. |
| AI | Allows AI configuration within Settings Permissions. |
| Developer | Configure AI features using accounts prepared by Powerfront. |
Limits and good to know
- Automatic fallback is off by default.
- Optional fallback is restricted to eligible failures before actions have been recorded as performed. Once an INSIDE tool has been attempted, fallback is suppressed to avoid repeating work.
- A timeout or cancellation does not guarantee a fallback run.
- An unknown or unavailable execution service causes the request to fail rather than silently choosing another service.
- External tools use run-specific access that expires. They do not receive unrestricted access to your INSIDE website.
- Where personal-data protection is configured, a failure to protect external tool results can stop execution.
- External-output safety pushback can apply its configured failure action without rerunning the external agent.
Depends on and works with
View all connections as a list
This feature uses
- AI feature settings and change historyConfigured by
Supported features select the AI account used for execution.
- AI run limitsEnhances
AiFlow is the built-in execution option and an optional fallback.
- AI functions and required inputsEnhances
External agents can receive access to permitted INSIDE functions.
- AI guardrail routing and fallback actionsEnhances
Configured safety decisions can block external agent output.
- AI accounts and shared defaultsRequires
The selected AI account supplies the harness and service configuration.
- Shared AI service connectionsConfigured by
Powerfront configures the external service connection selected for agent execution.
- Personal information masking for AIEnhances
Configured personal-data protection also applies to external execution and tool results.
Used by
- AI run limitsRelated
The selected execution service determines whether built-in AI flow limits apply.
- AI accounts and shared defaultsConfigured by
The selected harness determines which service executes the feature.
- Shared AI service connectionsEnhances
External agent connections can supply an alternative AI execution service.
- Salesforce Models API connectionRelated
Salesforce Models generates text with a selected model, while Agentforce runs a configured Salesforce agent.
FAQ and troubleshooting
Why cannot I change Harness?
Powerfront manages AI account execution settings. Ask Powerfront to change the service for you.
Why did an external service failure not switch to AiFlow?
Fallback is off by default and is limited when enabled. It is suppressed after a tool attempt or recorded action.
Why is the reply delivered only when complete?
The selected service may not support streamed replies. INSIDE can deliver a final result from such services.
Why cannot the external agent use an INSIDE function?
The tool must be permitted for that feature and run, remain available, and pass INSIDE's execution checks. Ask Powerfront to review the connection if the feature's assignments are correct.