PortaOneInstall

Overview

This node allows you to update custom field values for a specific customer in PortaOne via its API. It is designed for scenarios where you need to programmatically modify or manage additional metadata (custom fields) associated with customer records, such as updating preferences, statuses, or other user-defined information.

Common use cases:

• Automating the update of CRM data when a customer’s status changes.
• Integrating external systems that require syncing custom attributes to customer profiles.
• Bulk updating custom fields for multiple customers based on business logic.

Example:
When a customer completes onboarding, you might want to set a "Onboarding Complete" custom field to true for their record.

Properties

Output

• The node outputs a JSON object reflecting the result of the update operation.
• If Simplify is enabled, only the property specified by SimplifyPath (by default, custom_fields_values) will be returned.
• Otherwise, the full response from the PortaOne API is provided, which typically includes the updated customer record and its custom fields.

Example output (simplified):

{
  "custom_fields_values": {
    "field1": "value1",
    "field2": "value2"
  }
}

Binary Data:
This node does not output binary data; all output is in JSON format.

Dependencies

• Requires access to the PortaOne API.
• You must configure either:
  • PortaOne Token API credentials (for Token Authentication), or
  • PortaOne Basic API credentials (for Basic Authentication)
• n8n credentials must be set up accordingly.

Troubleshooting

Common issues:

• Invalid Credentials:
  Error if the provided API credentials are incorrect or missing.
  Resolution: Check your authentication method and ensure the correct credentials are configured in n8n.

• Customer Not Found:
  If the specified Customer ID does not exist, the API may return an error.
  Resolution: Verify the Customer ID is correct and exists in PortaOne.

• Missing Required Fields:
  If required properties (like Customer ID or Custom Fields Values) are not provided, the node may throw validation errors.
  Resolution: Ensure all required fields are filled in the node configuration.

• API Errors:
  Any errors returned by the PortaOne API (e.g., permission denied, invalid field names) will be surfaced as node errors.
  Resolution: Review the error message and consult PortaOne API documentation for details.

Links and References

• PortaOne Official Documentation
• n8n Credentials Documentation
• Custom Fields in PortaOne