MOCO

Consume MOCO API

Actions20

Overview

This node interacts with the MOCO API to list projects based on various filtering and sorting criteria. It is useful for retrieving project data from MOCO, such as in project management or reporting workflows. For example, users can fetch all projects, limit the number of projects returned, filter projects by IDs, or specify date ranges for creation or updates. Additional filters include company, leader, tags, and project group, among others.

Use Case Examples

  1. List all projects without limit.
  2. List up to 50 projects filtered by specific IDs.
  3. List projects updated after a certain date.
  4. List projects including archived ones and with detailed company information.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit.
Limit Maximum number of project results to return when not returning all.
IDs Comma-separated list of project IDs to filter and fetch multiple specific projects.
Updated After Timestamp to filter projects created or updated after this date.
Additional Fields Additional optional filters and parameters for listing projects, such as company ID, date ranges, tags, sorting, and flags like including archived projects.

Output

JSON

  • id - Unique identifier of the project.
  • name - Name of the project.
  • currency - Currency used in the project.
  • start_date - Project start date.
  • finish_date - Project finish date.
  • fixed_price - Fixed price of the project if applicable.
  • retainer - Boolean indicating if the project is a retainer.
  • leader_id - ID of the project leader.
  • customer_id - ID of the customer associated with the project.
  • budget_monthly - Monthly budget for the project.
  • identifier - Project identifier.
  • additionalFields - Other optional fields such as co-leader, deal ID, billing details, tags, custom properties, and info.

Dependencies

  • MOCO API
  • API authentication token or API key credential

Troubleshooting

  • Ensure the API credentials are correctly configured and have the necessary permissions to access project data.
  • If filtering by IDs, ensure the IDs are valid and exist in MOCO.
  • Date filters must be in the correct format; otherwise, the API may return errors or no results.
  • If the node returns an error about limits, check the 'Return All' and 'Limit' settings to avoid exceeding API limits.

Links

Discussion