Actions15
Task → Create
AI-generatedOverview
This node integrates with the RogerRoger API to manage tasks within workspaces and columns. Specifically, the Task Create operation allows users to create a new task by specifying its title, workspace, column, and optional additional details such as description, tags, associated people or organizations, and due date.
Common scenarios for this node include automating task creation in project management workflows, syncing tasks from other systems into RogerRoger, or programmatically adding tasks based on triggers or events in n8n workflows.
For example, you could use this node to:
- Automatically create a follow-up task when a new lead is added.
- Generate tasks from form submissions or emails.
- Organize tasks into specific workspaces and columns dynamically based on workflow logic.
Properties
| Name | Meaning |
|---|---|
| Title | The title of the task to be created. |
| Workspace Name or ID | Select the workspace where the task will be created. Can choose from a list or specify an ID via expression. |
| Column Name or ID | Select the column within the workspace where the task will be placed. Depends on the selected workspace. Can choose from a list or specify an ID via expression. |
| Additional Fields | Optional extra fields to provide more details about the task: |
| - Description | A textual description of the task. |
| - Tags | Tags associated with the task (multiple selectable). |
| - People | People associated with the task (multiple selectable). |
| - Organizations | Organizations associated with the task (multiple selectable). |
| - Due Date | Due date and time for the task. |
Output
The node outputs JSON data representing the created task resource as returned by the RogerRoger API. The output includes at least:
resource: The resource type, here always"task".operation: The operation performed, here"create".- Other fields as returned by the API describing the newly created task, including its ID, title, workspace, column, description, tags, associated people and organizations, and due date.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the RogerRoger API.
- The node dynamically loads options for workspaces, columns, tags, people, and organizations by querying the RogerRoger API.
- Proper configuration of the API base URL and authentication token is necessary in the credentials setup.
Troubleshooting
- Invalid Workspace or Column: If the workspace or column ID/name is incorrect or not accessible with the provided API key, the API request will fail. Ensure that the workspace and column exist and the API key has sufficient permissions.
- Missing Required Fields: The "Title", "Workspace", and "Column" fields are required. Omitting these will cause validation errors.
- API Errors: Network issues or invalid API keys will result in errors. Check the API key validity and network connectivity.
- Rate Limits: Excessive requests may trigger rate limiting by the RogerRoger API; handle such errors by retrying after some delay.
- Expression Errors: When using expressions to specify workspace or column IDs, ensure the expressions resolve correctly to valid strings.
Error messages thrown by the node typically include HTTP response details from the RogerRoger API and can be resolved by verifying input parameters and credentials.
Links and References
- RogerRoger API Documentation (hypothetical link for reference)
- n8n Expressions Documentation
- n8n Node Development Guide