Perfex

Consume Perfex API
Join our community

Actions14

Overview

This node integrates with the Perfex API to manage leads, customers, and contacts. Specifically for the Lead - Update operation, it updates an existing lead's information in the Perfex system by sending a PUT request with the specified fields.

Typical use cases include:

  • Updating contact details or company information of a lead after receiving new data.
  • Modifying lead attributes such as phone number, position, or website to keep records current.
  • Automating lead management workflows where lead data changes frequently.

For example, if you have a workflow that captures updated lead info from a form submission, this node can update the corresponding lead record in Perfex automatically.

Properties

Name Meaning
Lead ID The unique identifier of the lead to update (required).
Additional Fields Optional fields to update on the lead. These include:
- Phone: The phone number of the lead.
- Position: The job position of the lead.
- Website: The website URL associated with the lead.

Note: The "Additional Fields" property is a collection allowing you to specify any combination of these optional fields to update.

Output

The node outputs the JSON response returned by the Perfex API after updating the lead. This typically includes the updated lead object with its current properties reflecting the changes made.

If multiple items are processed, each output item corresponds to one lead update result.

No binary data is produced by this node.

Dependencies

  • Requires an active connection to the Perfex API via an API key credential configured in n8n.
  • The base URL for the Perfex instance must be set in the credentials.
  • The node uses HTTP methods (PUT) to interact with the /api/leads/{leadId} endpoint.

Troubleshooting

  • Common issues:

    • Invalid or missing Lead ID will cause the API to return an error.
    • Incorrect or expired API credentials will result in authentication failures.
    • Providing invalid field values may cause the API to reject the update.

  • Error messages:

    • Errors from the API are captured and returned in the node output if "Continue On Fail" is enabled.
    • Typical errors include "Not Found" if the lead does not exist, or "Unauthorized" if credentials are invalid.

  • Resolutions:

    • Verify the Lead ID exists in your Perfex system.
    • Ensure API credentials are correctly configured and have sufficient permissions.
    • Validate all input fields conform to expected formats.

Links and References

Discussion