Perfex CRM

Interagir com o Perfex CRM via WON API
Join our community

Actions30

Overview

This node integrates with the Perfex CRM system via the WON API, allowing users to manage various CRM resources such as clients, contacts, leads, projects, tasks, and invoices. Specifically for the Tarefa (Task) resource with the Listar (getAll) operation, it fetches a list of tasks from the Perfex CRM.

Typical use cases include:

  • Retrieving all tasks assigned or related to projects for reporting or automation.
  • Filtering tasks by specific criteria like status, priority, or due date.
  • Paginating through large sets of tasks to process them in batches.

For example, a user might want to list all urgent tasks due this week or retrieve tasks assigned to a particular team member.

Properties

Name Meaning
Opções Adicionais Collection of additional options to customize the task listing:
- Limite Maximum number of task records to return (number between 1 and 1000).
- Página Page number of results to return (starting at 1).
- Filtros JSON string representing filters to apply to the search query (e.g., {"status":2}).

These properties allow controlling pagination and filtering when listing tasks.

Output

The output is an array of JSON objects where each object represents a task record retrieved from the Perfex CRM. The structure corresponds directly to the data returned by the WON API endpoint /won_api/won/api/tasks.

Each task JSON typically includes fields such as:

  • id (task identifier)
  • name (task name)
  • description
  • priority (numeric priority level)
  • status (status ID)
  • startdate (start date in ISO format)
  • duedate (due date in ISO format)
  • assignees (array or comma-separated IDs of responsible users)
  • project_id (ID of the associated project)
  • milestone (milestone ID)

No binary data output is produced by this operation.

Dependencies

  • Requires an API token credential for authenticating with the Perfex CRM WON API.
  • The node uses Axios HTTP client internally to make requests to the configured base URL of the Perfex CRM instance.
  • The user must configure the node credentials with the correct API URL and token.

Troubleshooting

  • Invalid JSON in Filters: If the "Filtros" property contains invalid JSON, the node will throw an error parsing it. Ensure the filter string is valid JSON.
  • Authentication Errors: If the API token is missing or invalid, the node returns an authentication error. Verify the API token in credentials.
  • Pagination Limits: Setting a very high limit may cause performance issues or API errors; keep within recommended limits (max 1000).
  • Date Format Validation: Although not directly relevant to listing, other operations validate date formats strictly (YYYY-MM-DD). Incorrect formats cause errors.
  • Connection Issues: Network problems or incorrect base URL configuration can cause connection errors.
  • Unknown Resource or Operation: Selecting unsupported resources or operations will result in an error indicating unknown resource or operation.

Links and References

This summary focuses on the "Tarefa" resource with the "Listar" operation, describing how to list tasks from Perfex CRM using this node.

Discussion