Actions47
- Template Actions
- Communication Actions
- Card Actions
- Create
- Get
- Get All
- Update
- Delete
- Get Balance
- Add Points
- Deduct Points
- Add Amount
- Deduct Amount
- Add Stamps
- Deduct Stamps
- Transfer Points
- Transfer Amount
- Block Card
- Unblock Card
- Generate QR Code
- Get Operations
- Add Visits
- Deduct Visits
- Add Reward
- Deduct Reward
- Receive Reward
- Redeem Coupon
- Set Expiration Date
- Set Membership Tier
- Customer Actions
- Company Actions
- Analytics Actions
- System Actions
Overview
This node interacts with the Digital Wallet Cards API, specifically focusing on operations related to card templates when using the "Template" resource. The "Get" operation retrieves detailed information about a specific card template by its ID.
Typical use cases include:
- Fetching the configuration and details of a loyalty or membership card template.
- Integrating template data into workflows for customer engagement or marketing automation.
- Using template details to create new cards or manage reward tiers programmatically.
For example, you might use this node to get the details of a template before issuing new cards based on it or to display template information in a dashboard.
Properties
| Name | Meaning |
|---|---|
| Template ID | The numeric identifier of the card template to retrieve. This is required to specify which template's details to fetch. |
Output
The output JSON contains the detailed information of the requested card template. This typically includes fields such as template ID, name, type, status, and other metadata describing the card template.
The structure corresponds directly to the API response for a single template object, transformed for easier consumption in n8n workflows.
No binary data is output by this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the Digital Wallet Cards API.
- The node makes HTTP requests to
https://api.digitalwallet.cards/api/v2/templates/{templateId}endpoint. - No additional external dependencies are needed beyond the configured API credentials.
Troubleshooting
- Missing or invalid Template ID: The node requires a valid numeric Template ID. Ensure this property is set and corresponds to an existing template.
- API authentication errors: Verify that the API key credential is correctly configured and has permissions to access template data.
- Network or API errors: Check connectivity to the Digital Wallet Cards API and ensure the service is operational.
- Unexpected response format: If the API changes, the node may fail to parse the response correctly. Updating the node or checking API documentation may be necessary.
Common error messages will indicate missing required parameters or failed HTTP requests. Review the error message details and verify input properties and credentials.
Links and References
- Digital Wallet Cards API Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes
- General API Authentication best practices in n8n
This summary focuses exclusively on the "Template" resource with the "Get" operation as requested.