MOCO

Consume MOCO API

Actions20

Overview

This node interacts with the MOCO API to manage projects. Specifically, the 'Get' operation under the 'Project' resource retrieves detailed information about a specific project by its ID. This is useful for workflows that need to fetch project data for reporting, updating, or integration with other systems.

Use Case Examples

  1. Retrieve detailed information about a project by providing its Project ID to use in further automation or reporting.
  2. Fetch project details to synchronize with another project management tool.

Properties

Name Meaning
Project ID The unique identifier of the project to retrieve. This is a required string input.

Output

JSON

  • id - The unique identifier of the project.
  • name - The name of the project.
  • currency - The currency used in the project.
  • start_date - The start date of the project.
  • finish_date - The finish date of the project.
  • fixed_price - Indicates if the project has a fixed price.
  • retainer - Indicates if the project has a retainer.
  • leader_id - The ID of the project leader.
  • customer_id - The ID of the customer associated with the project.
  • budget_monthly - The monthly budget allocated for the project.
  • identifier - An identifier for the project.
  • coLeaderId - The ID of the co-leader of the project.
  • dealId - The ID of the deal associated with the project.
  • billingAddress - Billing address details for the project.
  • billingEmailTo - Billing email recipient address.
  • billingEmailCc - Billing email CC addresses.
  • billingNotes - Additional billing notes.
  • settingIncludeTimeReport - Setting to include time reports.
  • billingVariant - Billing variant used for the project.
  • hourlyRate - Hourly rate for the project.
  • budget - Overall budget for the project.
  • budgetExpenses - Budget allocated for expenses.
  • tags - Tags associated with the project.
  • customProperties - Custom properties defined for the project.
  • info - Additional information about the project.

Dependencies

  • MOCO API with authentication via an API key credential

Troubleshooting

  • Ensure the provided Project ID is valid and exists in the MOCO system to avoid 'not found' errors.
  • Check API credentials and permissions if authentication errors occur.
  • If the API rate limit is exceeded, requests may fail; consider adding delays or retries.
  • Network issues or incorrect endpoint URLs can cause request failures; verify connectivity and configuration.

Links

Discussion