# Custom scripts managed by Powerfront

Powerfront can load and refresh custom scripts that adapt INSIDE to your integration requirements without restarting the service.

*Release 3.3 · developer*

**Inside Dev Console › Tools › Custom Scripts**

## What it is

Custom scripts adapt INSIDE to integration requirements beyond the standard configuration. INSIDE can prepare deployed C# scripts for execution and refresh them while the service is running. Powerfront manages deployment and runtime updates for you.

## Who uses it and why

As a developer, you work with Powerfront on the behaviour, website access and expected results of a custom integration. Operators and visitors use the resulting tools or workflow behaviour without compiling scripts themselves.

## Where to find it

Powerfront manages scripts through **Inside Dev Console › Tools › Custom Scripts**. This screen is separate from **Settings**. The **Developer** role displays the development console; Powerfront manages script updates for you.

## How it works

INSIDE loads scripts from its configured deployment location. Each script supplies a name, category, identifier and website scope. These determine where the script can be selected or invoked.

Powerfront has three update options:

- **Update Scripts** loads new scripts, recompiles scripts whose contents changed and removes deleted scripts from the script list and selectors. Unchanged scripts are skipped.
- **Recompile All Scripts** prepares all scripts in the configured location again.
- **Recompile** on an individual row reloads that script.

The screen shows loaded and failed totals, each script's **Name**, **Script**, **Category**, **Last Compiled** time and any compilation errors. A load result describes whether the script was prepared successfully. It does not prove that a subsequent integration request completed successfully.

## Configure it

Ask Powerfront to deploy or change your custom script. Agree which websites should use it and which event, workflow or AI function should invoke it.

After deployment, Powerfront refreshes the scripts and checks each affected script's load status. If an update is already running, Powerfront waits for it to finish before another update. Then check the actual integration behaviour, including its failure response.

### Permissions

| Permission | Lets you |
|---|---|
| Developer | Displays the development console; script loading and recompilation require Powerfront-managed access. |

## Limits and good to know

- A failed replacement can remove the previous script from use. Do not assume an automatic return to the previous working version.
- A successful overall update response can still contain failed scripts. Ask Powerfront to check individual load results.
- If you are retiring an integration that also provides API operations, ask Powerfront to confirm those operations have been withdrawn as well.
- Updating scripts can run their initialisation again. Integrations with background work or external side effects need particular care during refreshes.
- Script execution failures can return an empty or fallback result, or report an error, depending on how the script is invoked.
- Runtime scripts execute within INSIDE and can use its services. Powerfront must review and manage executable changes.

## Depends on and works with

### This feature uses

- **Configured in** [Roles and permissions](ADM-008.md): Development tools and script management have separate access checks.
- **Works better with** [Integration script selection for automated actions](EXT-016.md): Loaded scripts can appear in category-specific selectors and respond to platform events.
- **Works better with** [Custom integrations](EXT-017.md): Custom integrations use the script runtime for website-specific behaviour.
- **Related** [INSIDE API](EXT-018.md): Custom scripts can expose additional API operations with their own access checks.

### Used by

- **Required by** [Click to Call callback form](RTC-036.md): A configured callback script processes the submitted request.
- **Required by** [Custom commerce integrations](COM-006.md): Powerfront must deploy an available custom commerce script before it can be selected as a provider.
- **Required by** [Custom CRM integration](CRM-022.md): Custom CRM behaviour uses the website's managed custom-script capability.
- **Required by** [Integration script selection for automated actions](EXT-016.md): Scripts must be deployed and loaded before they can be selected or invoked.
- **Required by** [Custom integrations](EXT-017.md): Script-based custom integrations need a deployed and loaded script.
- **Required by** [Custom scripts in email event rules](EXT-022.md): Script conditions and actions depend on scripts configured by Powerfront.
- **Configures** [AI model provider selection](AIP-003.md): Powerfront-managed custom scripts can supply an additional provider integration.
- **Configures** [Store product selection for chat](COM-009.md): An existing custom product-search integration can take precedence over commerce panel replacement.
- **Configures** [Sales attribution to conversations and operators](COM-021.md): A website-specific integration can override default conversation and operator selection.
- **Configures** [Purchase details and conversion credit](COM-030.md): A Powerfront-managed custom integration can replace the default purchase-history results.
- **Configures** [Media callbacks and embedded form results](EXT-021.md): Powerfront configures the website-specific script that processes an embedded result.
- **Enhances** [Task integrations, appointments and embedded pages](ENG-017.md): Custom script installation makes registered integration scripts available.
- **Enhances** [Virtual Assistant task import and export](ENG-019.md): Powerfront installs the transfer integration used by configuration imports.
- **Enhances** [AI instructions and templates](AI-002.md): A website customisation can supply instructions before external or local instructions.
- **Enhances** [Email Autopilot for tickets](AI-012.md): A Powerfront-arranged customisation can replace the standard decision processing.
- **Enhances** [Context Compiler for AI conversations](AI-015.md): A Powerfront-arranged custom compiler can prepare the context while retaining protected instructions and recent input.
- **Enhances** [AI integrations and automation tools](AI-018.md): Custom Script functions need a configured script implementation.
- **Enhances** [AI product suggestion settings](AI-027.md): A Powerfront-arranged website script can replace the built-in product-suggestion process.
- **Enhances** [AI resolution and first-contact metrics](AI-030.md): A Powerfront-arranged website script can replace the built-in metrics evaluation.
- **Enhances** [Tracked product search and integrations](COM-018.md): Existing website customisations can supply search results and basket-action information.

## FAQ and troubleshooting

### Why has my new script not appeared?

Ask Powerfront to check deployment, load status, website scope and category. Copying an updated script alone does not confirm it has been loaded.

### Why does the update look successful while the integration fails?

Ask Powerfront to check the affected script's load status and then its actual execution. The overall update result is not proof that every script compiled or every external service responded.

### Can a refresh restore the previous working script automatically?

Do not rely on that. Ask Powerfront to correct or restore the deployed script and reload it if a replacement fails.

### Do we need to restart INSIDE for a script change?

The script update and recompilation controls can apply changes while INSIDE is running. Powerfront checks the affected integration after the refresh.