EspoCRM icon

EspoCRM

Interact with EspoCRM API to manage accounts, contacts, leads, and opportunities. Create, read, update and delete CRM records.
Join our community

Actions21

Overview

The node provides functionality to update an existing Account record in a CRM system. It allows users to modify key details of an account such as its name, type, and additional information like website, industry, phone number, billing address, and description. This node is useful in scenarios where account information needs to be kept current, for example, updating contact details after a client changes their office location or revising the account type when a business relationship evolves.

Practical examples include:

  • Updating the official company name after a rebranding.
  • Changing the account type from "Customer" to "Partner" when a new business alliance is formed.
  • Adding or modifying billing address details for invoicing purposes.

Properties

Name Meaning
Account ID The unique identifier of the account to update (required).
Account Name The official name of the company or organization (required).
Account Type The business relationship type categorizing how this account relates to your organization. Options: Customer, Investor, Partner, Reseller.
Additional Fields Optional extra fields to provide more details about the account:
- Website Company website URL.
- Industry The industry sector the company operates in (e.g., Technology, Manufacturing, Healthcare).
- Phone Number Main phone number for the account.
- Billing Address Street Street address for billing.
- Billing Address City City for billing address.
- Billing Address Country Country for billing address.
- Description Additional notes or description about the account.

Output

The node outputs JSON data representing the updated Account object. This typically includes all the fields that were updated along with any other relevant account details returned by the CRM system after the update operation. There is no indication that binary data is output by this node.

Dependencies

  • Requires connection to the target CRM system's API.
  • Needs appropriate API authentication credentials configured in n8n to authorize update operations.
  • The node depends on internal modules for descriptions and operations, which handle the actual API calls and data formatting.

Troubleshooting

  • Common issues:
    • Providing an invalid or non-existent Account ID will likely result in an error indicating the account could not be found.
    • Missing required fields such as Account ID or Account Name will cause validation errors before the request is sent.
    • Incorrect API credentials or insufficient permissions may lead to authorization errors.
  • Error messages:
    • "Account not found": Verify the Account ID is correct and exists in the CRM.
    • "Missing required parameter": Ensure all mandatory fields are filled.
    • "Unauthorized": Check API credentials and permissions.

Links and References

  • Refer to your CRM system’s API documentation for detailed information on the Account resource and update operation.
  • n8n documentation on creating and using custom nodes for API integrations.

Discussion