Actions478
- Account Actions
- Account Details For Period Inquiry Actions
- Account Group Actions
- Account Summary Inquiry Actions
- Activity Actions
- Amazon Store Actions
- Appointment Actions
- Attribute Definition Actions
- Big Commerce Stores Actions
- Bill Actions
- Budget Actions
- Business Account Actions
- Carrier Actions
- Case Actions
- Cash Sale Actions
- Cash Transaction Actions
- Change Order Actions
- Change Order Class Actions
- Check Actions
- Companies Structure Actions
- Company Financial Period Actions
- Contact Actions
- Contract Usage Actions
- Cost Code Actions
- Currency Actions
- Customer Actions
- Customer Class Actions
- Customer Location Actions
- Customer Payment Method Actions
- Customer Price Class Actions
- Deduction Benefit Code Actions
- Discount Actions
- Discount Code Actions
- Earning Type Code Actions
- Email Actions
- Email Processing Actions
- Employee Actions
- Employee Payroll Class Actions
- Employee Payroll Settings Actions
- Event Actions
- Expense Claim Actions
- Expense Receipt Actions
- External Commitment Actions
- Financial Period Actions
- Financial Year Actions
- F O B Point Actions
- Inventory Adjustment Actions
- Inventory Allocation Inquiry Actions
- Inventory Issue Actions
- Inventory Quantity Available Actions
- Inventory Receipt Actions
- Inventory Summary Inquiry Actions
- Invoice Actions
- Item Class Actions
- Item Sales Category Actions
- Item Warehouse Actions
- Journal Transaction Actions
- Kit Assembly Actions
- Kit Specification Actions
- Labor Cost Rate Actions
- Lead Actions
- Ledger Actions
- Lot Serial Class Actions
- Non Stock Item Actions
- Opportunity Actions
- Pay Group Actions
- Payment Actions
- Payment Method Actions
- Pay Period Actions
- Payroll Batch Actions
- Payroll Union Local Actions
- Payroll W C C Code Actions
- Physical Inventory Count Actions
- Physical Inventory Review Actions
- Pro Forma Invoice Actions
- Project Actions
- Project Budget Actions
- Project Task Actions
- Project Template Actions
- Project Template Task Actions
- Project Transaction Actions
- P T O Bank Actions
- Purchase Order Actions
- Purchase Receipt Actions
- Sales Invoice Actions
- Sales Order Actions
- Salesperson Actions
- Sales Prices Inquiry Actions
- Sales Price Worksheet Actions
- Service Order Actions
- Shipment Actions
- Shipping Box Actions
- Shipping Term Actions
- Shipping Zones Actions
- Ship Via Actions
- Shopify Store Actions
- Stock Item Actions
- Storage Details By Location Inquiry Actions
- Storage Details Inquiry Actions
- Subaccount Actions
- Subcontract Actions
- Task Actions
- Tax Actions
- Tax Category Actions
- Tax Reporting Settings Actions
- Tax Zone Actions
- Template Items Actions
- Time Entry Actions
- Transfer Order Actions
- Union Local Actions
- Units Of Measure Actions
- Vendor Actions
- Vendor Class Actions
- Vendor Prices Inquiry Actions
- Vendor Price Worksheet Actions
- Warehouse Actions
- Work Calendar Actions
- Work Class Compensation Code Actions
- Work Location Actions
Email → Insert/Update
AI-generatedSummary
Upserts (inserts or updates) an Email entity in Acumatica via the Default endpoint (23 200 001).
Inputs
- Parent — Parent record reference for the email (e.g., a contact or account). A simple value field wrapped in a fixedCollection container. Accepts any string identifier; the node will wrap the value in Acumatica's {value: …} format before sending. If omitted, the field is excluded from the request body after stripping empties.
- TimeActivity — Time‑activity details linked to the email. Provided as a fixed collection with the following sub‑fields (all optional): Approver (string), Billable (boolean), BillableOvertime (string), BillableTime (string), CostCode (string), EarningType (string), Overtime (string), Project (string), ProjectTask (string), ReferenceNbr (string), Released (boolean), Status (string), TimeSpent (string), TrackTime (boolean). The node builds a nested object where each sub‑field is wrapped as {value: …} and any sub‑field with an empty/default value is removed before the request is sent.
- NoteID — Identifier of a note attached to the email. A single string value inside a fixedCollection; treated like Parent – wrapped as {value: …} and omitted if empty.
- RelatedEntityNoteID — Identifier of a note on the related entity (e.g., a sales order or project) that the email is associated with. Same handling as NoteID.
- Additional Fields — A collection of email‑specific and system fields. Each field is optional; the node reads the supplied values, recursively strips empty/default values, wraps primitives in Acumatica's {value: …} format, and includes the resulting object in the request body. The fields are: Bcc (string), Body (string), Cc (string), Description (string), From (string), FromEmailAccountDisplayName (string), FromEmailAccountID (number), Incoming (boolean), Internal (boolean), MailStatus (string), Owner (string), ParentSummary (string), StartDate (dateTime), Subject (string), To (string), Workgroup (string), CreatedByID (string), CreatedDateTime (dateTime), LastModifiedDateTime (dateTime), RelatedEntityType (string), RelatedEntityDescription (string).
Output shape
The raw response returned by the Acumatica API for the upserted Email record. Typically a JSON object containing the same set of fields that were sent (plus any system‑generated values such as IDs, timestamps, etc.), wrapped in Acumatica's value format where applicable.
The node does not transform the response beyond passing it through; workflow developers can access any returned property directly from the node's output.
Examples
Example 1: Create a new outgoing email
Set Subject, Body, To, From, and optionally CC/BCC. Leave Parent, TimeActivity, NoteID, RelatedEntityNoteID blank unless you need to attach the email to a specific record.
Example 2: Update an existing email
Provide the email’s unique identifier (often held in a field like NoteID or a custom key) plus any fields you wish to change. Omitted fields retain their existing values because the node strips empties before sending.
