SignifyCRM icon

SignifyCRM

Consume SignifyCRM API
Join our community

Actions30

Overview

This node integrates with the SignifyCRM API to manage various CRM resources, including Tasks. Specifically, the Task - Get Many operation retrieves multiple task records from the SignifyCRM system. It supports fetching either all tasks or a limited number of them based on user input.

Typical use cases include:

  • Synchronizing task data from SignifyCRM into other systems.
  • Automating reporting or dashboards that require bulk task information.
  • Filtering and processing tasks in workflows where multiple task details are needed at once.

For example, you might use this node to fetch all open tasks assigned to your team or retrieve the latest 50 tasks for review.

Properties

Name Meaning
Return All Boolean flag indicating whether to return all matching tasks (true) or limit the results (false).
Limit Maximum number of task records to return when Return All is set to false. Minimum value is 1.

Output

The node outputs an array of JSON objects representing task records. Each task object includes fields such as:

  • id: Unique identifier of the task.
  • name: Task name or title.
  • status: Current status of the task.
  • date_start: Start date of the task.
  • date_due: Due date of the task.
  • priority: Priority level of the task.
  • assigned_user_id: Identifier of the user assigned to the task.
  • parent_type: Type of related parent entity (e.g., Account, Contact).
  • parent_id: Identifier of the related parent entity.

The output does not include binary data.

Dependencies

  • Requires an API key credential for authenticating with the SignifyCRM API.
  • The node makes HTTP POST requests to SignifyCRM endpoints such as /get_entry_list and /get_entries_count.
  • No additional external dependencies beyond the SignifyCRM API and its authentication.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Requesting too many records without proper limits may lead to timeouts or rate limiting by the API.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
    • Rate limit or timeout errors suggest reducing the number of requested records or adding delays between requests.
    • Validation errors may occur if required parameters are missing or malformed; ensure Return All and Limit are correctly set.

Links and References

Discussion