Live API only. Purchases spend real balance.
No keys are included. Purchases require explicit confirmation. Never automatically create a replacement order after a timeout.
Download sim7-purchase-and-sms.json ↓1. Import the workflow and select credentials
Download the JSON and use Import from File in n8n. The workflow is inactive and starts manually. No tokens, private credential names or customer data are exported. Create a live Sim7 key with orders:read and orders:write; separate catalog checks require catalog:read.
Create a Generic Header Auth credential: header name Authorization, value Bearer followed by your private key. Select the same credential in both HTTP Request nodes. Never paste secrets into Code nodes, URLs or plain configuration fields. Review exported workflows before sharing them.
2. Configure the business order, not an execution ID
In Your business order set business_id from your system, its immutable created_at ISO UTC timestamp, service, country, operator and max_price in USD. Copy route IDs from /api/v1/prices rather than translated country names. max_price is a ceiling, not a promised purchase price.
Do not use $execution.id, a fresh random UUID or a new timestamp as the purchase identity on retries. Keep the original ID, request fields, creation date and credentials. The guard rejects intents older than six days before the API's seven-day replay boundary; never refresh the date to bypass this guard.
This is a controlled onboarding template. Unattended resale requires your own persistent database mapping customer orders, original inputs, key identity and Sim7 order_id. The workflow is not that database. Do not rotate the key for an unresolved purchase; reconcile the original operation first.
3. Confirm the purchase and observe messages
Enable confirm_live_purchase only after checking the input. This spends real balance. Idempotency-Key is tied to business_id and no automatic replacement order is created after an error. Timeout, 409, 429 or 5xx stops execution: retain the input, respect Retry-After and retry only the original intent.
The order is read every five seconds. target_messages=1 returns the first SMS without calling finish. For a second message request another SMS in the target service and rerun the same business_id with target_messages=2. Keep purchase fields unchanged. Further messages require an active order and number; the workflow cannot extend their lifetime.
Observation stops at the requested message count, a terminal status or the local twenty-minute deadline. That deadline does not cancel the order or issue a refund. The result includes a stop reason and current order. Finishing or cancelling requires a separate explicit operation.
Webhooks and n8n security
This JSON uses polling. Never connect an unverified public Webhook node directly to fulfillment or financial actions. For push events use the Python or Node.js receiver linked here: it verifies raw-body signatures, timestamps and delivery identity, then persists the event before returning 200. Your worker can forward verified events to an authenticated n8n workflow.
Saving successful, failed and manual executions is disabled. Wait and n8n infrastructure may still retain intermediate state: restrict editor access, protect storage and set retention. Credentials protect secrets, but phone numbers and SMS are sensitive too. Never forward them to public chats or expose another customer's order.
Only built-in nodes are required. No community nodes or unrestricted environment access from Code are needed. If your n8n installation rejects a node version, update a compatible installation and test the import with purchase confirmation still disabled. Do not remove signature verification as a shortcut.

