Attio icon

Attio

Interact with Attio API

Overview

This node updates an existing task in the "Tasks" resource of the connected service via its API. It is useful when you want to modify details of a specific task, such as changing its deadline, completion status, linked records, or assignees.

Common scenarios include:

  • Updating the due date or deadline of a task.
  • Marking a task as completed or not completed.
  • Changing the people or workspace members assigned to a task.
  • Linking or unlinking related records to provide context or relationships.

For example, you might use this node to update a task's deadline after receiving new information or to assign the task to a different team member dynamically.

Properties

Name Meaning
Task Id The unique identifier of the task to update.
Data JSON object containing the fields to update on the task. Possible keys include:
- deadline_at: ISO 8601 timestamp string for the task deadline.
- is_completed: Boolean indicating if the task is completed.
- linked_records: Array of objects linking other records, each with target_object and target_record_id.
- assignees: Array of objects specifying assignees, each with referenced_actor_type and referenced_actor_id.

The Data property must be provided as a valid JSON string representing the fields and values to update.

Output

The node outputs the updated task data in the json field of the output item. This JSON contains the full representation of the task after the update, reflecting all changes made.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the external service.
  • The node makes HTTP PATCH requests to the service's /v2/tasks/{task_id} endpoint.
  • The base URL for the API is https://api.attio.com.
  • Proper permissions are needed on the API key to update tasks.

Troubleshooting

  • Invalid Task Id: If the provided Task Id does not exist or is malformed, the API will return an error. Verify the Task Id is correct.
  • Malformed JSON in Data: The Data property must be valid JSON. Parsing errors will occur if the JSON is invalid. Use proper JSON formatting.
  • Insufficient Permissions: The API key used must have permission to update tasks. Otherwise, authorization errors will occur.
  • Network Issues: Connectivity problems can cause request failures. Check network access and API availability.
  • Missing Required Fields: Some fields may be required by the API depending on the update. Ensure all necessary fields are included.

If the node throws an error mentioning operation configuration or routing, it indicates a misconfiguration in the node parameters or unsupported operation/resource combination.

Links and References

Discussion