Actions12
Overview
The node integrates with the Memberspot API to manage user-related data and actions. Specifically, for the User resource and the Set Custom Properties operation, it allows setting or updating custom properties for a user identified by their email address. This is useful in scenarios where you want to enrich user profiles with additional metadata or attributes that are not part of the default user schema.
Practical examples:
- Adding custom tags or labels to users for segmentation.
- Storing user preferences or settings as custom properties.
- Tracking additional user-specific information like membership levels or subscription details.
Properties
| Name | Meaning |
|---|---|
| The email address of the user whose custom properties will be set. | |
| Custom Properties | A collection of key-value pairs representing the custom properties to assign to the user. Each property has: - ID: Identifier/name of the custom property. - Value: The value to assign to that property. |
Output
The output is a JSON object representing the response from the Memberspot API after setting the custom properties for the specified user. It typically contains confirmation of the update or the updated user data.
If an error occurs during the API request, the output JSON will contain an error field with the error message.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Memberspot API.
- The base URL and API key must be configured in the node credentials.
- The node makes HTTP requests to the Memberspot API endpoints.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect email format or non-existent user email may result in errors or no updates.
- Providing invalid property IDs or values might cause the API to reject the request.
Error messages:
- Errors returned from the API are passed through in the output's
errorfield. - Network or connectivity issues will throw errors indicating failure to reach the API.
- Errors returned from the API are passed through in the output's
Resolution tips:
- Verify the API key and base URL in the credentials.
- Ensure the email corresponds to an existing user in Memberspot.
- Confirm that custom property IDs exist and are valid within the Memberspot system.
- Use the "Continue on Fail" option if you want the workflow to proceed despite individual item errors.
Links and References
- Memberspot API Documentation (general reference, replace with actual URL if available)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling)
- n8n Expressions (for dynamic parameter usage)