Acumatica API - Endpoint Default 23 200 001Install

Summary

Upserts a Contact in Acumatica by constructing a request body from provided fixedCollections and additional fields, wrapping primitive values in Acumatica { value: x } format, unwrapping nested collection option keys, and stripping default/empty values to prevent API validation errors.

Inputs

• ContactID — Unique identifier for the contact. If non-zero, the operation updates the existing record; otherwise it inserts a new one. Defaults to 0 when not provided.
• Activities — Related activity records including billable/overtime status, categories, cost codes, created/last modified timestamps, creator ID, note ID, owner, project details, project task, released flag, start date, status, summary, time spent, type, and workgroup ID.
• Address — Contact address details including address line1, line2, city, country, postal code, state, and validated flag.
• Attributes — Attribute records with attribute ID, description, is active flag, required flag, value, value description, and ref note ID.
• Campaigns — Campaign associations including campaign ID, campaign name, contact ID, and stage.
• Cases — Case records with case ID, class ID, closing date, date reported, estimation, initial response, owner, reason, severity, status, and subject.
• Duplicates — Duplicate detection records including business account, business account name, business account type, display name, email, last modified date, and type.
• MarketingLists — Marketing list subscriptions with contact ID, dynamic list flag, format, list name, marketing list ID, and subscribed flag.
• Notifications — Notification records with active/bcc flags, class ID, description, format, mailing ID, module, notification ID, report, and source.
• Opportunities — Opportunity records with currency, display name, estimation date, owner, probability, stage, status, subject, total, and workgroup.
• Relations — Relation records linking accounts, contacts, documents, emails, and role information with primary flag and relation ID.
• RoleAssignments — Role assignment records with assignment ID, BAccount ID, contact ID, location CD, role, and created/last modified timestamps.
• UserInfo — User information including generate password flag, login, password, roles, status, and user type.
• NoteID — Note identifier with a value field.
• AdditionalFields — Free-form additional contact fields including active status, override account address, address validated flag, attention, business account, company name, contact class, contact ID, contact method, converted by, date of birth, display name, do not call/email/fax/mail flags, duplicate info, email, fax/fax type, first/last name, gender, image, job title, language/locale, last incoming/outgoing activity, marital status, middle name, no marketing/mass mail flags, owner, owner employee name, parent account, phone1/2/3 and types, qualification date, reason, source, source campaign, spouse/partner name, status, synchronize flag, title, type, web site, workgroup, workgroup description, full name, and external reference number.

Output shape

The Acumatica API response representing the inserted or updated Contact record, typically returned as the node's execution result. If the request fails (e.g., 400 validation error from un-stripped defaults), the node returns an error.

All parameter values are optional; defaults (empty strings, false, 0) are automatically stripped per the node's buildBody logic to avoid Acumatica 400 errors. Primitive values are wrapped in Acumatica { value: x } format, and fixedCollection option keys are unwrapped so nested fields appear directly under their parent key in the request body.

Examples

Example 1: Insert a new Contact with basic info and one activity.

Set ContactID to 0 (or omit), provide First Name/Last Name/Email in AdditionalFields, and add a single Activity with Billable=true. The node will strip defaults, wrap values, and send the constructed body to the Acumatica Contact endpoint.

Links

• n8n community nodes installation guide