WibiClick icon

WibiClick

Interact with WibiClick API

Actions92

Overview

This node integrates with the WibiClick API to manage tasks within a system. Specifically, the "Update Task" operation allows users to update details of an existing task by providing the task's ID and new information such as title, associated job ID, or customer ID.

Common scenarios where this node is beneficial include:

  • Automating updates to task records in response to changes elsewhere in a workflow.
  • Synchronizing task data between WibiClick and other systems.
  • Modifying task attributes programmatically without manual intervention.

For example, if a job's status changes and you want to update related tasks' titles or associations automatically, this node can perform that update seamlessly.

Properties

Name Meaning
Task ID The unique identifier of the task to update (required).
Task Details A collection of fields to update on the task:
- Title: New title of the task.
- Job ID: New ID of the associated job.
- Customer ID: New ID of the associated customer.

Output

The output JSON contains the updated task object returned from the WibiClick API after a successful update. It reflects the current state of the task including any changed fields.

Example output structure:

{
  "id": "string",
  "title": "string",
  "jobId": "string",
  "customerId": "string",
  // ... other task properties as returned by the API
}

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.
  • Proper API URL and authentication token must be configured in the node credentials.

Troubleshooting

  • Task not found error: If the provided Task ID does not exist, the node throws an error indicating "Task not found". Verify the Task ID is correct.
  • Invalid task details: If the update payload is malformed or missing required fields, the node returns "Invalid task details". Ensure all fields conform to expected formats.
  • Unexpected errors: Other HTTP or network issues will result in generic error messages. Check API connectivity and credentials.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one update fails, returning success status per item.

Links and References

Discussion