Actions92
- Contact Actions
- Employee Actions
- Estimate Actions
- Invoice Actions
- Job Actions
- Line Item Actions
- Note Actions
- Setting Actions
- Supplier Actions
- Task Actions
- Technician Actions
- User Actions
- Website Actions
- WhatsApp Actions
Overview
This node integrates with the WibiClick API to manage various resources, including tasks. Specifically, for the Task resource and the Get Task operation, it retrieves detailed information about a single task by its ID.
Typical use cases include:
- Fetching details of a specific task in a workflow to process or analyze it further.
- Integrating task data retrieval into automation flows where task status or details influence subsequent steps.
- Synchronizing task information from WibiClick into other systems or databases.
Example: You have a task ID from a previous step or external source, and you want to get all details about that task (such as title, associated job/customer, status) to decide on next actions like notifications or updates.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to retrieve. This is required to specify which task's details to fetch. |
Output
The output JSON contains the full details of the requested task as returned by the WibiClick API. This typically includes fields such as task title, associated job or customer IDs, status, creation date, and any other metadata the API provides for a task.
If the task is not found, the node throws an error indicating "Task not found".
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the WibiClick API via an API key credential.
- The node uses HTTP requests to communicate with the WibiClick API endpoints.
- The API key must be configured in n8n credentials for authentication.
Troubleshooting
- Task not found error: If the specified Task ID does not exist or is incorrect, the node will throw a "Task not found" error. Verify the Task ID is correct and exists in your WibiClick account.
- Unexpected error: Other HTTP or network errors will result in a generic "An unexpected error occurred" message. Check network connectivity and API key validity.
- Missing Task ID: Since Task ID is required, ensure it is provided and not empty; otherwise, the node will fail before making the request.
- API Key issues: Invalid or missing API key credentials will cause authentication failures. Confirm the API key is correctly set up in n8n.
Links and References
- WibiClick API Documentation (Assumed URL, replace with actual if known)
- n8n HTTP Request Node documentation for understanding underlying HTTP calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
This summary focuses solely on the "Task" resource and "Get Task" operation as requested, based on static analysis of the provided source code and input properties.