mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node operation, Leadfyndr Remove Unlocked Lead Reservation, is designed to remove or cancel an unlocked lead reservation in the Lead Fyndr system. It is useful in scenarios where a previously reserved lead is no longer needed or should be released back into the pool for reassignment or other processing.

Practical examples include:

  • A sales team member unlocking a lead but then deciding not to pursue it, so they release the reservation.
  • Automated workflows that clean up stale or unused lead reservations to keep the lead database current and accurate.

Properties

Name Meaning
Lead Id The unique identifier of the lead whose unlocked reservation you want to remove.
Customer Id The unique identifier of the customer associated with the lead reservation.

Both properties are required string inputs that specify exactly which lead reservation to remove.

Output

The output JSON will typically contain the result of the removal operation, such as a success confirmation or status message indicating whether the unlocked lead reservation was successfully removed. The exact structure depends on the API response but generally includes fields confirming the action's outcome.

There is no indication that this node outputs binary data.

Dependencies

  • Requires an active connection to the Lead Fyndr API service.
  • Needs appropriate API authentication credentials configured in n8n (e.g., an API key or token).
  • Network access to Lead Fyndr endpoints must be available from the n8n environment.

Troubleshooting

  • Common issues:

    • Invalid or missing Lead Id or Customer Id will cause the operation to fail.
    • Authentication errors if API credentials are incorrect or expired.
    • Network connectivity problems preventing access to the Lead Fyndr API.
  • Error messages and resolutions:

    • "Unauthorized" or "Authentication failed": Verify and update the API credentials.
    • "Lead not found" or "Reservation does not exist": Check that the Lead Id and Customer Id are correct and correspond to an existing unlocked reservation.
    • Timeouts or network errors: Ensure stable internet connection and that the Lead Fyndr API endpoint is reachable.

Links and References

  • Refer to the official Lead Fyndr API documentation for detailed information on lead reservation management and error codes.
  • Consult n8n documentation on setting up API credentials and handling HTTP request nodes for additional context.

Discussion