Create an invite from a CRM contact
Trigger on a new or qualified contact, map its CRM ID to External ID, create a card invite, and pass the returned install URL to an email or SMS step.
No-code automation guide
Connect 7stamp to Zapier — step by step
Implementation guideUse Zapier when your workflow is a clear sequence: a contact or order appears, 7stamp performs an action, then another business tool is updated. The secure route today is API by Zapier for outgoing 7stamp API calls and Webhooks by Zapier → Catch Hook for incoming 7stamp events.
There is no public 7stamp app in Zapier's marketplace. Use API by Zapier → API Request where available: it stores a static API key in the app connection instead of exposing it in a Zap step. Use Webhooks by Zapier only for incoming Catch Hook events; do not put a 7stamp Bearer key into a visible Webhooks action field.
Start with a linear, testable Zap
Keep the first Zap small. A reliable contact-to-card or paid-order-to-stamps flow is a better starting point than a broad two-way CRM sync.
Add stamps after checkout
Trigger from the paid order or closed receipt, map the customer identity and order ID, then use Scan Card with the order amount or explicit number of stamps.
Issue a one-off recovery voucher
Use a CRM rule, support event, or segment export to identify a customer, issue a voucher to their card, and send a follow-up message from the correct channel.
Write card events back to your CRM
Use Webhooks by Zapier > Catch Hook to receive 7stamp card events. Match the returned External ID to the CRM record and add the relevant note, tag, or task.
7stamp operations to call from API by Zapier
Add API by Zapier → API Request after your trigger. Create one 7stamp API-key connection, then select the exact method and full URL below. Each operation returns fields that you can map into the next Zap step.
API by Zapier action
POST /cards/invite Create Card Invite
Creates a fresh wallet-card install URL and delivery-insert code for one external contact.
- Required
- external_id from the CRM/contact trigger.
- Next step
- Map install_url into email, SMS, or a CRM field.
API by Zapier action
POST /cards/invite/bulk Bulk Create Card Invites
Creates up to 100 invite links from a controlled JSON batch.
- Required
- items array with 1–100 invite objects.
- Check
- Read success_count, error_count, and every result before delivery.
API by Zapier action
POST /cards/scan Scan Card
Adds stamps by User Card ID or External ID, with amount, stamp count, order ID, and optional receipt data.
- Identity
- external_id plus optional external_source; user_card_id wins if both are present.
- Stamp rule
- stamps_count takes priority over amount.
API by Zapier action
POST /vouchers/issue Issue Voucher
Issues a voucher directly to a card owner.
- Required
- voucher.short_description and a target external_id or known user_card_id.
- Result
- Map unique_code, status, or expires_at to a CRM note or message.
API by Zapier action
POST /messages/send Send Message
Sends wallet-card push and/or email content to a card owner.
- Card push
- card_push_text is limited to 20 characters.
- subject plus body; the result reports whether delivery was queued.
API by Zapier action
GET /cards Find Cards
Finds card records by External ID, with optional source and template filters.
- Required
- external_id as a query parameter.
- Use first
- Use before creating an invite when your rule avoids duplicate invites.
API by Zapier action
GET /cards/{user_card_id} Get Card Detail
Reads the state of a card by its 7stamp internal ID.
- Required
- Replace {user_card_id} with an ID returned by 7stamp.
- Useful output
- stamps_count, wallet state, and active_vouchers_count.
API by Zapier action
GET /templates List Templates
Lists templates available to the connected profile and verifies the API connection.
- First test
- Call it before any write action: it changes no customer data.
- Use later
- An active id becomes template_id when multiple templates exist.
API by Zapier action
GET /templates/{template_id}/design Get Template Design
Retrieves a template's design settings for a known template ID.
Zapier trigger
Webhooks by Zapier → Catch Hook Receive card events
Catch Hook gives Zapier a unique HTTPS URL. Paste it in 7stamp Admin's webhook settings and test it with a real card event.
- In Zapier
- Use Catch Hook for parsed event data; use Catch Raw Hook only when you also need raw request headers/body.
- Match
- Find the CRM contact using external_id and optional external_source from the event.
Three Zapier workflows you can build step by step
Each scenario uses a real, currently available Zapier module. Build one small route first and test it with a disposable contact before turning the Zap on.
1. Qualified CRM contact → issue a card
Expected result: The next Zap step receives install_url and can send it to the customer or write it back to the CRM record.
- 1 Create a Zap and select the CRM event that means a contact is eligible for loyalty. Test the trigger and confirm you have the contact's immutable ID.
- 2 Add API by Zapier → API Request. Create or select the 7stamp API-key connection, choose POST, and set URL to https://api.7loc.com/cards-api/cards/invite.
- 3 Set the body to JSON. Map the CRM ID into external_id, set a fixed external_source such as kommo, and add template_id only when more than one 7stamp template is active.
- 4 Test the action. Confirm the response contains install_url and delivery_insert_code for the same external_id.
- 5 Add your CRM Update, email, or SMS action. Map install_url from the API response; do not hard-code or copy a test URL.
Check: Create Card Invite always returns a fresh invite. Add a Find Cards request or a Zapier Filter first if your policy is one invite per contact.
2. Paid order → award stamps
Expected result: The order creates a traceable 7stamp scan and the Zap can record stamps_added or scan_id in the source system.
- 1 Use a Paid Order/Closed Receipt trigger and test it. Confirm the customer ID and unique order ID are both present before continuing.
- 2 Add API by Zapier → API Request with POST https://api.7loc.com/cards-api/cards/scan and select the same 7stamp connection.
- 3 Send JSON with external_id, external_source, external_order_id, and either amount for amount-based templates or stamps_count for an explicit stamp award.
- 4 Test with a disposable order. Inspect success, scan_id, and stamps_added in the response.
- 5 Add a Filter that continues only after a successful response, then update the order/CRM with the confirmed result.
Check: If the Zap is replayed, check the original order before sending another scan. Keep external_order_id stable so the event can be reconciled later.
3. 7stamp event → create a CRM note or task
Expected result: Zapier receives a parsed 7stamp event, finds the customer by external_id, and creates the appropriate follow-up.
- 1 Create a new Zap with Webhooks by Zapier as the trigger. Select Catch Hook, continue, and copy the unique URL shown in the Test step.
- 2 In 7stamp Admin, open API & Integrations → Webhooks, add the Catch Hook URL, select only needed event types, and save.
- 3 Cause a real test scan or card event. Back in Zapier, click Test trigger and confirm event_type, external_id, and external_source arrive as sample fields.
- 4 Add a CRM Find Contact action using external_id. Add a Filter or Paths rule for event_type, for example separate SCAN from REWARD_EARNED.
- 5 Create a CRM note/task and map only fields that exist for that event, such as scanned_at, stamps_after, external_order_id, or issued_vouchers.
Check: A Catch Hook URL is a secret. If the Zap is transferred to another owner, update the URL in 7stamp Admin before relying on it.
Create the 7stamp API key before building the Zap
These are the 7stamp-side steps. Do this once, then use the key only inside the API by Zapier connection—not in a Webhooks by Zapier action field or a note.
Connection rules that prevent data mismatches
Keep the API key in an API by Zapier connection
In 7stamp Admin, choose API & Integrations → API Keys → Add API Key. In API by Zapier, create an API-key connection with a static Authorization header containing Bearer followed by that key. API by Zapier keeps the credential in the connection instead of a visible Zap step; restrict access to the connection and rotate the key if it is exposed.
Map External ID and External Source consistently
External ID is your own stable customer identifier; External Source labels where it came from, for example hubspot, bitrix24, shopify, or poster. Use the same pair for create, find, scan, voucher, and webhook flows.
Know which card identifier wins
Card-targeting actions accept User Card ID or External ID. When both are present, User Card ID takes priority. Use the internal ID only after it was returned by a trusted 7stamp step; otherwise prefer the source-system External ID.
Exact API by Zapier request: award one stamp
Copy this into your automation step
http Method: POST
URL: https://api.7loc.com/cards-api/cards/scan
Headers:
Authorization: Bearer YOUR_7STAMP_API_KEY
Content-Type: application/json
Data:
{
"external_id": "crm_contact_8821",
"external_source": "hubspot",
"stamps_count": 1,
"external_order_id": "order_2048"
}Build your first Zap
Create a 7stamp API key in Admin: API & Integrations → API Keys → Add API Key. Use a separate test key/profile when available.
In Zapier, create a Zap and test the source trigger. Use a real sample so the contact ID, customer ID, order ID, and amount are available for mapping.
Add API by Zapier → API Request. Create a 7stamp connection for the static Bearer Authorization header rather than putting the secret in a Webhooks by Zapier action field.
Call GET https://api.7loc.com/cards-api/templates first. This confirms the key works and shows which active template IDs are available without modifying customer data.
Select POST /cards/invite or POST /cards/scan, set JSON as the body type, and map the stable External ID plus the relevant template/order fields from the trigger.
Run the action with a disposable contact, inspect its exact response fields, then map those fields into the next CRM, email, or messaging step before publishing the Zap.
Use the universal request only for documented routes
Use API by Zapier for a 7stamp request with a Bearer API key: it keeps static header keys in an app connection. Use Webhooks by Zapier for Catch Hook event delivery, not as the preferred location for a 7stamp secret. Keep the base URL at https://api.7loc.com/cards-api, use the public OpenAPI reference for exact schemas, and never send credentials or customer data to an unverified URL.
Receive 7stamp events through Catch Hook
Create Webhooks by Zapier → Catch Hook, copy the unique URL shown in the test setup, paste it into the 7stamp profile's webhook settings, select the event types, and then send a real test scan or card event. Use the event payload's External ID and External Source to locate the right CRM contact. Choose Catch Raw Hook only when you specifically need the unparsed body and request headers.
Use the secure Zapier route now
API by Zapier and Catch Hook are sufficient for every public 7stamp API operation and card event. If you need a future native 7stamp Zapier app, send us the exact action/trigger your team uses most.
Frequently asked questions
Where can I find the 7stamp app in Zapier?
There is no public 7stamp marketplace app today. Use API by Zapier → API Request for 7stamp API calls and Webhooks by Zapier → Catch Hook for incoming 7stamp events.
Where do I create the Zapier token?
Create a 7stamp API key in Admin under API & Integrations → API Keys → Add API Key. Store it as a static Bearer Authorization header in the API by Zapier connection, not in a visible Webhooks by Zapier action field.
How can Zapier receive a stamp or voucher event?
Create a Catch Hook in Webhooks by Zapier, paste the generated URL into the 7stamp profile's webhook settings, select the events, and send a test event before enabling CRM updates.
Should I choose Zapier or Make?
Choose Zapier for a mostly linear trigger-action workflow. Choose Make when you need routers, complex transformations, or long multi-branch scenarios. Both use the same 7stamp API key and endpoints.
Next step
Build the first Zap with a test contact
Create the API key, test GET /templates through API by Zapier, then build one contact-to-card or order-to-stamps action. Add the Catch Hook once the outbound flow has a proven test result.