Actions90
- Activity Actions
- Company Actions
- Contact Actions
- Deal Actions
- Project Actions
- User Actions
Overview
This node operation updates an existing activity in the MOCO system. It allows users to modify details such as the date, associated project and task, time spent (in seconds), description, and additional optional fields like billable status, remote identifiers, remote service, remote URL, and tags. This operation is useful for keeping activity records accurate and up-to-date, for example, when correcting logged time or updating activity descriptions after the fact.
Use Case Examples
- Updating the time spent on a specific activity to reflect actual work done.
- Changing the project or task associated with an activity to correct misclassification.
- Adding or modifying tags or remote service information for better tracking and integration with other systems.
Properties
| Name | Meaning |
|---|---|
| Activity ID | The unique identifier of the activity to update, required to specify which activity record to modify. |
| Date | The date of the activity in YYYY-MM-DD format, representing when the activity took place. |
| Project Name or ID | The project associated with the activity, selectable from a list or specified by ID. |
| Task Name or ID | The task within the project associated with the activity, selectable from a list or specified by ID. |
| Seconds | The amount of time spent on the activity, expressed in seconds. |
| Description | A textual description of the activity. |
| Additional Fields | Optional fields to provide extra details about the activity, including billable status, remote ID, remote service, remote URL, and tags. |
Output
JSON
id- The unique identifier of the updated activity.date- The date of the updated activity.project_id- The ID of the project associated with the updated activity.task_id- The ID of the task associated with the updated activity.seconds- The time spent on the activity in seconds.description- The description of the updated activity.billable- Indicates if the activity is billable.remote_id- The remote identifier of the activity.remote_service- The remote service associated with the activity.remote_url- The remote URL linked to the activity.tag- The tag assigned to the activity.
Dependencies
- MOCO API
- An API key credential for MOCO API authentication
Troubleshooting
- Ensure the Activity ID provided is valid and exists in the MOCO system; otherwise, the update will fail with a not found error.
- Verify that the date is in the correct YYYY-MM-DD format to avoid validation errors.
- Check that the project and task IDs correspond to existing entries, especially if specifying them manually or via expressions.
- If the API key credential is missing or invalid, authentication errors will occur; ensure proper credential configuration in n8n.
- When using optional fields, ensure their values conform to expected types and formats to prevent request rejection.
Links
- MOCO API Activities Documentation - Official MOCO API documentation for managing activities, including update operations.