SignifyCRM icon

SignifyCRM

Consume SignifyCRM API
Join our community

Actions30

Overview

This node integrates with the SignifyCRM API to update an existing Account record. It allows users to modify various fields of an account such as its name, type, industry, status, and assigned user. This operation is useful in scenarios where account information needs to be kept current, for example:

  • Updating a customer's industry classification after a business pivot.
  • Changing the assigned sales representative responsible for the account.
  • Modifying the account status based on recent interactions or contract changes.

Practical example: A sales automation workflow that updates account details when new information is received from a lead qualification process or customer support interaction.

Properties

Name Meaning
Account ID The unique identifier of the account to update. Found at the end of the account's URL.
Name The updated name of the account.
Type The category of the account. Options: Customer, Others, Partner, Prospect, Supplier.
Industry The industry sector the account belongs to. Options include Agro, Automobile, Construction Materials, Consumption, e-Commerce, Education, Electronics, Energy, Engineering, Fashion, Finance, Food, Government, Health, Home, Hotel, ICT, Insurance, Machine, Non-Profit, Other, Packaging, Petrochemical, Pharmaceutical, Printing, Property, Restaurant, Retail, Tourism, Transportation.
Status Current status of the account. Options: Active, Approved, Collection, Inactive, Pending, Rejected, Suspend.
Assigned To Name or ID The user assigned to this account. Can be selected from a list or specified via expression.
Update Fields Additional optional fields to update: Email (Primary), Office Phone, Description.

Output

The node outputs JSON data representing the response from the SignifyCRM API after attempting to update the account. This typically includes confirmation of the updated record and any relevant metadata returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the SignifyCRM API.
  • Relies on internal helper functions to fetch the current user ID and make authenticated HTTP POST requests to the SignifyCRM endpoints.
  • The node uses the /set_entry endpoint of the SignifyCRM API to perform the update.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Account ID will result in failure to update.
    • Missing required authentication credentials will cause authorization errors.
    • Attempting to update with empty or invalid field values may cause the API to reject the request.

  • Error messages:

    • Errors from the API are propagated and can include messages about invalid IDs, missing permissions, or malformed requests.
    • If the node is set to continue on fail, errors will be included in the output JSON under an error property.

  • Resolution tips:

    • Verify the Account ID is correct and exists in the CRM.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Double-check all input fields for correctness and completeness before running the node.

Links and References

Discussion