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 delete a customer record from the Straddle API by specifying the customer's unique identifier. It is useful in scenarios where you need to programmatically remove customer data, such as cleaning up test accounts, managing user lifecycle, or complying with data deletion requests.
For example, if you have a workflow that processes customer churn and want to automatically delete customers who unsubscribe, this node can be used to perform that deletion via the API.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the customer to delete. |
| Straddle Account Id | (Optional) For platforms: specifies an account ID to set the scope of the request via header. |
| Request Id | (Optional) Client-generated identifier to trace and debug a specific request via header. |
| Correlation Id | (Optional) Client-generated identifier to trace and debug a series of related requests via header. |
Output
The node outputs JSON data representing the response from the Straddle API after attempting to delete the specified customer. Typically, this will include confirmation of deletion or error details if the operation failed.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Straddle API.
- The base URL for API requests is dynamically constructed based on the configured environment credential.
- The node uses standard HTTP headers including
Accept: application/jsonandContent-Type: application/json. - Optional custom headers (
Straddle-Account-Id,Request-Id,Correlation-Id) can be set to provide additional context or scoping.
Troubleshooting
- Missing or invalid Id: The
Idproperty is required. If omitted or incorrect, the API will return an error indicating the customer was not found. - Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions to delete customers.
- Scope issues: If using
Straddle Account Id, verify that the account ID is valid and that your API key has access to it. - Rate limiting or network errors: Standard HTTP errors may occur; retry logic or error handling should be implemented in workflows.
- Error messages returned by the API typically include status codes and descriptive messages; check these to diagnose issues.
Links and References
- Straddle API Documentation (hypothetical link)
- n8n documentation on HTTP Request Node for understanding how API calls are made
- General best practices for API authentication and error handling in n8n workflows