Actions20
Overview
The MOCO Project Create node allows you to create a new project in the MOCO system via its API. This is useful for automating project onboarding, integrating project creation with other business processes (such as CRM or sales pipelines), and ensuring consistent data entry across systems. For example, you could automatically create a MOCO project when a deal is closed in your CRM, or batch-create projects from a spreadsheet.
Properties
Below are the input properties supported by this operation:
Display Name | Type | Description |
---|---|---|
Name | String | Name of the project being created. |
Currency | String | Currency of the project (3-letter currency code, e.g., USD, EUR). |
Start Date | String | Start date of the project (format: YYYY-MM-DD). |
Finish Date | String | Finish date of the project (format: YYYY-MM-DD). |
Fixed Price | Boolean | Whether the project is fixed price or not. |
Retainer | Boolean | Whether the project is a retainer or not. |
Leader Name or ID | Options | Select a leader from the list or specify an ID using an expression. |
Customer Name or ID | Options | Select a customer from the list or specify an ID using an expression. |
Budget Monthly | Number | Monthly budget for the project. |
Identifier | String | Identifier for the project (mandatory if number ranges are manual). |
Additional Fields | Collection | Optional additional fields (see below). |
Additional Fields (Collection)
- Billing Address: String — Billing address for the project.
- Billing Email CC: String — Email address for billing CC.
- Billing Email To: String — Email address for billing.
- Billing Notes: String — Notes related to billing.
- Billing Variant: Options — Billing variant (
project
,task
,user
). - Budget: Number — Overall budget for the project.
- Budget Expenses: Number — Expenses budget for the project.
- Co Leader Name or ID: Options — Co-leader selection or ID.
- Custom Properties: Fixed Collection — Custom key-value pairs for the project.
- Deal Name or ID: Options — Associated deal selection or ID.
- Hourly Rate: Number — Hourly rate for the project.
- Info: String — Additional information about the project.
- Setting Include Time Report: Boolean — Whether to include time report.
- Tags: Fixed Collection — Tags for the project.
Output
The output will be a JSON object representing the newly created project as returned by the MOCO API. The structure typically includes (but is not limited to):
{
"id": 12345,
"name": "Project Name",
"currency": "USD",
"start_date": "2024-07-01",
"finish_date": "2024-12-31",
"fixed_price": true,
"retainer": false,
"leader_id": 678,
"customer_id": 910,
"budget_monthly": 10000,
"identifier": "PRJ-001",
// ...other fields as provided or returned by MOCO
}
All fields sent in the request, along with additional metadata from MOCO, may be present in the response.
Dependencies
- MOCO API: Requires access to the MOCO API.
- API Credentials: You must configure valid MOCO API credentials in n8n under the name
mocoApi
. - n8n Environment: No special environment variables required beyond standard credential setup.
Troubleshooting
- Missing Required Fields: If any required property (e.g., Name, Currency, Leader, Customer) is missing, the node will throw an error indicating which field is absent.
- Invalid Dates: Ensure that dates are in the correct format (
YYYY-MM-DD
). Invalid formats may result in API errors. - Permission Issues: If the API credentials lack permission to create projects, you will receive an authentication/authorization error from MOCO.
- Identifier Requirement: If your MOCO instance requires manual identifiers and none is provided, the API will reject the request.
- Continue On Fail: If enabled, errors for individual items will be output in the
error
field of the JSON.