MOCO

Consume MOCO API

Actions20

Overview

This node interacts with the MOCO API to list activities based on various filtering and sorting criteria. It is useful for retrieving detailed activity records such as time tracking entries, project-related tasks, or company activities. For example, users can fetch all activities updated after a certain date, filter by specific project or task IDs, or limit the number of results returned.

Use Case Examples

  1. List all activities updated after a specific date to generate a report of recent work.
  2. Fetch activities related to a particular project to analyze project progress.
  3. Retrieve a limited number of activities matching certain search terms for quick review.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit.
Limit Maximum number of results to return when not returning all.
IDs Filter activities by specific comma-separated IDs.
Updated After Filter activities created or updated after this timestamp.
Additional Fields Additional optional filters and parameters such as company ID, project ID, task ID, date range, user ID, search term, and sorting options.

Output

JSON

  • id - Unique identifier of the activity.
  • date - Date of the activity.
  • project_id - ID of the associated project.
  • task_id - ID of the associated task.
  • seconds - Duration of the activity in seconds.
  • description - 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 - External ID linked to the activity.
  • remoteUrl - External URL linked to the activity.

Dependencies

  • MOCO API

Troubleshooting

  • Ensure the API credentials are correctly configured to avoid authentication errors.
  • If no activities are returned, verify the filter parameters such as date ranges, IDs, and search terms are correct and match existing data.
  • Handle API rate limits by implementing retry logic or reducing request frequency.
  • Common error messages include 'Unauthorized' due to invalid credentials and 'Not Found' if specified IDs do not exist.

Links

Discussion