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 operation creates a new organization in the Straddle system via its API. It allows users to define key details about an organization such as its name, external identifier, metadata, and optional tracing headers for request debugging.
Typical use cases include:
- Automating onboarding workflows by programmatically creating organizations in Straddle.
- Integrating internal systems with Straddle to keep organizational data synchronized.
- Adding organizations dynamically based on events or triggers from other applications.
For example, after collecting organization details in a form, this node can be used to create the organization record in Straddle automatically.
Properties
| Name | Meaning |
|---|---|
| Request Id | Optional client-generated identifier to trace and debug a specific request. |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests. |
| Name | Required. The name of the organization to be created. |
| Metadata | User-defined key-value pairs (JSON object) to attach custom metadata to the organization. |
| External Id | Unique identifier for the organization in your own database, used for cross-referencing between systems. |
Output
The node outputs JSON data representing the newly created organization as returned by the Straddle API. This typically includes all the organization's properties such as its assigned ID, name, metadata, external ID, and possibly additional status or verification details depending on the API response.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to authorize requests to the Straddle API.
- The base URL for API requests is dynamically set based on the environment specified in credentials.
- The node sends HTTP requests with
Content-Type: application/jsonand expects JSON responses.
Troubleshooting
- Missing Required Fields: If the "Name" property is not provided, the API will likely reject the request. Ensure all required fields are filled.
- Invalid JSON in Metadata: The "Metadata" field expects valid JSON. Invalid JSON syntax will cause parsing errors before sending the request.
- Authentication Errors: If the API key or token is missing or invalid, the request will fail with authorization errors. Verify credentials configuration.
- API Endpoint Issues: The base URL depends on the environment parameter; ensure it is correctly set to avoid connection failures.
- Header Injection: The optional "Request Id" and "Correlation Id" headers must be strings; incorrect types may cause header formatting issues.
Links and References
- Straddle API Documentation (hypothetical link)
- n8n HTTP Request Node Documentation (for understanding how API calls are made)
- JSON Schema Reference for Metadata: https://json-schema.org/understanding-json-schema/
If you need further details on other operations or resources, feel free to ask!