Client fields
- No external credential is required.
Values are saved per business and masked after save. QRScanInk system services are handled internally and are not required for client setup.
Help center
Clover POS setup
Prepare restaurant QR service and order-intent handoffs for Clover POS workflows while keeping request-only mode available.
Where to test
Open the dashboard Integration Setup Center. Use the test or sample-event button to confirm the client-owned connection before enabling a workflow.
1. Add client credentials
Fill only the fields listed above. Missing optional external tools do not block core QR publishing.
2. Run a sample event
The sample endpoint checks URL safety where applicable and records redacted delivery logs for troubleshooting.
3. Launch safely
Use scoped API/MCP tokens, signed webhooks, export caps, rate limits, and audit logs for client work.
Related help
Webhooks
Send signed scan, lead, conversion, report, alert, and product passport events to any public HTTPS endpoint.
Zapier via webhooks
Use Zapier Catch Hook triggers with QRScanInk signed webhook payloads.
Make via webhooks
Trigger Make scenarios for leads, scans, reports, alerts, and client automations.
Slack alerts
Post milestone alerts, suspicious spike alerts, low-performing QR notices, and failed delivery messages to Slack.
Google Sheets exports
Sync leads, scans, report rows, and product passport activity to client-owned spreadsheets.
GA4 and Google Tag Manager
Add analytics tags to QRScanInk destinations so post-scan behavior connects to client reporting.