n8n-nodes-figranium) lets you trigger tasks, inspect execution history, and manage schedules from within any n8n workflow.
Installation
- In n8n, go to Settings > Community Nodes.
- Click Install a community node.
- Enter
n8n-nodes-figraniumand agree to the risks. - Restart n8n if prompted.
Credentials
The node authenticates using a Figranium API credential.- Go to Credentials and click Add Credential.
- Search for Figranium API.
- Fill in the two fields:
Node Overview
The Figranium node exposes three top-level resources, each with one or more operations.Task
Execute
Runs a saved task and returns its result as JSON. Parameters
API call:
POST /api/tasks/{taskId}/api
Output: The full JSON response from the task execution — typically includes result data, status, and metadata.
Example use case: A webhook fires when a new order arrives. The Figranium node executes a “Scrape Competitor Price” task, passing product_url as a variable extracted from the webhook payload. The result flows into a database insert node.
List
Returns all tasks available on the connected Figranium server. Parameters: None beyond the credential. API call:GET /api/tasks/list
Output: One item per task, each containing at minimum a name and id field.
Execution
List
Returns a summary of all past task executions recorded by Figranium. Parameters: None beyond the credential. API call:GET /api/executions/list
Output: An array of execution records. Each record typically includes the task ID, execution timestamp, status, and a result summary.
Schedule
List
Returns all tasks that currently have a schedule configured. Parameters: None beyond the credential. API call:GET /api/schedules
Output: An array of schedule objects, one per scheduled task.
Get Status
Returns the schedule configuration and the next calculated run time for a specific task. Parameters
API call:
GET /api/schedules/{taskId}/status
Output: A single object containing the schedule definition and the nextRun timestamp.
Set Schedule
Creates or updates the schedule for a task. Two scheduling modes are available: Frequency (a structured picker) or Cron Expression (a raw cron string). Parameters
When Schedule Mode is “Frequency”
When Schedule Mode is “Cron Expression”
API call:
POST /api/schedules/{taskId}
Output: The saved schedule object.
Delete Schedule
Disables and removes the schedule from a task. The task itself is not deleted. Parameters
API call:
DELETE /api/schedules/{taskId}
Output: A confirmation object.
Describe Schedule
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. Parameters
API call:
POST /api/schedules/{taskId}/describe
Output: A preview object describing when the schedule would fire.
Get Scheduler Status
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/all
Output: A status object for the scheduler engine (e.g. running, paused, number of active schedules).
Troubleshooting
Task dropdown is empty
- 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 Unauthorizedor404 Not Founderrors during the “load options” phase.
Connection refused in Docker
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.