Attio icon

Attio

Interact with Attio API
Join our community

Actions52

Overview

This node allows you to create a new task in the "Tasks" resource of the connected service via its API. It is useful for automating task creation workflows, such as adding follow-up tasks, reminders, or action items based on other triggers or data sources within your automation.

For example, you can use this node to automatically create a task to "Follow up on current software solutions" with a specific deadline and assign it to workspace members or link it to related records like people or projects.

Properties

Name Meaning
Data JSON object representing the task details to create. This includes fields such as:
- content: The description or title of the task.
- deadline_at: The deadline timestamp for the task.
- is_completed: Boolean indicating if the task is completed.
- linked_records: Array of objects linking the task to other records (e.g., people) by specifying target object type and record ID.
- assignees: Array of assignee objects specifying the type and ID of actors assigned to the task (e.g., workspace members).

The property expects a valid JSON string that will be parsed and sent as the request body.

Output

The node outputs the JSON response from the API after creating the task. The output JSON contains the created task's details as returned by the API, including any generated IDs, timestamps, and the properties you set.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the external service.
  • The node sends HTTP requests to the service's API endpoint (https://api.attio.com/v2/tasks).
  • Proper configuration of the API authentication token in n8n credentials is necessary.

Troubleshooting

  • Invalid JSON in Data property: If the JSON string provided in the "Data" property is malformed, the node will fail to parse it. Ensure the JSON is valid before running.
  • Authentication errors: If the API key or token is missing, expired, or invalid, the node will return authorization errors. Verify the API credentials are correctly configured.
  • Missing required fields: The API may reject requests missing mandatory task fields like content. Make sure all required fields are included in the JSON.
  • API rate limits or downtime: Temporary failures might occur due to API limits or service issues. Retrying later or handling errors gracefully is recommended.
  • Error messages typically include HTTP status codes and descriptive messages from the API. Review these messages to adjust input data or credentials accordingly.

Links and References

Discussion