Automate Gift Card Fulfillment with Make.com

Running a gift card resale operation means executing the same sequence hundreds of times a day: receive an order, look up a product ID, call a wholesale API, receive a delivery code, and route it to the buyer. Every manual step costs time and introduces errors. Make.com — a visual no-code automation platform formerly known as Integromat — lets you connect your storefront to external APIs through drag-and-drop workflows called scenarios. Wire it to the FazerCards wholesale API and the entire fulfillment sequence runs unattended, completing in seconds for each order, around the clock.

Prerequisites

Before building your scenario, have three things ready:

• A FazerCards account. The free 5-day Gold trial gives you full API access and the entire catalog — enough to build and validate the automation before committing to a paid plan.
• A Make.com account. The free tier handles low-volume testing; upgrade when your order throughput demands it.
• An order intake source: a Shopify storefront, a Telegram bot, a form, or any system that can POST a JSON payload to a URL when a customer places an order.

Step 1: Understand the FazerCards API flow

Spend a few minutes with the API reference before opening Make.com. The FazerCards API is REST-based: you authenticate with an API key in the request header, query the catalog for the product IDs you plan to sell, then POST to the orders endpoint. For most products the delivery code arrives in the response within seconds — that instant-delivery pipeline is what makes hands-free automation viable at scale.

You will need two things from the API docs: the exact field names for the order request body and the header name used for authentication. Keep the docs tab open while configuring Make.com.

Step 2: Create a webhook trigger

In Make.com every scenario begins with a trigger. For a gift card store, a webhook trigger is the right starting point.

1. Open Make.com and click Create a new scenario.
2. Add a Webhooks → Custom Webhook module as the trigger.
3. Make.com generates a unique HTTPS endpoint URL for the webhook. Copy it.
4. Paste that URL as the destination in your storefront or order-intake system. Every confirmed purchase will POST a JSON payload to that address — typically containing the product name or your internal SKU, the quantity, and the buyer contact detail (email or Telegram ID).
5. Click Run once in Make.com, then place a test order in your storefront. Make.com captures the incoming payload automatically, naming each field so they appear as selectable items in later modules.

Keep the test order result open — you will reference its fields throughout the remaining steps.

Step 3: Map product names to FazerCards product IDs

Your storefront likely uses human-readable product names such as Xbox $25 Gift Card. The FazerCards API expects a numeric product ID. Bridge that gap before the order module runs.

The cleanest solution in Make.com is a Data Store: a key-value table where each key is your product name and each value is the corresponding FazerCards product ID. Populate it once by browsing the FazerCards catalog, then read from it in your scenario.

Add a Data Store → Get a Record module after the webhook trigger. Pass the product name from the webhook payload as the search key. The returned value is the FazerCards product ID you will use in the next step.

Step 4: Call the FazerCards API to purchase and receive the code

1. Add an HTTP → Make a request module after the data store lookup.
2. Set the method to POST and enter the FazerCards orders endpoint from the API docs.
3. In the request headers, add your API key using the header name specified in the docs.
4. Set the body type to Raw (JSON) and build the payload by mapping fields from the earlier modules: the product ID from the data store lookup, the quantity from the webhook payload, and a unique order reference from your storefront. The order reference is critical — FazerCards uses it for idempotency so that if Make.com retries the step after a network hiccup, the same purchase never fires twice.
5. Parse the JSON response using a JSON → Parse JSON module. The parsed output exposes the delivery code and any additional fields as individual mappable values.

For a deeper look at webhook-based status callbacks — useful when you want FazerCards to push delivery notifications to your server — see the webhooks guide and the article on FazerCards API webhooks and integration patterns.

Step 5: Deliver the code to the customer

This step depends on your sales channel:

• Email — add a Gmail or generic SMTP module. Compose the delivery message using Make.com's templating system: pull the code from the parsed API response and the customer email from the original webhook payload.
• Telegram — add a Telegram Bot → Send a Message module. Map the customer chat ID from the webhook payload and include the code plus redemption instructions in the message body.
• Storefront callback — POST the delivery result back to your storefront's order-update endpoint so the order status changes to Fulfilled automatically.

Whichever channel you choose, log each delivery in a Make.com Data Store or a connected Google Sheet: order reference, product, timestamp, and delivery outcome. That record becomes your audit trail if a buyer disputes a delivery.

Step 6: Add error handling and go live

A scenario that only works when everything succeeds is not production-ready. Configure error handling on two critical steps:

• On the FazerCards API call — if the HTTP module returns a non-200 status, route the error to a notification step (email or Telegram) that alerts you immediately with the order reference and error details. Never let a purchase failure go unnoticed.
• On the delivery step — if sending the code to the buyer fails, write the undelivered code to a backup Data Store so you can retry manually. A purchased code that never reaches the buyer is both a financial and reputational loss.

Set the scenario's built-in retry limit to three attempts for transient network errors, then stop and alert rather than retrying indefinitely.

Before routing live orders through the scenario, run a full end-to-end test:

1. Place a test order using a small-denomination product such as a Google Play gift card or a Roblox card.
2. Confirm every module shows a green checkmark in the Make.com execution log.
3. Verify the code arrived at the test recipient.
4. Cross-check the order in your FazerCards dashboard.

Once the test passes, enable Scheduling in Make.com to keep the scenario active around the clock.

What you have at the end

With this scenario running, every order flows from your storefront through Make.com to the FazerCards API and back to the buyer without any manual action on your part. The same workflow handles the full 10,000+ product catalog: adding a new SKU means adding one record to the data store, not changing a line of code. The scenario scales with your order volume — limited only by your Make.com plan's monthly operation count, not by developer availability.

From here, extend the scenario: add a branch that sends a daily summary of order counts and revenue to a Telegram channel, or wire the scenario into a FazerCards subscription tier check to verify you are on the plan that best fits your current volume.

Claim a free 5-day Gold trial to get your API key today — no payment information required — and wire up your first automated fulfillment scenario before the weekend.