Actions22
- User Actions
- User Note Actions
- User Action Actions
- User Relationship Actions
- Event Actions
- Event Session Actions
- Event RSVP Actions
- Event Attendance Actions
- User List Actions
- Pages Actions
User Action → Create
AI-generatedOverview
The node operation "Create" under the "User Action" resource allows you to create a new user action record in the Solidarity Tech system. This is useful for tracking specific actions performed by users on a given page, such as clicks, form submissions, or other interactions that need to be logged for analytics, auditing, or workflow automation purposes.
Typical use cases include:
- Logging user interactions on a website or app page.
- Tracking engagement metrics by recording user actions.
- Triggering downstream workflows based on user behavior.
For example, you might create a user action when a user submits a contact form on a particular page, capturing the user ID, page ID, timestamp, and any additional data related to the action.
Properties
| Name | Meaning |
|---|---|
| Page ID | The identifier of the page where the action occurred (required). |
| User ID | The identifier of the user performing the action (required). |
| Created At | (Optional) Timestamp when the action was created. |
| Data | Additional data about the action, constructed from user-related fields such as phone number, email, name, permissions, tags, address, and custom properties. This data is assembled from multiple input fields described below: |
| - Phone Number | User's phone number. |
| 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 second language. |
| - Chapter ID | Numeric chapter ID associated with the user. |
| - SMS Permission | Boolean indicating if the user has given SMS permission. |
| - Call Permission | Boolean indicating if the user has given call permission. |
| - Email Permission | Boolean indicating if the user has given email permission. |
| - 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 lines, city, state, zip code, country, latitude, and longitude. |
| - Custom User Properties | Multiple key-value pairs for custom user properties (e.g., memberStatus, department). |
Note: The "Data" field is automatically constructed from these inputs when creating the user action.
Output
The output JSON object represents the newly created user action as returned by the Solidarity Tech API. It typically includes:
id: Unique identifier of the created user action.page_id: The page ID where the action took place.user_id: The user ID who performed the action.created_at: Timestamp of when the action was recorded.data: Object containing the detailed data about the user and action, reflecting the input fields provided.- Other metadata fields as defined by the API response.
The node outputs this data as an array of JSON objects, one per processed item.
Dependencies
- Requires an API key credential for authenticating with the Solidarity Tech API.
- The base URL for the API must be configured in the credentials.
- The node uses HTTP requests with JSON payloads to communicate with the Solidarity Tech API endpoints.
Troubleshooting
- Missing Required Fields: If "Page ID" or "User ID" are not provided, the API request will fail. Ensure these required fields are set.
- Invalid JSON in Custom Properties: When using raw JSON input methods (not applicable here), invalid JSON syntax can cause errors.
- API Authentication Errors: Failure to retrieve or provide valid API credentials will result in authentication errors.
- Network or URL Issues: Invalid or missing base URL configuration can cause connection failures.
- Rate Limits: Excessive requests may trigger rate limiting; consider enabling batch processing or adding delays if supported.
Error messages typically include details about the failed HTTP request or validation issues, along with debug information to assist troubleshooting.
Links and References
- Solidarity Tech API Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for error handling and authentication.
This summary is based solely on static analysis of the provided source code and property definitions for the "User Action" resource with the "Create" operation.