Actions20
Overview
This node 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 ID, remote service, remote URL, and tags. This operation is useful for keeping activity records accurate and up-to-date, for example, when correcting time entries or updating project task associations.
Use Case Examples
- Updating the time spent on a specific activity to reflect actual work done.
- Changing the project or task linked to an activity after reassignments.
- Adding or modifying tags or descriptions to better categorize activities.
Properties
| Name | Meaning |
|---|---|
| Activity ID | The unique identifier of the activity to update, required to specify which activity to modify. |
| Date | The date of the activity in YYYY-MM-DD format, specifying 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 of the activity.tag- The tag associated with the activity.
Dependencies
- MOCO API
- an API key credential for MOCO API authentication
Troubleshooting
- Ensure the Activity ID is correct 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 are valid and correspond to existing entities in MOCO.
- If the API key credential is missing or invalid, authentication errors will occur.
- Network issues or API rate limits may cause request failures; retry or check connectivity.
Links
- MOCO API Activities Documentation - Official documentation for managing activities via the MOCO API.