Sperse icon

Sperse

Sperse CRM enables secure payment processing and affiliate marketing for online businesses

Actions6

Overview

This node integrates with Sperse CRM to manage contact data. Specifically, the Contact - Get operation retrieves detailed information about a contact by its unique ID. This is useful in scenarios where you need to fetch existing contact details for further processing, reporting, or synchronization with other systems.

Practical examples:

  • Fetching a contact's full profile before updating their information.
  • Retrieving contact data to display in a dashboard or send personalized communications.
  • Integrating with other tools that require up-to-date contact information from Sperse CRM.

Properties

Name Meaning
Contact ID The unique numeric identifier of the contact to retrieve.

Output

The output is a JSON object containing the full data of the requested contact as returned by the Sperse CRM API. This typically includes personal information, business info, addresses, contact methods, and any custom fields associated with the contact.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to Sperse CRM via an API key credential configured in n8n.
  • The node uses the Sperse CRM REST API endpoint /api/services/CRM/Contact/GetContactData with a GET request, passing the Contact ID as a query parameter.

Troubleshooting

  • Common issues:

    • Invalid or missing Contact ID: The API will fail if the Contact ID is not provided or does not exist.
    • Authentication errors: Ensure the API key credential is correctly set up and has permissions to access contact data.
    • Network or connectivity problems may cause request failures.
  • Error messages:

    • "Contact not found": Verify the Contact ID is correct and exists in Sperse CRM.
    • "Unauthorized" or authentication-related errors: Check API credentials and permissions.
    • Timeout or network errors: Confirm network connectivity and API availability.

Links and References

Discussion