Overview

This node interacts with the MOCO API to manage activities within the MOCO system. Specifically, the 'Activity: Get' operation retrieves detailed information about a single activity by its unique Activity ID. This is useful for scenarios where you need to fetch and use specific activity data, such as time tracking entries or work logs, in your workflow for reporting, auditing, or further processing.

Use Case Examples

1. Retrieve details of a specific activity by providing its Activity ID to integrate with time tracking or project management workflows.
2. Fetch an activity's information to update or analyze work logs within an automated business process.

Properties

Output

JSON

• id - The unique identifier of the retrieved activity.
• date - The date when the activity was recorded.
• project_id - The ID of the project associated with the activity.
• task_id - The ID of the task associated with the activity.
• seconds - The duration of the activity in seconds.
• description - A textual description of the activity.
• billable - Indicates if the activity is billable.
• tag - Tags associated with the activity.
• remoteService - External service linked to the activity.
• remoteId - Identifier in the external service.
• remoteUrl - URL to the external service entry.

Dependencies

• Requires an API key credential for authenticating requests to the MOCO API.

Troubleshooting

• Common issues include providing an invalid or non-existent Activity ID, which results in an error from the MOCO API indicating the activity could not be found.
• Network or authentication errors may occur if the API key credential is missing, invalid, or expired. Ensure the credential is correctly configured in n8n.
• If the node fails with an error message about permissions, verify that the API key has sufficient rights to access activity data in MOCO.

Links

• MOCO API Activities Documentation - Official MOCO API documentation for activities, detailing endpoints and data structures.