Solidarity Tech

Interact with Solidarity Tech API

Actions22

User → Update

AI-generated

Overview

The node integrates with the Solidarity Tech API to update user information. It allows updating various user attributes such as contact details, language preferences, permissions, tags, address, and custom properties. This operation is useful in scenarios where user data needs to be kept current, for example:

  • Synchronizing user profile updates from a CRM or form submission.
  • Modifying user communication preferences (SMS, call, email permissions).
  • Managing user segmentation by adding or removing tags.
  • Updating location or custom metadata related to users.

Practical example: After a user submits an updated profile form on a website, this node can update their record in Solidarity Tech with new phone number, email, and address details.

Properties

Name Meaning
User ID The unique identifier of the user to update (required).
Phone Number User's phone number.
Email User's email address.
First Name User's first name.
Last Name User's last name.
Preferred Language User's preferred language.
Second Language User's secondary language.
Chapter ID Numeric ID representing the user's chapter affiliation.
SMS Permission Boolean indicating if the user has given permission to receive SMS messages.
Call Permission Boolean indicating if the user has given permission to receive calls.
Email Permission Boolean indicating if the user has given permission to receive emails.
Add Tags Comma-separated list of tags to add to the user.
Remove Tags Comma-separated list of tags to remove from the user.
Address Collection of address fields including: Address Line 1, Address Line 2, City, State, Zip Code, Country, Latitude, Longitude.
Custom User Properties Multiple key-value pairs for setting custom user properties (e.g., memberStatus, department, role).

Output

The node outputs JSON data representing the updated user object returned by the Solidarity Tech API. The structure typically includes all user fields after the update, reflecting changes made. The output does not include binary data.

Example output snippet (conceptual):

{
  "id": "user123",
  "phone_number": "+1234567890",
  "email": "user@example.com",
  "first_name": "John",
  "last_name": "Doe",
  "preferred_language": "en",
  "sms_permission": true,
  "add_tags": ["tag1", "tag2"],
  "address": {
    "address1": "123 Main St",
    "city": "Anytown",
    "state": "CA",
    "zip_code": "90210",
    "country": "USA",
    "lat": 34.05,
    "lon": -118.25
  },
  "custom_user_properties": {
    "memberStatus": "active",
    "department": "engineering"
  }
}

Dependencies

  • Requires an API key credential configured in n8n for authenticating with the Solidarity Tech API.
  • The node uses the base URL provided in credentials to construct API requests.
  • The API expects JSON content type and supports standard REST methods (PUT for update).

Troubleshooting

  • Invalid JSON in Raw Input: If using raw JSON input for user data, invalid JSON syntax will cause an error. Ensure the JSON is well-formed.
  • Missing User ID: The update operation requires a valid User ID; omitting it will result in an error.
  • API Authentication Errors: Failure to provide valid API credentials or misconfigured credentials will cause authentication failures.
  • Invalid Base URL: The base URL must be a valid HTTPS URL; otherwise, the request will fail.
  • Permission Flags: Boolean permission fields must be correctly set; incorrect types may cause validation errors.
  • Tag Formatting: Tags should be comma-separated strings without extra spaces; improper formatting might lead to unexpected behavior.

To resolve errors, verify credentials, ensure required parameters are provided, and validate JSON inputs.

Links and References

Discussion