Axelor Poll Trigger icon

Axelor Poll Trigger

Triggers when a new item created or updated

Overview

This node is a poll trigger for Axelor, designed to watch for new or updated records in a specified Axelor model. It periodically checks the Axelor API for changes and triggers workflows when matching records are found. This is useful for automating processes that depend on data changes in Axelor ERP, such as syncing data with other systems, sending notifications on record creation or updates, or triggering business logic based on record lifecycle events.

Practical examples:

  • Trigger a workflow whenever a new customer record is created in Axelor.
  • Monitor updates to sales orders and automatically update an external CRM system.
  • Watch for newly created invoices to send automated reminders.

Properties

Name Meaning
Model Name or ID Select the Axelor model to watch for changes. You can choose from a list of available models or specify a model ID using an expression.
Trigger On Choose whether to trigger on record creation ("Create") or on both new and updated records ("Update").
Limit Maximum number of records to fetch per internal request (minimum 1). The node will fetch up to this limit each poll cycle, with a maximum of 3200 internal requests allowed per operation.
Choose Where To Start Defines the starting point for watching records: either "Since specific date" to start from a given timestamp, or "All" to start from the earliest possible time (epoch).
Date If "Since specific date" is selected above, specify the exact date and time to start watching from.

Output

The node outputs an array of JSON objects representing the records fetched from the Axelor model that match the trigger criteria. Each object corresponds to one record returned by the Axelor API search endpoint.

  • The json output contains the raw record data as received from Axelor.
  • No binary data output is produced by this node.

Dependencies

  • Requires an active connection to an Axelor instance via an API key credential configured in n8n.
  • Uses Axelor REST API endpoints to query records.
  • The node depends on correct timezone handling for date filtering.
  • Requires polling to be enabled in the workflow since it is a poll trigger node.

Troubleshooting

  • No model selected error: Ensure you select a valid Axelor model before running the node.
  • Please set a poll time error: The node expects at least one poll execution time configured in the workflow settings.
  • Failed to poll for records: Could indicate network issues, invalid credentials, or API errors. Verify API connectivity and credentials.
  • If no records are returned, check that the filter dates and trigger options are correctly set and that there are relevant changes in Axelor.
  • Large limits or frequent polling may hit API rate limits or performance bottlenecks; adjust accordingly.

Links and References

Discussion