Actions15
Overview
This node integrates with the Teamdeck API to manage bookings, projects, and time entries for project management and resource scheduling. Specifically, the Booking - Delete operation allows users to delete an existing booking by its unique ID.
Typical use cases include:
- Automatically removing outdated or canceled bookings from Teamdeck.
- Cleaning up bookings as part of a workflow triggered by external events (e.g., cancellations in a calendar system).
- Managing resource allocations dynamically by deleting bookings when resources become unavailable.
Example: A user wants to delete a booking with ID "abc123" after a client cancels a meeting. This node will send a DELETE request to Teamdeck's API to remove that booking.
Properties
| Name | Meaning |
|---|---|
| Booking ID | The unique identifier of the booking to delete. |
| Add Additional JSON | Whether to pass through additional JSON data from input to output (true/false). |
| Additional JSON | Optional JSON data to pass through from input to output if "Add Additional JSON" is enabled. |
Output
The node outputs JSON data representing the result of the delete operation:
- On success, the output JSON contains:
{ "success": true, "additionalJson": { /* optional additional JSON passed through */ } } - If "Add Additional JSON" is enabled, the provided JSON is included under the
additionalJsonfield in the output.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Teamdeck API.
- The node makes HTTP requests to the Teamdeck API endpoint at
https://api.teamdeck.io/v1/bookings. - Proper configuration of the API key credential in n8n is necessary.
Troubleshooting
Common issues:
- Missing or invalid Booking ID: The node requires a valid booking ID to delete; ensure it is correctly provided.
- Authentication errors: Verify that the API key credential is set up correctly and has sufficient permissions.
- Network or API downtime: Check connectivity and Teamdeck service status.
Error messages:
"Unknown operation: delete": Indicates an unsupported operation was requested; verify the operation parameter."Invalid API response received": The API did not return expected data; check API availability and parameters."The resource you are requesting could not be found": The booking ID may not exist or was already deleted.
Resolution tips:
- Double-check the booking ID value.
- Confirm API key validity and permissions.
- Enable "Continue on Fail" in the node settings to handle errors gracefully in workflows.