MOCO icon

MOCO

Consume MOCO API

Overview

This node interacts with the MOCO API to list activities based on various filters and parameters. It is useful for retrieving detailed activity records such as time tracking, project tasks, or company-related activities. For example, it can be used to fetch all activities updated after a certain date, or to get a limited number of activities filtered by project or task ID.

Use Case Examples

  1. Fetch all activities related to a specific project updated after a certain date.
  2. Retrieve a limited number of activities filtered by specific activity IDs.
  3. List activities sorted by a specific field, such as date or user.

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 for listing activities, such as company ID, date range, project ID, task ID, search term, and sorting field.

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 - Remote service linked to the activity.
  • remoteId - Remote identifier for the activity.
  • remoteUrl - Remote URL related to the activity.

Dependencies

  • MOCO API
  • API key credential for authentication

Troubleshooting

  • Ensure the API key credential is correctly configured and has the necessary permissions to access activities.
  • Check that the IDs provided in the filter are valid and exist in the MOCO system.
  • If no results are returned, verify the filter parameters such as date ranges and search terms are correctly set.
  • Handle API rate limits by implementing retries or limiting the number of requests.

Links

Discussion