MOCO

Consume MOCO API

Actions20

Overview

This node operation creates a new project in the MOCO system using the MOCO API. It is useful for automating project management workflows by programmatically adding projects with detailed attributes such as name, currency, start and finish dates, pricing model, leadership, customer association, budgets, and additional optional fields. For example, it can be used to create a fixed-price or retainer project with specified budgets and billing details, streamlining project setup in MOCO from other systems or automation workflows.

Use Case Examples

  1. Creating a new fixed-price project with a specified start and finish date, leader, customer, and monthly budget.
  2. Creating a retainer project with additional billing and custom properties set for detailed project tracking.

Properties

Name Meaning
Name Name of the project being created, required to identify the project.
Currency Three-letter currency code representing the currency of the project, required for financial tracking.
Start Date Start date of the project in YYYY-MM-DD format, required to define the project timeline.
Finish Date Finish date of the project in YYYY-MM-DD format, required to define the project timeline.
Fixed Price Boolean indicating whether the project is fixed price or not, affecting billing and budgeting.
Retainer Boolean indicating whether the project is a retainer type, affecting billing and budgeting.
Leader Name or ID The user ID of the project leader, selected from a list or specified by expression, required for project leadership assignment.
Customer Name or ID The customer ID associated with the project, selected from a list or specified by expression, required for customer association.
Budget Monthly Monthly budget amount for the project, required if the project is a retainer.
Identifier Optional identifier for the project, used if number ranges are manual.
Additional Fields Optional additional fields for the project such as billing address, emails, notes, billing variant, budgets, co-leader, deal association, hourly rate, info, time report inclusion, tags, and custom properties.

Output

JSON

  • id - Unique identifier of the created project.
  • name - Name of the created project.
  • currency - Currency code of the project.
  • start_date - Start date of the project.
  • finish_date - Finish date of the project.
  • fixed_price - Indicates if the project is fixed price.
  • retainer - Indicates if the project is a retainer.
  • leader_id - User ID of the project leader.
  • customer_id - Customer ID associated with the project.
  • budget_monthly - Monthly budget of the project.
  • identifier - Identifier of the project.
  • additionalFields
    • coLeaderId - Co-leader user ID if set.
    • dealId - Associated deal ID if set.
    • billingAddress - Billing address if provided.
    • billingEmailTo - Billing email address if provided.
    • billingEmailCc - Billing email CC if provided.
    • billingNotes - Billing notes if provided.
    • settingIncludeTimeReport - Flag to include time report.
    • billingVariant - Billing variant type.
    • hourlyRate - Hourly rate if provided.
    • budget - Overall budget if provided.
    • budgetExpenses - Expenses budget if provided.
    • tags - Tags associated with the project.
    • customProperties - Custom properties set for the project.
    • info - Additional info about the project.

Dependencies

  • MOCO API
  • API key credential for MOCO

Troubleshooting

  • Ensure all required fields (name, currency, start date, finish date, fixed price, retainer, leader ID, customer ID, budget monthly) are provided to avoid validation errors.
  • Check that the currency code is a valid 3-letter ISO currency code to prevent API errors.
  • Verify that the leader ID and customer ID exist in the MOCO system to avoid not found errors.
  • If the API request fails, check the API key credential and network connectivity.
  • When using optional fields, ensure data types match expected formats (e.g., dates in YYYY-MM-DD, emails valid) to prevent request rejection.

Links

Discussion