Linqer CRM icon

Linqer CRM

Integração com a API do CRM Linqer

Actions32

Overview

This node integrates with the Linqer CRM API to manage custom fields within the CRM system. Specifically, for the "Campos Personalizados" (Custom Fields) resource and the "Deletar" (Delete) operation, it allows users to delete a specified custom field by its ID.

Common scenarios where this node is beneficial include:

  • Automating cleanup of obsolete or unused custom fields in your CRM.
  • Managing CRM schema dynamically based on business needs.
  • Integrating CRM custom field management into broader automation workflows.

For example, you might use this node to delete a custom field that was used temporarily during a campaign or project, ensuring your CRM stays organized without manual intervention.

Properties

Name Meaning
ID do Campo The unique identifier (ID) of the custom field to be deleted. This is required to specify which custom field should be removed.

Output

The output of the node is the JSON response from the Linqer CRM API after attempting to delete the specified custom field. Typically, this will confirm whether the deletion was successful or provide error details if it failed.

The structure generally includes:

  • Confirmation of deletion (e.g., success status).
  • Any relevant messages or metadata returned by the API.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Linqer CRM API.
  • The node uses HTTP requests to communicate with the Linqer CRM REST endpoints.
  • Ensure the API URL and authentication credentials are correctly configured in n8n.

Troubleshooting

  • Common Issues:

    • Providing an invalid or non-existent custom field ID will result in an error from the API.
    • Missing or incorrect API credentials will cause authentication failures.
    • Network connectivity issues can prevent the node from reaching the Linqer CRM API.

  • Error Messages:

    • "Operation 'delete' not supported for custom fields": This would indicate an internal misconfiguration or unsupported operation; however, the code supports delete, so this is unlikely unless the resource or operation parameters are incorrect.
    • API errors related to authorization or permissions typically mean the API key lacks rights to delete custom fields.
    • "Resource 'customFields' not supported": If the resource parameter is wrong or misspelled.

  • Resolutions:

    • Verify the custom field ID exists in the CRM before attempting deletion.
    • Check and update API credentials in n8n settings.
    • Confirm network access to the Linqer CRM API endpoint.
    • Use the node's "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion