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 customer record in the Straddle system via the API. It is designed for platforms or applications that need to onboard customers by submitting detailed customer information such as name, type (individual or business), contact details, compliance data, and device info.
Common scenarios where this node is beneficial include:
- Financial platforms onboarding new users/customers.
- Business systems integrating with Straddle to manage customer profiles.
- Compliance workflows requiring structured customer data submission.
For example, a fintech app can use this node to register a new user by providing their full name, email, phone number, address, and compliance profile, enabling further payment or payout operations.
Properties
| Name | Meaning |
|---|---|
| Straddle Account Id | For platforms to specify an account ID to set the scope of the request (sent as HTTP header). |
| Request Id | Optional client-generated identifier to trace and debug a single request (sent as HTTP header). |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests (sent as HTTP header). |
| Name | Full name of the individual or business name (required). |
| Type | Customer type; options are "Individual" or "Business" (required). |
| The customer's email address (required). | |
| Address | JSON object containing address information such as line1, line2, city, state, postal code, country. |
| Phone | Customer's phone number in E.164 format; mobile preferred (required). |
| Compliance Profile | JSON object with compliance-related information about the customer. |
| External Id | Unique identifier for the customer in your own database for cross-referencing. |
| Device | JSON object describing device information like IP address and user agent (required). |
| Metadata | User-defined key-value pairs for custom metadata (JSON object). |
Output
The node outputs the response from the Straddle API after creating the customer. The output is a JSON object representing the newly created customer resource, including all submitted fields and additional metadata or status information returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests to the Straddle API.
- The base URL for the API is dynamically constructed based on the environment specified in credentials.
- The node sends JSON-formatted requests and expects JSON responses.
Troubleshooting
- Missing required fields: Ensure all required properties (Name, Type, Email, Phone, Device) are provided; otherwise, the API will reject the request.
- Invalid phone format: Phone numbers must be in E.164 format; incorrect formatting may cause validation errors.
- Malformed JSON inputs: Properties like Address, Compliance Profile, Device, and Metadata expect valid JSON strings; invalid JSON will cause parsing errors.
- Authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
- Header issues: Custom headers like Straddle Account Id, Request Id, and Correlation Id should be unique strings if used; improper values might affect request tracing.
Links and References
- Straddle API Documentation (hypothetical link)
- E.164 Phone Number Format
- n8n documentation on HTTP Request Node (for understanding routing and headers)