n8n-io/n8n · error · NodeOperationError

The resource "${resource}" is not supported!

Error message

The resource "${resource}" is not supported!

What it means

Default branch of the MiniMax router switch on the resource parameter. Supported values are audio, image, text, video; any other value falls through to this throw. Under normal UI use the resource comes from a fixed options enum so this is effectively unreachable, but a hand-edited workflow JSON, a stale node definition, or a renamed resource can land here.

Source

Thrown at packages/@n8n/nodes-langchain/nodes/vendors/MiniMax/actions/router.ts:36

		operation,
	} as MiniMaxType;

	let execute;
	switch (miniMaxTypeData.resource) {
		case 'audio':
			execute = audio[miniMaxTypeData.operation].execute;
			break;
		case 'image':
			execute = image[miniMaxTypeData.operation].execute;
			break;
		case 'text':
			execute = text[miniMaxTypeData.operation].execute;
			break;
		case 'video':
			execute = video[miniMaxTypeData.operation].execute;
			break;
		default:
			throw new NodeOperationError(this.getNode(), `The resource "${resource}" is not supported!`);
	}

	for (let i = 0; i < items.length; i++) {
		try {
			const responseData = await execute.call(this, i);
			returnData.push(...responseData);
		} catch (error) {
			if (this.continueOnFail()) {
				returnData.push({ json: { error: error.message }, pairedItem: { item: i } });
				continue;
			}

			throw new NodeOperationError(this.getNode(), error, {
				itemIndex: i,
				description: error.description,
			});
		}
	}

View on GitHub (pinned to 5ac6606e81)

Solutions

  1. Open the node in the n8n UI and re-select the resource from the dropdown to reset it to a valid enum value.
  2. Inspect the workflow JSON's resource field and correct it to one of: audio, image, text, video.
  3. Update the MiniMax node to the latest version to ensure the router and parameter enum agree.
  4. If importing a workflow, re-map the resource field to the current enum after import.
Defensive patterns

Strategy: validation

Validate before calling

const MINIMAX_RESOURCES = ['audio', 'image', 'text', 'video'] as const;
type MinimaxResource = typeof MINIMAX_RESOURCES[number];
function isValidMinimaxResource(r: unknown): r is MinimaxResource {
  return typeof r === 'string' && (MINIMAX_RESOURCES as readonly string[]).includes(r);
}

// before dispatching
const resource = this.getNodeParameter('resource', 0) as unknown;
if (!isValidMinimaxResource(resource)) {
  throw new NodeOperationError(
    this.getNode(),
    `Resource '${String(resource)}' is invalid. Supported: ${MINIMAX_RESOURCES.join(', ')}.`,
  );
}

Type guard

function isMinimaxResource(r: unknown): r is 'audio' | 'image' | 'text' | 'video' {
  return r === 'audio' || r === 'image' || r === 'text' || r === 'video';
}

Try / catch

// This is a programming/data error, not a transient one — do not retry.
// Validate up front (see validationCode) so the user gets a clear message
// instead of the generic default-branch throw.

Prevention

When it happens

Trigger: Workflow JSON has resource set to a value not in {audio, image, text, video}; node definition and router shipped out of sync (new resource added to UI but not to router switch); corrupted/migrated workflow carrying a legacy or localized resource string; programmatic workflow injection with an invalid resource.

Common situations: User edited the workflow JSON directly; imported a workflow from a newer/older n8n version where resource names differ; localization leaked a translated resource value into the parameter; custom node fork renamed resources.

Related errors

AI-assisted analysis of n8n-io/n8n@5ac6606e81 (2026-08-12). Data as JSON: /api/errors/e6a00bfa1f966377. Report an issue: GitHub.