Actions101
- Attendance Actions
- Client Actions
- Department Actions
- Designation Actions
- Employee Actions
- Holiday Actions
- KPI Actions
- KPI Category Actions
- KPI Data Actions
- Lead Actions
- Leave Actions
- OKR Key Result Actions
- OKR Objective Actions
- Performance Cycle Actions
- Project Actions
- Project Category Actions
- Task Actions
- Task Category Actions
- Ticket Actions
- Ticket Agent Actions
- Ticket Channel Actions
- Ticket Type Actions
Overview
The node provides integration with the Flowyteam API, allowing users to manage various HR and project management resources. Specifically, for the Attendance resource with the Clock In operation, the node enables employees to record their clock-in time along with the location they are working from.
This is useful in scenarios where organizations want to track employee attendance remotely or on-site, ensuring accurate timekeeping and location data for payroll, compliance, or productivity analysis.
Practical example:
An employee starts their workday and uses this node to "clock in" by specifying their current working location (e.g., "Home Office", "Headquarters", or "Client Site"). The node sends this information to Flowyteam, which records the attendance entry.
Properties
| Name | Meaning |
|---|---|
| Working From | Location where you are working from (string). This is a required field and should specify the employee's current work location at clock-in time. |
Output
The node outputs JSON data representing the result of the clock-in action. This typically includes details such as:
- Confirmation of the clock-in event.
- Timestamp of the clock-in.
- The specified working location.
- Possibly other metadata related to the attendance record.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Flowyteam API.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- The node depends on the Flowyteam service being available and reachable over the network.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing an empty or invalid "Working From" value will likely result in validation errors.
- Network connectivity problems can prevent successful API calls.
- Using unsupported operations or resources will throw errors.
Error messages:
"The operation '...' is not supported for Attendance resource": Indicates an unsupported operation was selected.- Authentication errors: Check that the API key or token is correctly set up in n8n credentials.
- Validation errors about missing required fields: Ensure "Working From" is provided and non-empty.
Links and References
- Flowyteam Official Website
- Flowyteam API Documentation (for detailed API endpoints and parameters)