How it works
- 1Connect your Clover account to ReviewNudger with a secure OAuth authorization — no API keys to copy and nothing to install at the register.
- 2When a payment is completed in Clover, ReviewNudger receives the event, resolves the customer attached to the order, and applies your sending rules. An eligible event can send one neutral Google review request by SMS or email.
- 3Clover only shares contact details when a customer is attached to the order, so walk-in payments without one are recorded and visibly skipped — nothing is guessed. Every send is tracked with delivery status, opt-outs, and review click-through.
Why a native connection beats middleware
The same four guarantees on every native integration — because they come from the platform, not the connector.
No middleware account or per-task fees
The connection runs directly between your account and ReviewNudger. There is no third-party automation account to maintain and no per-task metering on your review requests.
No manual field mapping
ReviewNudger already knows the provider's payload. Customer name, phone, and email resolve automatically — there are no field mappings to build or quietly break later.
Built-in duplicate protection
Every incoming event is deduplicated before any message goes out, so provider retries and replays can never double-text a customer.
Opt-out compliance handled
STOP replies and email unsubscribes are recorded per customer and honored automatically on every future trigger.
Set up the Clover integration
- 1Start a ReviewNudger trial and finish the short signup.
- 2Install the ReviewNudger app from the Clover App Market and approve the OAuth connection.
- 3Attach the customer to a real order in Clover and complete the payment to confirm the trigger end to end.
- 4Done. Eligible payments can now start one automatic review request under your sending rules.
Frequently asked questions
Do I need a Zapier account to connect Clover?
No. The Clover integration is native: you connect it directly inside ReviewNudger, with no middleware account, no per-task automation fees, and no field mapping to maintain.
What exactly triggers a review request?
Each time a payment is completed in Clover, ReviewNudger records the event and sends one review request to that customer by SMS or email, following your per-location send delay and cooldown settings.
Can a retry or duplicate webhook double-text a customer?
No. Every incoming event is deduplicated before any message is sent, and each event can create at most one review request. Provider retries and replays collapse onto the same request instead of sending twice.
What about customers who opt out?
SMS recipients can reply STOP at any time and email recipients can unsubscribe. Opt-outs are recorded per customer and honored across every future Clover-triggered event.
What about walk-in payments with no customer attached?
Clover only includes contact details when the customer is attached to the order, so a walk-in card tap with no customer is recorded and skipped — no review request is sent and no contact is guessed. Attach the customer to the order at checkout and ReviewNudger takes it from there.
Questions before you start? Email support@reviewnudger.com and a human will answer.