dots.eco icon

dots.eco

Work with dots.eco API. Rewarding you for casually saving the planet.

Actions19

Flow Card → Create

AI-generated

Overview

This node interacts with the dots.eco API to create flow cards. It is useful for automating the creation of digital flow cards that can be used for rewards or gifting purposes. For example, a business can use this node to generate flow cards with specific SKUs, optional expiration dates, and personalized recipient and sender information, including messages.

Use Case Examples

  1. Creating a flow card with a specific SKU and sending it to a recipient's email with a personalized message.
  2. Automating the creation of flow cards with expiration dates for promotional campaigns.

Properties

Name Meaning
App Token Application token used to authenticate and authorize the creation of flow cards.
SKU SKU of the flow card to create, identifying the specific type or design of the card.
Expiration Date Optional expiration date for the flow card in YYYY-MM-DD format.
Recipient Email Optional email address of the recipient who will receive the flow card.
Recipient Name Optional name of the recipient shown on the flow card.
Sender Name Optional name of the sender shown on the flow card.
Message Optional message included with the flow card, allowing personalization.

Output

JSON

  • json
    • id - Unique identifier of the created flow card.
    • sku - SKU of the created flow card.
    • expirationDate - Expiration date of the flow card if set.
    • recipientEmail - Email address of the recipient if provided.
    • recipientName - Name of the recipient if provided.
    • from - Name of the sender if provided.
    • message - Personalized message included with the flow card.

Dependencies

  • dots.eco API
  • An API key credential for authentication

Troubleshooting

  • Ensure the App Token is valid and has the necessary permissions to create flow cards.
  • Verify that the SKU provided corresponds to an existing flow card SKU in the dots.eco system.
  • Check the format of the expiration date to be YYYY-MM-DD if provided.
  • If the node throws authentication errors, confirm that the API key credential is correctly configured and active.

Links

Discussion