Actions81
- Users Actions
- Organizations Actions
- Representatives Actions
- Bridge Actions
- Platforms Actions
- Tools Actions
- User Invites Actions
- Customers Actions
- Paykeys Actions
- Reports Actions
- Charge Actions
- Funding Events Actions
- Payments Actions
- Payout Actions
- Accounts Actions
- Get Account By Id
- put__v1_accounts_account_id
- Create Account
- get__v1_accounts
- post__v1_accounts_account_id_onboard
- post__v1_accounts_account_id_simulate
- patch__v1_internal_accounts_account_id
- get__v1_internal_accounts_account_id
- patch__v1_internal_accounts_account_id_status
- get__v1_internal_accounts_account_id_settings
- Capability Requests Actions
- Linked Bank Accounts Actions
Overview
This node allows you to create a new user in the target system by sending user details such as name, email, roles, and organizational information. It is useful in scenarios where you want to automate user onboarding or integrate user management workflows with other systems.
For example, you can use this node to:
- Automatically add new employees to your internal platform when they join the company.
- Create users in a SaaS application as part of a customer signup process.
- Synchronize user accounts between different services.
Properties
| Name | Meaning |
|---|---|
| Request Id | Optional client-generated identifier to trace and debug a request (sent as HTTP header). |
| Correlation Id | Optional client-generated identifier to trace and debug a series of requests (HTTP header). |
| Organization Id | The unique identifier of the organization this user belongs to (included in request body). |
| Platform Id | Identifier for the platform associated with the user (included in request body). |
| Authenticator Id | Unique identifier used for authentication purposes (included in request body). |
| First Name | The first name of the user (required, included in request body). |
| Last Name | The last name of the user (required, included in request body). |
| The email address of the user; used for login and communication (required, in request body). | |
| Roles | JSON array defining the role(s) assigned to the user, determining their permissions (required). |
Output
The node outputs the response from the API call in the json field of the output data. This typically contains the created user's details including identifiers, status, and any metadata returned by the service.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the external Straddle API.
- The base URL for API requests is dynamically set based on the configured environment credential.
- The node sends JSON-formatted requests and expects JSON responses.
Troubleshooting
- Missing required fields: Ensure all required properties (
first_name,last_name,email,roles) are provided; otherwise, the API may reject the request. - Invalid roles format: The
rolesproperty must be valid JSON; invalid JSON will cause parsing errors. - Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network issues: Check connectivity to the API endpoint and ensure the correct environment is selected.
- Header injection: If using
Request IdorCorrelation Id, ensure values are properly formatted strings.
Common error messages will likely come from the API and relate to validation failures, authentication issues, or rate limiting. Review the API documentation for specific error codes.
Links and References
- Straddle API Documentation (example placeholder)
- n8n documentation on Creating Custom Nodes
- JSON schema standards for defining user roles and attributes