Overview

This node interacts with the MOCO API to perform operations on various resources such as activities, companies, contacts, deals, projects, and users. Specifically, for the 'Project' resource with the 'Get' operation, it retrieves detailed information about a specific project by its Project ID. This is useful for workflows that need to fetch project details for reporting, updating, or integration purposes.

Use Case Examples

1. Retrieve detailed information about a project by providing its Project ID to integrate project data into a CRM or project management dashboard.
2. Fetch project details to trigger subsequent automation steps based on project status or attributes.

Properties

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 - The fixed price set for the project.
• retainer - The retainer amount for the project.
• 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 - The billing address for the project.
• billingEmailTo - The primary billing email address.
• billingEmailCc - The CC billing email address.
• billingNotes - Additional billing notes.
• settingIncludeTimeReport - Flag indicating if time reports are included.
• billingVariant - The billing variant used.
• hourlyRate - The hourly rate for the project.
• budget - The overall budget for the project.
• budgetExpenses - The 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
• An API key credential for MOCO API authentication

Troubleshooting

• Ensure the Project ID provided is valid and exists in the MOCO system to avoid 'not found' errors.
• Check that the API credentials are correctly configured and have the necessary permissions to access project data.
• If the API request limit is exceeded, the node may fail; consider implementing retry logic or reducing request frequency.

Links

• MOCO API Projects Documentation - Official MOCO API documentation for project-related endpoints and usage.