Easy Redmine icon

Easy Redmine

Easy Redmine Operations

Actions37

Overview

This node integrates with Easy Redmine to manage attendance records. Specifically, the Attendance - Create operation allows users to create new attendance entries by specifying arrival time and optional details such as departure time, description, and associated activity ID.

Common scenarios for this node include:

  • Automatically logging employee attendance times into Easy Redmine.
  • Creating attendance records from external time-tracking systems or forms.
  • Adding contextual information (description or activity) to attendance logs for better tracking.

Example use case: A company uses a form to capture employee clock-in and clock-out times. This node can be used to send those timestamps to Easy Redmine as attendance records, optionally including notes or linking to specific activities.

Properties

Name Meaning
Arrival The date and time when the attendance starts (employee arrival).
Departure (Optional) The date and time when the attendance ends (employee departure).
Description (Optional) Additional text describing the attendance entry (e.g., reason or notes).
Activity ID (Optional) Numeric identifier linking the attendance to a specific activity or task.

Output

The node outputs JSON data representing the created attendance record(s) as returned by the Easy Redmine API. Each output item corresponds to one attendance entry created.

The structure typically includes fields like:

  • id: Unique identifier of the attendance record.
  • arrival: Timestamp of arrival.
  • departure: Timestamp of departure (if provided).
  • description: Text description.
  • activityId: Linked activity identifier.

No binary data is produced by this node.

Dependencies

  • Requires an active connection to Easy Redmine via an API key credential configured in n8n.
  • The node uses the base URL from the credential's domain setting.
  • The API must support creating attendance records with the specified fields.

Troubleshooting

  • Authentication errors: Ensure the API key credential is valid and has permissions to create attendance records.
  • Invalid date/time format: The Arrival and Departure fields must be valid ISO 8601 datetime strings; otherwise, the API may reject the request.
  • Missing required fields: Arrival is mandatory; omitting it will cause errors.
  • API errors: If the API returns errors, check the error messages included in the node output for details (e.g., invalid activity ID).

If the node fails and "Continue On Fail" is disabled, execution stops on the first error. Enabling "Continue On Fail" allows processing subsequent items despite errors.

Links and References

Discussion