Create a card after a new CRM contact
Use the CRM contact ID as External ID, create a 7stamp card invite, then send the returned install URL through your usual email, SMS, or messaging step.
No-code automation guide
Connect 7stamp to Make — step by step
Implementation guideUse Make to connect 7stamp with a CRM, POS, online shop, spreadsheet, messaging tool, or any system that can send data into a scenario. The production-ready route today is Make's HTTP app for 7stamp API calls and Make's Custom webhook for incoming 7stamp events.
There is no public 7stamp app in Make's app picker yet. Do not wait for one: add HTTP → Make a request, use the exact URL, method, Bearer header, and JSON below, then map the fields from your source module. This is the same 7stamp Integration API a future connector would use.
Choose the first scenario that matches your workflow
Start with one event and one outcome. Once the test data is correct, add filters, routers, CRM updates, and follow-up messages around it.
Add stamps after a paid order
Trigger the scenario from a paid POS or ecommerce order. Map its stable customer ID and order ID into Scan a Card, then use an amount or explicit stamp count.
Send a reward follow-up
When a card event reports a reward or voucher, branch the scenario: update the CRM, notify the team, and send a wallet-card push or email only when needed.
Handle a system without a native Make app
Use Make's HTTP module to call 7stamp directly. This is the universal choice for a custom POS, ERP, booking engine, or any API-first service.
7stamp operations to call from Make HTTP
For each card below, add HTTP → Make a request, then set the method and URL exactly as shown. Use the same Bearer key for every request. The required mapping tells you what to supply from your CRM, POS, or ecommerce trigger.
Make trigger
Webhooks → Custom webhook Receive a card event
Create a Custom webhook in Make, copy its URL, then paste that URL into the 7stamp profile webhook settings. This starts a scenario when 7stamp sends an event such as SCAN, REWARD_EARNED, or VOUCHER_ISSUED.
- In Make
- Webhooks → Custom webhook → Add; give it a clear name and copy its generated URL.
- In 7stamp
- Admin → API & Integrations → Webhooks; paste the URL, select event types, save, then create a test event.
HTTP action
POST /cards/invite Create a Card Invite
Creates a fresh personal install URL and delivery-insert code for one external contact.
- Required
- external_id — map your stable CRM/contact ID, not a name.
- Then use
- Map install_url from the response into your email, SMS, or CRM update step.
HTTP action
POST /cards/invite/bulk Bulk Create Card Invites
Creates up to 100 invite links in one request. Use it for a controlled migration or campaign, not an unbounded contact export.
- Required
- items — a JSON array of 1–100 individual invite request objects.
- Check
- Read success_count, error_count, and each result before sending any links.
HTTP action
GET /cards Find Cards
Finds card records by External ID, with optional template and source filters.
- Required
- Query parameter external_id.
- Optional
- external_source and template_id narrow the lookup when one system has multiple programmes.
HTTP action
GET /cards/{user_card_id} Get a Card Detail
Reads the full state of one card when a prior step has returned its internal User Card ID.
- Required
- Replace {user_card_id} with the internal ID returned by a trusted 7stamp response.
- Avoid
- Do not guess or store a card ID from a different profile.
HTTP action
POST /cards/scan Scan a Card
Adds stamps from a purchase amount or an explicit count. It accepts User Card ID or External ID and can retain the external order reference.
- Identity
- Use external_id and optional external_source; user_card_id wins if both are supplied.
- Purchase
- Use amount for amount-based cards or stamps_count for an explicit number; stamps_count takes priority.
- Traceability
- Map external_order_id from the paid order/receipt so 7stamp events can be matched back.
HTTP action
GET /templates List Templates
Lists the card templates available to the API key. Use it to test the connection or to select a template dynamically.
- First test
- This is the safest first request: it has no body and does not change customer data.
- Map later
- Use an active template's id as template_id only when the profile has more than one active template.
HTTP action
GET /templates/{template_id}/design Get Template Design
Returns the visual design settings for a known template, useful when another system needs to display a consistent card choice.
HTTP action
POST /vouchers/issue Issue a Voucher
Issues a voucher to a card owner identified by External ID or User Card ID.
- Required
- voucher.short_description. Target the card with external_id or a known user_card_id.
- Validity
- Use validity_type with validity_value, or read the OpenAPI reference for a fixed expiry date.
HTTP action
POST /messages/send Send a Message
Sends content to the card owner through wallet-card push and/or email, subject to the configured channel and consent rules.
- Card push
- card_push_text is limited to 20 characters and requires an installed wallet pass.
- Send subject plus body; basic HTML is supported in the body.
Make module
Full 7stamp endpoint URL HTTP → Make a request
This is the Make module that calls every 7stamp route above. Use a complete URL, select the documented method, add the Bearer header, and use JSON only when the route needs a body.
- Base URL
- https://api.7loc.com/cards-api
- Header
- Authorization: Bearer YOUR_7STAMP_API_KEY; Content-Type: application/json for POST requests.
Three Make scenarios you can build exactly as written
The names below are the real Make modules. Start with the first scenario, run it against a disposable contact, and only then add routers, filters, or production scheduling.
1. New CRM contact → send a 7stamp card link
Expected result: The customer receives the install_url returned by 7stamp; your CRM can keep that URL in the same contact record.
- 1 Create a scenario and add your CRM's New/Created Contact trigger. For Kommo, choose the contact creation trigger and run it once to load a sample contact.
- 2 Add HTTP → Make a request. Set Method to POST and URL to https://api.7loc.com/cards-api/cards/invite.
- 3 Add Authorization: Bearer YOUR_7STAMP_API_KEY and Content-Type: application/json. In the JSON body, map the CRM contact ID into external_id and set external_source to a fixed label such as kommo.
- 4 Run the HTTP module once. Confirm the output has install_url, delivery_insert_code, external_id, and template_id.
- 5 Add your email/SMS/CRM update module after HTTP and map install_url from the HTTP output. Save the URL on the CRM contact if the team must resend it later.
Check: POST /cards/invite always creates a fresh invite. Use Find Cards first if your business rule is to avoid another invite for an existing contact.
2. Paid order → add loyalty stamps
Expected result: A successful scan response includes success, scan_id, stamps_added, and the post-scan card state for your next step.
- 1 Start from the POS/ecommerce Paid Order trigger. Make sure its sample contains a stable customer ID and the order/receipt ID.
- 2 Add HTTP → Make a request with POST https://api.7loc.com/cards-api/cards/scan and the same Bearer header.
- 3 Map external_id from the customer, external_source from the system name, and external_order_id from the order ID. Add amount for amount-based cards, or stamps_count for an explicit number of stamps.
- 4 Run once with a test order. Check the returned success flag and stamps_added before enabling the scenario schedule.
- 5 Optionally add a filter after the HTTP step: continue only when success is true, then write scan_id or stamps_added back to the order/CRM record.
Check: Use the same external_order_id on retries so the order can be traced in later webhook events; do not award stamps twice after an unclear failed run.
3. 7stamp event → update the CRM
Expected result: Make receives the 7stamp event immediately and can find the matching CRM record via external_id and external_source.
- 1 Create a separate Make scenario. Add Webhooks → Custom webhook, select Add, name it 7stamp-card-events, and copy the generated URL.
- 2 In 7stamp Admin, open API & Integrations → Webhooks. Add that URL and select a small set of events, for example SCAN and REWARD_EARNED.
- 3 Create a disposable test scan or card event in 7stamp. Return to Make and use Run once to let Make determine the event data structure.
- 4 Add a CRM search step using external_id. Add a filter or router on event_type so SCAN, REWARD_EARNED, and VOUCHER_ISSUED can take different actions.
- 5 Add the CRM update/note action. Map scanned_at, stamps_after, external_order_id, and issued_vouchers only when those fields are present for the selected event type.
Check: Keep the webhook URL private. Test a real event before switching on irreversible messages, vouchers, or CRM changes.
Get the 7stamp API key before opening Make
These are the exact 7stamp Admin screens. Create the key once, copy it into Make's secure HTTP connection/keychain, then immediately remove it from your clipboard.
Prepare the connection before building
Create one API key per environment
In 7stamp Admin, go to API & Integrations → API Keys → Add API Key. Store the value in Make's HTTP API-key connection/keychain when that option is available. Never map the key from a text field, place it in a note, or use it in a browser-facing workflow. A key belongs to one 7stamp workplace/profile.
Use a stable External ID
Map the immutable ID from your CRM, POS, or commerce platform—for example a CRM contact ID or customer UUID. Add External Source such as hubspot, shopify, or poster when the same identifier could appear in more than one system.
Decide which template applies
When the connected 7stamp profile has one active card template, Template can be left empty. With multiple templates, map or choose template_id deliberately so every invite and scan reaches the intended loyalty programme.
Exact Make HTTP setup: create one card invite
Copy this into your automation step
http Method: POST
URL: https://api.7loc.com/cards-api/cards/invite
Headers:
Authorization: Bearer YOUR_7STAMP_API_KEY
Content-Type: application/json
Body type: Raw / JSON
{
"external_id": "crm_contact_8821",
"external_source": "hubspot",
"template_id": 42
}Build and test your first Make scenario
In 7stamp Admin, create a key in API & Integrations → API Keys → Add API Key. Use a separate test profile/key when your account setup allows it.
In Make, create a scenario and add the source trigger. Run it once before mapping so you can see a real sample contact or paid order.
Click the next plus, search for HTTP, and choose Make a request. Set the method, full URL, and headers from the operation card on this page.
Use GET https://api.7loc.com/cards-api/templates as the first request. Its successful response proves the key works without changing any customer data.
For POST routes, select application/json and paste the body shape from this guide. Map a stable External ID; add template_id only if the profile has multiple active templates.
Run with a disposable contact, inspect the HTTP output, and only then map its exact response fields into the next CRM, email, or messaging module.
When should you use Make HTTP?
Use HTTP for 7stamp now: it is the documented, production-ready route, not a reduced fallback. Choose it whenever you need a 7stamp operation, a new API route, or a custom POS/ERP connection. The OpenAPI reference is the source of truth for the method, full path, body, and response schema; the bearer key and base URL stay the same.
Receive 7stamp events in Make
For an event-driven scenario, add Webhooks → Custom webhook and create a webhook. Copy its URL, open API & Integrations → Webhooks in the 7stamp profile, paste the URL, select the event types, save, and send a real test event. The 7stamp profile owns that subscription; the current API does not expose automatic webhook subscribe/unsubscribe endpoints.
No public Make connector is required
The instructions on this page use Make modules that are available to every Make account. If you want a future native 7stamp module rather than HTTP, send us the workflow you need; until then, HTTP and Custom webhooks cover every documented 7stamp operation.
Frequently asked questions
I cannot find 7stamp in Make. Can I still automate it?
Yes. There is no public 7stamp app in Make today. Add HTTP > Make a request, use the complete 7stamp endpoint URL, and send Authorization: Bearer followed by your 7stamp API key. HTTP can call every documented endpoint.
Where do I get the token for the Make connection?
In 7stamp Admin, open API Integrations, then API Keys, then Add API Key. The key is scoped to the workplace/profile that created it, so use a test profile for test scenarios whenever possible.
Which identifier should I map as External ID?
Use the stable identifier from the source system, preferably a CRM contact ID or customer UUID. Do not use a display name. A phone number or email can work, but can change and should be handled consistently.
How do I get 7stamp events into Make?
Create a Webhooks > Custom webhook in Make, then paste its generated URL into the webhook settings of the 7stamp profile. Use a Make filter or router after delivery to handle the incoming event_type.
Next step
Ready to automate the first loyalty action?
Create the API key, test List Templates, and build one invite or scan scenario with a disposable contact. Add routers and messaging only after that simple flow is reliable.