BackOffice ERP icon

BackOffice ERP

BackOffice ERP API with Google-style smart search. IMPORTANT FOR AI: Use customer/project names instead of IDs (e.g., "VIGACA" not customer ID 123). Supports AI auto-fill from conversation context. Handles case-insensitive search across all business entities.

Projects → Update

AI-generated

Summary

Update an existing project by its ID using detailed project information including name, related type, customer, billing type, dates, status, and optionally cost, progress, members, tags, description, and other attributes.

Inputs

  • Project Id (required) — The exact project ID number or a search keyword (e.g., project name) to identify the project to update; supports smart search resolving to an ID.
  • Name (required) — The updated name of the project.
  • Rel type (required) — The type of relation the project has (Project Related).
  • Customer (required) — The related customer ID or a searchable keyword (name, email, etc.) to identify the customer associated with the project.
  • Billing type (required) — Numeric value representing the billing type for the project.
  • Start date (required) — The project's start date and time.
  • Status (required) — Numeric value representing the project status.
  • Progress from tasks — Optional flag ('on' or 'off') indicating if progress is calculated from tasks.
  • Project cost — Optional field to specify the project's cost.
  • Progress — Optional field to indicate the project's progress.
  • Project rate per hour — Optional hourly rate for the project.
  • Estimated hours — Optional estimated total hours for the project.
  • Project members — Optional list or description of project members.
  • Deadline — Optional project deadline date and time.
  • Tags — Optional tags associated with the project.
  • Description — Optional textual description of the project.

Output shape

a single JSON object containing the updated project data returned by the BackOffice ERP API.

If the project ID or any related ID fields are given as names or keywords instead of exact numeric IDs, the node uses smart search to resolve them to the correct IDs. If multiple matches occur, the operation outputs a multiple match warning and requires disambiguation. The operation throws errors for missing required fields or invalid inputs unless 'Continue On Fail' is enabled in the node settings.

Discussion