Flowtly Create Work Time icon

Flowtly Create Work Time

Create work time entry - Clean and simple

Flowtly Create Work Time

AI-generated

Overview

This node creates a work time entry in the Flowtly system. It is useful for logging employee work hours on specific projects with details such as date, duration, and description. Typical use cases include time tracking for project management, payroll, or productivity analysis.

Use Case Examples

  1. Logging an employee's 4-hour work session on a project with a description of tasks performed.
  2. Recording work time entries for multiple employees across different projects on specific dates.

Properties

Name Meaning
Organization ID Flowtly organization ID used to identify the organization in which the work time entry is created.
Employee ID ID of the employee for whom the work time entry is being created, copied from Flowtly Get Employees output.
Project ID ID of the project associated with the work time entry, copied from Flowtly Get Projects output.
Date Date and time when the work was performed.
Duration (Hours) Duration of the work session in hours.
Description Description of the work performed during the logged time.

Output

JSON

  • success - Indicates if the work time entry creation was successful (true/false).
  • organization - The organization ID used for the entry.
  • employeeId - The employee ID for whom the entry was created.
  • projectId - The project ID associated with the entry.
  • date - The date and time of the work entry.
  • hours - The duration of the work entry in hours.
  • description - Description of the work performed.
  • workTime - The response data from Flowtly API representing the created work time entry.
  • message - A success message confirming the creation of the work time entry.
  • error - Error message if the creation failed.
  • status - HTTP status code returned from the API if an error occurred.
  • details - Additional error details from the API response if available.

Dependencies

  • Flowtly API credentials (username and password) are required for authentication.

Troubleshooting

  • Common issues include invalid or missing credentials, incorrect organization, employee, or project IDs, and network connectivity problems.
  • Error messages include HTTP status codes and API response details to help diagnose issues.
  • If the node is set to continue on fail, it will output error details instead of stopping execution.

Discussion