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 updating the review status of a specific customer in the "Customers" resource by sending a PATCH request to the endpoint that reviews a customer by their ID. It is useful in workflows where you need to programmatically verify or reject customers based on some external logic or automated checks.
Typical use cases include:
- Automating customer verification processes after manual or automated review.
- Integrating with compliance systems to update customer review statuses.
- Triggering downstream actions based on whether a customer was verified or rejected.
For example, after running an identity verification check externally, this node can be used to mark the customer as "verified" or "rejected" accordingly.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the customer whose review status you want to update (required). |
| Straddle Account Id | Optional header to specify an account id for scoping the request, typically used by platforms. |
| Request Id | Optional client-generated identifier to trace and debug this specific request. |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests. |
| Status | The new review status to set for the customer. Options: "Verified" or "Rejected" (required). |
Output
The node outputs the JSON response from the API call, which typically contains the updated customer review information including the new status. The exact structure depends on the API but generally includes fields confirming the status change and possibly metadata about the customer.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Straddle API.
- Needs the environment subdomain configured in credentials to construct the base URL (
https://{environment}.straddle.io). - The node uses standard HTTP headers and JSON payloads.
Troubleshooting
- Missing or invalid Id: The node requires a valid customer ID; ensure it is provided and correctly formatted.
- Authentication errors: Verify that the API key credential is correctly set up and has permissions to update customer reviews.
- Invalid status value: Only "verified" or "rejected" are accepted; other values will cause errors.
- Network or API errors: Check connectivity and API availability; also confirm the environment subdomain is correct.
- Header conflicts: If using optional headers like
Straddle-Account-Id, ensure they are valid and expected by the API.
Common error messages usually relate to authentication failures, missing parameters, or invalid status values. Resolving these involves checking credentials, input parameters, and API documentation.
Links and References
- Straddle API Documentation (hypothetical link)
- n8n HTTP Request Node documentation for general API interaction guidance
- Best practices for handling API keys and request tracing in n8n workflows