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.

Tasks → Create

AI-generated

Summary

Create a new task in BackOffice ERP with specified details such as name, start date, related entity type, and optional attributes like public visibility, billable status, hourly rate, milestone, due date, priority, repeat settings, cycles, related ID (supports smart search), tags, and description.

Inputs

  • Name (required) — Specifies the name of the task.
  • Startdate (required) — Specifies the start date and time of the task.
  • Rel type (required) — Defines the type of entity the task is related to (e.g., customer, project).
  • Is public — Indicates if the task is public.
  • Billable — Specifies if the task is billable.
  • Hourly rate — Specifies the hourly rate for the task.
  • Milestone — Associates the task with a milestone.
  • Duedate — Sets the task's deadline date and time.
  • Priority — Sets the priority level of the task.
  • Repeat every — Defines the repeat interval for the task.
  • Repeat every custom — Custom numeric value for repeating the task at a specified interval.
  • Repeat type custom — Custom type describing the repeat interval unit.
  • Cycles — Number of repeat cycles for the task.
  • Rel id — ID related to the task's related entity. Supports smart search by entering name, email, or keywords instead of numeric ID.
  • Tags — Tags associated with the task.
  • Description — Textual description of the task.

Output shape

a single JSON object representing the created task, including all provided fields and the assigned task ID

If the related ID is provided as a name or keyword, the node performs a smart search to resolve it to a numeric ID; if multiple matches are found, an error indication with match options is returned. Errors during creation will throw exceptions unless 'Continue on Fail' is enabled, in which case errors are included in the output JSON.

Examples

Example 1: Create a basic task with mandatory fields

Name, Startdate, Rel type, and Rel id are set; other fields omitted or defaulted.

Discussion