Flowyteam icon

Flowyteam

Custom node for Flowyteam API

Actions101

Overview

The "Clock Out" operation of the Attendance resource allows users to record the end time of an employee's attendance session. This is typically used in workforce management scenarios where tracking the exact clock-out time is necessary for payroll, attendance monitoring, and productivity analysis.

Practical examples include:

  • An employee finishing their workday and recording their clock-out time.
  • Automated workflows that update attendance records at the end of shifts.
  • Integration with HR systems to maintain accurate attendance logs.

Properties

Name Meaning
Attendance ID The ID of the attendance record to clock out

Output

The node outputs a JSON object representing the updated attendance record after the clock-out operation. This typically includes details such as the attendance ID, clock-in time, clock-out time, and possibly other metadata related to the attendance session.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Flowyteam API.
  • The node depends on the Flowyteam service endpoint responsible for managing attendance records.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Attendance ID will likely result in an error indicating the record cannot be found.
    • Missing or incorrect API authentication credentials will cause authorization failures.
    • Network connectivity problems can prevent communication with the Flowyteam API.
  • Error messages and resolutions:

    • "The operation 'clockOut' is not supported for Attendance resource": This indicates a misconfiguration or typo in the operation name; ensure "clockOut" is selected.
    • "Attendance record not found": Verify that the Attendance ID provided exists and is correct.
    • Authentication errors: Check that the API key credential is correctly set up and has sufficient permissions.
    • Timeouts or network errors: Confirm network connectivity and API endpoint availability.

Links and References

Discussion