n8n-nodes-figranium

Official n8n community node for Figranium — trigger tasks, inspect executions, and manage schedules directly from your n8n workflows.

Resources and operations

Execute

Task Actions

Execution

Schedule

Requirements

• n8n (cloud or self-hosted) with community nodes enabled.
• Figranium server reachable from wherever n8n is running (default http://localhost:11345).
• Valid API key created via Figranium Settings.

Documentation

Full walkthrough of the n8n integration: https://figranium.dev/docs/n8n-integration

Installation

Classic (recommended)

1. In n8n, go to Settings → Community Nodes.
2. Enter n8n-nodes-figranium.
3. Install and restart n8n if prompted.

Manual (from source)

npm install
npm run build

Configuration

Credentials

The node uses the Figranium API credential type:

• Base URL — your Figranium server address, e.g. http://localhost:11345. Trim trailing slashes.
• API Key — stored securely and sent as x-api-key on every request.

Execute › Execute Task

• Task Name or ID — choose from the dropdown, which is populated via /api/tasks/list. Each option shows the task name and description (if set).
• Variables — optional key/value pairs injected at runtime under variables in the request body. Names are required; values can be empty strings.

Task Actions › Create / Update

• Name, URL, Mode (Scrape / Agent / Headful) are required on Create; all fields are optional on Update — only what you set is sent as a partial patch.
• Additional Fields / Update Fields cover the remaining task config: description, wait, selector, extraction options, rotation/stealth toggles, and three raw-JSON fields:
  • Actions (JSON) — the ordered array of automation step objects (navigate, click, type, wait_selector, if/else/end, etc.). See the n8n integration docs for the full action schema.
  • Variables (JSON) — an object of variable definitions, e.g. { "myVar": { "type": "string", "value": "" } }.
  • Stealth (JSON) — anti-bot/human-behavior flags, e.g. { "allowTypos": true, "cursorGlide": true }.

Schedule › Set Schedule

• Schedule Mode — Frequency (interval/daily/weekly/monthly) or Cron Expression.
• Frequency fields (hour, minute, days of week, day of month) appear based on the selected frequency.
• Cron accepts a standard 5-field expression, e.g. 0 9 * * 1.

Usage example — Execute a task with variables

POST {baseUrl}/api/tasks/{taskId}/api
x-api-key: {apiKey}

{
  "variables": {
    "url": "https://example.com",
    "limit": "10"
  }
}

The node returns the JSON response from Figranium as output data for downstream nodes.

Troubleshooting

• Task dropdown is empty — confirm the credential Base URL and API key, ensure n8n can reach the Figranium server, and check that /api/tasks/list returns data.
• Execute fails with HTTP error — check Figranium logs for task-specific errors and confirm the task ID still exists.
• Variables are ignored — each entry in the Variables collection must have a non-empty Name.
• Schedule operations fail — confirm the Task ID is correct and that the Figranium scheduler is running (Get Scheduler Status).

Toggling n8n workflows programmatically

If you provision or activate/deactivate n8n workflows from a script or pipeline (not through this node, but the same n8n instance it targets), be aware of a few things that are n8n-core behavior, not specific to Figranium:

• "Active" in the database ≠ "running" in the process. The n8n CLI writes workflow state straight to the database, but a running n8n process doesn't reload from the DB. A workflow toggled via the CLI will show as active/inactive everywhere you look (DB, workflow list) while the running process's actual execution behavior hasn't changed — the worst kind of bug to chase because every inspection says it worked. Always toggle workflows through n8n's public REST API, not the CLI, when doing this programmatically.
• import:workflow deactivates the workflow it imports. Don't assume an imported workflow keeps its prior active state — re-activate it explicitly after import.
• The endpoints are activate / deactivate, not publish. Hitting a publish endpoint returns a 405.
• Send Content-Type: application/json with a {} body, even for calls with no real payload. Omitting it produces a 415 that reads like an auth/permissions problem but isn't.

Diagnosing "it's active but nothing happens": the DB record and the running process can disagree, so check both sides instead of trusting one:

# 1. What the DB / API says (this is what the UI and CLI both show)
curl -s {n8nBaseUrl}/api/v1/workflows/{workflowId} \
  -H "X-N8N-API-KEY: {apiKey}" | jq '.active'

# 2. What the running process is actually doing — recent executions for this workflow
curl -s "{n8nBaseUrl}/api/v1/executions?workflowId={workflowId}&limit=5" \
  -H "X-N8N-API-KEY: {apiKey}" | jq '.data[] | {id, startedAt, status}'

If (1) says active: true but (2) shows no executions where you'd expect them (e.g. a trigger has clearly fired but nothing ran), the process hasn't picked up the DB change. Restarting the n8n process forces it to reload — that's the reliable fix once you've confirmed the split, rather than re-toggling active/inactive and hoping.

Development

npm run build   # compile TypeScript + copy icons to dist/

Load the package as a local community node or publish to npm.

License

MIT License — see LICENSE.