Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
The "Get Cards Lookup" operation retrieves card information from an external integration by querying with a required integration slug and optional additional query parameters. This node is useful when you need to fetch card details linked to a specific external system, for example, retrieving payment card data or membership cards associated with a particular integration.
Practical examples include:
- Fetching user payment card details from a connected payment gateway.
- Looking up membership or loyalty cards from an external CRM or loyalty program.
- Integrating card data into workflows that require validation or enrichment of card-related information.
Properties
| Name | Meaning |
|---|---|
| Integration Slug | Identifier of the external integration. This is a required string that specifies which integration to query. |
| Additional Query Parameters | Optional collection of extra query fields: • Integration Id: ID in the external integration (required if Integration Identifier is not set). • Integration Identifier: Alternative identifier used if Integration Id is not provided. |
Output
The node outputs JSON data containing the card lookup results retrieved from the external integration. The exact structure depends on the external API response but typically includes card details such as card IDs, identifiers, and related metadata.
No binary data output is indicated.
Dependencies
- Requires an API key or authentication token configured in the node credentials to access the external integration's API.
- The base URL and headers for the API requests are expected to be set via node credentials or configuration.
- Uses query parameters to send the integration slug and optional identifiers to the external service.
Troubleshooting
- Missing Required Parameter: If the "Integration Slug" is not provided, the node will fail because it is mandatory.
- Invalid Identifiers: Providing neither "Integration Id" nor "Integration Identifier" in additional parameters may cause the external API to reject the request or return no results.
- Authentication Errors: Ensure the API key or authentication token is correctly configured; otherwise, the external service may respond with authorization errors.
- Network Issues: Connectivity problems to the external API endpoint can cause timeouts or failures.
- Unexpected Response Structure: If the external API changes its response format, downstream nodes expecting certain JSON fields might fail.
Links and References
- Refer to the external integration’s API documentation for detailed information about the card lookup endpoint and required parameters.
- n8n documentation on HTTP Request node for understanding how query parameters and credentials work.