Linqer CRM icon

Linqer CRM

Integração com a API do CRM Linqer

Actions32

Overview

This node integrates with the Linqer CRM API to update existing tasks ("Tarefas"). It allows users to modify various attributes of a task such as its title, description, due date, status, responsible user, related opportunity, duration, and type. This operation is useful in scenarios where task details need to be kept current within a CRM workflow, for example:

  • Updating the status of a task from "Pending" to "In Progress" or "Completed".
  • Changing the due date or description based on new information.
  • Assigning or reassigning the task to a different responsible user.
  • Linking the task to a different sales opportunity.

Practical examples include automating task updates after a meeting, adjusting deadlines dynamically, or syncing task changes from other systems into Linqer CRM.

Properties

Name Meaning
Título The title of the task (string, required).
Descrição A detailed description of the task (string, multiline).
Data de Vencimento The due date and time by which the task should be completed (dateTime, required).
Task ID A custom identifier for the task (string).
Status The current status of the task. Options: "Pendente" (Pending), "Em Andamento" (In Progress), "Concluída" (Completed), "Atrasada" (Overdue).
Responsável ID The ID of the user responsible for the task (string).
Opportunity ID The ID of the related sales opportunity (string).
Duração Estimated duration of the task, e.g., "30min", "1h" (string).
Tipo The type of task. Options: 1 = Tarefa (Task), 2 = Reunião (Meeting), 3 = Ligação (Call).
ID da Tarefa The unique identifier of the task to be updated (string, required).

Output

The node outputs JSON data representing the updated task object returned by the Linqer CRM API. This typically includes all the task fields after the update, confirming the changes made. The output can be used downstream in workflows to trigger further actions or logging.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Linqer CRM API.
  • The node uses HTTP requests to the Linqer CRM REST endpoints.
  • Proper configuration of the API URL and authentication credentials in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing task ID (ID da Tarefa) will cause the update to fail.
    • Incorrect API credentials or expired tokens will result in authentication errors.
    • Providing invalid values for enumerated fields like Status or Tipo may cause request rejection.
    • Network connectivity problems can prevent communication with the Linqer CRM API.

  • Error messages:

    • "Operação 'update' não suportada para tarefas": Indicates an unsupported operation was requested; ensure the operation parameter is set correctly.
    • Authentication errors usually mention unauthorized access; verify API keys and permissions.
    • Validation errors from the API will specify which field is incorrect or missing; review input properties accordingly.

  • Resolution tips:

    • Double-check that the ID da Tarefa corresponds to an existing task in Linqer CRM.
    • Confirm all required fields are provided and valid.
    • Ensure the API credentials configured in n8n are correct and have sufficient permissions.
    • Test connectivity to the Linqer CRM API endpoint outside n8n if needed.

Links and References

Discussion