Actions43
- Earning Types Actions
- Email Templates Actions
- Employee Types Actions
- Employees Actions
- Entities Actions
- Classes Actions
- Contacts Actions
- Department Groups Actions
- Exchange Rate Lines Actions
- Exchange Rate Types Actions
- Exchange Rates Actions
- Attachment Folders Actions
- Get Next Value Actions
- Location Groups Actions
- Locations Actions
- Roles Actions
- User Groups Actions
- Users Actions
- Affiliate Entity Groups Actions
- Attachments Actions
- Departments Actions
- Document Sequences Actions
Overview
This node operation creates a new contact within a company configuration in the Sage Intacct system. It is designed to add detailed contact information that can be used for billing, invoicing, statements, and other financial documents. This is particularly useful for organizations managing multiple contacts associated with their company entities, allowing them to maintain accurate and comprehensive contact records.
Practical examples include:
- Adding a new accounts receivable contact who will receive invoices and payment reminders.
- Creating a contact record for a vendor or partner company representative.
- Setting up internal contacts for expense reporting and reimbursement processes.
Properties
| Name | Meaning |
|---|---|
| Id | Unique identifier for the contact. |
| Print As | The contact's name as it will appear on bills, invoices, AR statements, advances, adjustments, checks, expense reports, and 1099s. |
| Additional Body Fields | Optional additional fields to provide more detailed contact information: |
| - Key | System-assigned unique key for the contact. |
| - Href | URL endpoint for the contact. |
| - Last Name | Contact's last name. |
| - First Name | Contact's first name. |
| - Middle Name | Contact's middle name or initial. |
| - Prefix | Prefix such as Mr., Mrs., or Ms. |
| - Email 1 | Primary email address. |
| - Email 2 | Secondary email address. |
| - Phone 1 | Primary phone number. |
| - Phone 2 | Secondary phone number. |
| - Mobile | Mobile phone number. |
| - Pager | Pager number. |
| - Fax | Fax number. |
| - URL 1 | Web page address for this contact. |
| - URL 2 | Secondary web page address. |
| - Company Name | Name of the company associated with this contact. |
| - Show In Contact List | Boolean flag to display the contact in the contact list (true or false). |
| - Discount | Default discount percentage applied to order entry transactions involving this contact. |
| - Status | Object status indicating if the contact is Active or Inactive. Options: Active, Inactive. |
| - Entity | JSON object representing the entity the contact is associated with (key, id, name, href). |
| - Mailing Address | JSON object containing mailing address details (address lines, city, state, postal code, country, ISO country code). |
| - Price List | JSON object defining the default price list used when this contact places orders. |
| - Price Schedule | JSON object defining the price schedule used when this contact places orders. |
| - Tax | JSON object specifying tax settings including taxable status, tax ID, and tax group information. |
Output
The node outputs a JSON object representing the newly created contact resource as returned by the Sage Intacct API. This typically includes all the properties sent in the request along with any additional metadata or identifiers assigned by the system.
If binary data were involved (e.g., attachments), it would be summarized here, but this operation deals solely with JSON data.
Dependencies
- Requires an API key credential for authenticating with the Sage Intacct API.
- The base URL for the API must be configured in the node credentials.
- The node uses JSON payloads to communicate with the Sage Intacct REST API endpoints.
Troubleshooting
- Missing Required Fields: If "Id" or "Print As" are not provided, the API will likely reject the request. Ensure these required fields are set.
- Invalid JSON in Complex Fields: Fields like "Entity", "Mailing Address", "Price List", "Price Schedule", and "Tax" expect valid JSON strings. Malformed JSON will cause errors.
- API Authentication Errors: Incorrect or missing API credentials will result in authentication failures.
- Status Field Values: Only "active" or "inactive" are accepted; other values may cause validation errors.
- Network Issues: Connectivity problems to the Sage Intacct API endpoint will prevent successful creation.
To resolve errors, verify all required fields, ensure JSON syntax correctness, confirm API credentials, and check network connectivity.
Links and References
- Sage Intacct Contacts API Documentation (for detailed field descriptions and usage)
- Order Entry Price Lists Help Center (explains price list assignment to contacts)