Axelor Poll TriggerInstall

Summary

Polls an Axelor model on the configured schedule and emits records created since the previous poll, or records created or updated since then. Uses node-level workflow static data to save the last check time between polls.

Inputs

• Poll Times (required) — One or more schedules for polling, such as every minute, hour, day, week, month, every X minutes or hours, or a custom cron expression. The operation errors if no poll time is configured.
• Model Name or ID (required) — Axelor model to search, selected from the available models or supplied as an expression.
• Trigger On (required) — Choose Create to match records whose createdOn timestamp is at or after the last check, or Update to match records whose createdOn or updatedOn timestamp is at or after it.
• Limit — Maximum number of results requested per poll; defaults to 50.
• Choose Where To Start (required) — Choose All to start from the Unix epoch, or Since specific date to use the supplied Date as the initial cutoff. Later polls use the saved last-check time.
• Date (required) — Starting date and time used when Choose Where To Start is Since specific date; converted using the workflow timezone.

Output shape

A list of n8n items, each containing an Axelor record in its JSON data; returns no output when the search finds no records.

The search is an Axelor POST request using the selected model, limit, and timestamp criteria. The last-check time is saved after a successful request, including when it returns no records. The UI hint says there can be at most 3,200 internal requests in one operation, but the poll implementation makes one search request.

Links

• n8n community nodes installation guide