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 interacts with the "Users" resource of an API to retrieve information about invited users based on their email address. Specifically, the operation get__v1_internal_users_invited fetches details about users who have been invited but not necessarily accepted or completed registration.
Common scenarios where this node is useful include:
- Verifying if a user with a specific email has been invited to a system.
- Auditing or tracking invitation statuses for compliance or operational purposes.
- Integrating invitation status checks into automated workflows, such as sending reminders or follow-ups.
Practical example:
- A workflow that triggers when a new invitation email is sent and uses this node to confirm the invitation was registered in the system before proceeding with further onboarding steps.
Properties
| Name | Meaning |
|---|---|
| The email address of the user to look up among invited users. | |
| Request Id | Optional client-generated identifier to trace and debug a single request (sent as header). |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests (header). |
Output
The node outputs JSON data representing the invited user(s) matching the provided email. The structure typically includes user details as returned by the API, which may contain fields like user ID, invitation status, timestamps, and other metadata related to the invitation.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authentication to the Straddle API.
- The base URL for API requests is dynamically constructed using the environment specified in credentials.
- The node sends HTTP requests with headers including
Accept: application/jsonandContent-Type: application/json. - Optional headers
request-idandcorrelation-idcan be set for tracing/debugging purposes.
Troubleshooting
- Empty or no results: If the email does not correspond to any invited user, the output will be empty or null. Verify the email input is correct.
- Authentication errors: Ensure the API key credential is correctly configured and has necessary permissions.
- Request tracing: Use the optional
Request IdandCorrelation Idproperties to help trace and debug requests in logs or monitoring tools. - API endpoint issues: Confirm the environment value used to build the base URL is valid and reachable.
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 request tracing