Actions15
Overview
This node integrates with the Teamdeck API to manage time tracking, project management, and resource scheduling data. Specifically, for the Time-Entry Delete operation, it allows users to delete a specific time entry by its ID from their Teamdeck account.
Common scenarios where this node is beneficial include:
- Automatically cleaning up or removing incorrect or obsolete time entries in Teamdeck.
- Integrating with other workflows that require conditional deletion of time entries based on external triggers or data.
- Managing time tracking data programmatically without manual intervention in the Teamdeck UI.
Example use case:
- A workflow that deletes a time entry when a related task is canceled in another system, ensuring time tracking data stays accurate.
Properties
| Name | Meaning |
|---|---|
| Add Additional JSON | Whether to add extra JSON data from input to output (boolean). |
| Additional JSON | The JSON data to pass through from input to output if "Add Additional JSON" is enabled. |
| Time Entry ID | The unique identifier of the time entry to delete (string, required). |
Output
The node outputs JSON data indicating the success of the deletion operation. The structure includes:
success: A boolean value (true) confirming the time entry was deleted successfully.additionalJson: If enabled, any additional JSON data passed through from input to output.
Example output JSON:
{
"success": true,
"additionalJson": { /* optional user-provided JSON */ }
}
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Teamdeck API.
- The node makes HTTP DELETE requests to the Teamdeck API endpoint for time entries.
- The base URL used is
https://api.teamdeck.io/v1/time-entries.
Troubleshooting
Common Issues
- Invalid or missing Time Entry ID: The operation requires a valid time entry ID. Omitting or providing an incorrect ID will cause errors.
- Authentication failures: Ensure the API key credential is correctly configured and has sufficient permissions.
- API rate limits or network issues: Temporary failures may occur due to API limits or connectivity problems.
Error Messages
"Unknown operation: delete": This would indicate an internal misconfiguration; ensure the operation parameter is set correctly."Invalid API response received": The API did not return expected data; check network and API status.- Errors including HTTP status codes (e.g., 404) typically mean the specified time entry does not exist or cannot be accessed.
Resolution Tips
- Verify the Time Entry ID exists in Teamdeck before attempting deletion.
- Confirm API credentials are valid and have necessary access rights.
- Use the node's "Continue On Fail" option to handle errors gracefully in workflows.
Links and References
- Teamdeck API Documentation
- Teamdeck Time Entries API Endpoint
- n8n Documentation on Creating Custom Nodes