Skip to main content
The official Figranium n8n community node (n8n-nodes-figranium) lets you trigger tasks, create and update task definitions, inspect execution history, manage schedules, and work with Figranium browser sessions directly from n8n. Task Create and Update also expose the per-task Cabinet ID field.

​
Installation

Figranium is a verified n8n community node, so you install it directly from the n8n node picker instead of manually entering an npm package name.
1

Open a workflow

Open an existing workflow in n8n or create a new one.
2

Add a node

Click Add node and search for Figranium.
3

Install Figranium

Select Figranium and install the verified community node when prompted.
4

Add it to your workflow

Once installed, add the Figranium node like any other n8n node and connect your Figranium credentials.
On self-hosted n8n instances, an instance owner may need to approve or install verified community nodes first. After that, everyone on the instance can use Figranium in workflows.

​
Credentials

The node authenticates using a Figranium API credential.
1

Add a new credential

Go to Credentials and click Add Credential.
2

Search for Figranium

Search for Figranium API.
3

Fill in the fields

Fill in the two fields:

​
Node Overview

The Figranium node exposes several top-level resources and operations.

Execute

Run a saved task with optional runtime variable overrides.

Task Actions

List, create, partially update, or delete saved tasks, including the Cabinet ID field.

Execution

Retrieve lightweight execution history for downstream workflow logic.

Schedule

List, inspect, set, delete, describe, and check scheduler status.

Browser

Launch or reattach to a managed Figranium browser session.

Inspector

Highlight and resolve elements in an active browser session.

​
Execute

Runs a saved task and returns its result as JSON.ParametersAPI call: POST /api/tasks/{taskId}/apiOutput: The full JSON response from the task execution.

​
Task Actions

Task Create and Update expose the task configuration fields supported by the node. Both include an optional Cabinet ID field for per-task download Cabinet selection; leave it empty to use the instance’s default Cabinet.
Returns all tasks available on the connected Figranium server.Parameters: None beyond the credential.API call: GET /api/tasks/listOutput: One item per task, each containing at minimum a name and id field.
Creates a task from n8n. Required fields are Name, URL, and Mode. Additional fields include task description, waits, selectors, extraction settings, rotation/stealth settings, raw Actions/Variables/Stealth JSON, and Cabinet ID.Cabinet ID selects the Cabinet that receives intercepted downloads for this task. If omitted, Figranium uses the default Cabinet.
Partially updates an existing task. Only fields you set are sent to Figranium, so you can change one property without replacing the full task definition.Cabinet ID can be set or changed here to route future intercepted downloads to a different Cabinet.
Permanently deletes the selected task.

​
Execution

Returns a summary of all past task executions recorded by Figranium.Parameters: None beyond the credential.API call: GET /api/executions/listOutput: An array of execution records. Each record typically includes the task ID, execution timestamp, status, and a result summary.

​
Schedule

Returns all tasks that currently have a schedule configured.Parameters: None beyond the credential.API call: GET /api/schedulesOutput: An array of schedule objects, one per scheduled task.
Returns the schedule configuration and the next calculated run time for a specific task.ParametersAPI call: GET /api/schedules/{taskId}/statusOutput: A single object containing the schedule definition and the nextRun timestamp.
Creates or updates the schedule for a task. Two scheduling modes are available: Frequency (a structured picker) or Cron Expression (a raw cron string).ParametersWhen Schedule Mode is “Frequency”When Schedule Mode is “Cron Expression”API call: POST /api/schedules/{taskId}Output: The saved schedule object.
Disables and removes the schedule from a task. The task itself is not deleted.ParametersAPI call: DELETE /api/schedules/{taskId}Output: A confirmation object.
Validates a schedule configuration and returns a human-readable preview (e.g. next run times) without saving anything. Useful for testing cron expressions before committing them.ParametersAPI call: POST /api/schedules/{taskId}/describeOutput: A preview object describing when the schedule would fire.
Returns the overall health and status of the Figranium task scheduler — not tied to any specific task.Parameters: None beyond the credential.API call: GET /api/schedules/status/allOutput: A status object for the scheduler engine (e.g. running, paused, number of active schedules).

​
Browser

Launches or reattaches to a managed Figranium browser session. The optional URL field sets the starting page.The node currently targets Figranium’s managed headful browser flow; the Mode field is informational.

​
Inspector

Highlights and inspects elements in an active browser session. You can optionally provide a Session ID, URL, and Target Hint to narrow down the element Figranium should resolve.

​
Troubleshooting

  • Confirm your Base URL is reachable from the n8n host (not just from your browser).
  • Verify the API Key is valid.
  • Check n8n logs for 401 Unauthorized or 404 Not Found errors during the “load options” phase.
If both n8n and Figranium run in Docker on the same machine, localhost in the Base URL will resolve to the n8n container itself. Use your host machine’s internal IP or the Docker bridge IP (e.g. http://172.17.0.1:11345) instead.
Variable Name values are case-sensitive and must match the variable names defined in the task exactly.
If you need to pass dynamic values from earlier n8n nodes, use n8n expressions in the Variables fields. For example, set a variable value to {{ $json.product_url }} to forward data from a webhook trigger.