AvantGuard - Sage Intacct (Company Configuration) icon

AvantGuard - Sage Intacct (Company Configuration)

AvantGuard - Sage Intacct (Company Configuration)

Actions43

Overview

This node operation "Create Company Config Contact" under the "Contacts" resource is designed to create a new contact record within a company's configuration in Sage Intacct via the AvantGuard API. It allows users to specify detailed contact information such as names, emails, phone numbers, addresses, tax settings, and other metadata relevant to billing, invoicing, and order entry.

Typical use cases include automating the creation of contacts for companies during onboarding processes, syncing contact data from CRM systems into Sage Intacct, or programmatically managing company contacts without manual entry.

For example, a finance team could use this node to automatically add new vendor contacts with all necessary details when a new vendor is approved, ensuring that invoices and payments are correctly addressed.

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, expense reimbursements, 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 associated with the contact. Contains keys like key, id, name, and href. Contacts created at the top level have null values here.
- Mailing Address JSON object containing mailing address details including address lines, city, state, postal code, country, and ISO country code.
- Price List JSON object specifying the default price list used in order entry when this contact places orders.
- Price Schedule JSON object specifying the price schedule used in order entry when this contact places orders.
- Tax JSON object defining tax settings for the contact, including whether taxable, tax ID, and tax group information.

Output

The node outputs JSON data representing the newly created contact object as returned by the API. This typically includes all the properties sent plus any system-generated fields such as unique keys or URLs.

If the node supports binary data output (not indicated here), it would represent attachments or documents related to the contact, but this operation focuses on JSON data only.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard Sage Intacct API.
  • The base URL for the API must be configured in the node credentials.
  • The node uses HTTP headers to accept and send JSON content.
  • No other external dependencies are indicated.

Troubleshooting

  • Missing Required Fields: If the required fields Id or Print As are not provided, the API will likely reject the request. Ensure these are always set.
  • Invalid JSON in Complex Fields: Fields like entity, mailingAddress, priceList, priceSchedule, and tax expect valid JSON strings. Malformed JSON will cause errors.
  • API Authentication Errors: If the API key or base URL is incorrect or missing, authentication will fail. Verify credentials configuration.
  • Status Field Values: Only active or inactive are accepted for the status field; other values may cause validation errors.
  • Network Issues: Connectivity problems to the API endpoint will result in request failures.
  • Permission Issues: The API user must have permissions to create contacts in the company configuration.

Links and References

Discussion