Official n8n community node for Figranium — trigger tasks, inspect executions, and manage schedules directly from your n8n workflows.
| Operation | Description |
|---|---|
| Execute | Run a saved task and return its result. Accepts optional runtime variables. |
| List | Return all task IDs, names, and descriptions from the server. |
| Operation | Description |
|---|---|
| List | Return a summary of all past execution records. |
| Operation | Description |
|---|---|
| List | Return all tasks that have a schedule configured. |
| Get Status | Get the schedule config and next run time for a specific task. |
| Set Schedule | Create or update a schedule on a task (frequency-based or cron). |
| Delete Schedule | Disable and remove the schedule from a task. |
| Describe Schedule | Validate and preview a schedule config without saving it. |
| Get Scheduler Status | Return the overall status of the task scheduler. |
- 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.
Full walkthrough of the n8n integration: https://figranium.dev/docs/n8n-integration
- In n8n, go to Settings → Community Nodes.
- Enter
n8n-nodes-figranium. - Install and restart n8n if prompted.
npm install
npm run buildThe 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-keyon every request.
- Task — 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
variablesin the request body. Names are required; values can be empty strings.
- Schedule Mode —
Frequency(interval/daily/weekly/monthly) orCron 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.
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.
- Task dropdown is empty — confirm the credential Base URL and API key, ensure n8n can reach the Figranium server, and check that
/api/tasks/listreturns 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).
npm run build # compile TypeScript + copy icons to dist/Load the package as a local community node or publish to npm.
Apache License 2.0 — see LICENSE.