Ask for a review after a purchase
When an order is placed, check the customer is eligible and email a review request, once per order.
What it does, step by step
- Read the order id, email, and total from the inbound order.
-
Decide whether this customer is eligible for a review request.
- yes goes to "Email the review request"
- no goes to "Skip"
- Send the customer a friendly review request.
- The customer is not eligible, so do nothing.
Build it just by talking to Claude
You do not wire this by hand. You describe it in a sentence, your Claude builds it, and Autoploy keeps it running.
What to build: Ask for a review after a purchase. When an order is placed, check the customer is eligible and email a review request, once per order. This is for founders and non-technical builders. How it behaves: 1. Runs when an order is placed and posts to the automation. 2. Read the order id, email, and total from the inbound order. 3. If eligible for a review request, then go to "Email the review request", otherwise go to "Skip". 4. Send the customer a friendly review request. 5. The customer is not eligible, so do nothing. The tools: - Resend (for "Which email service should send the review request?"). I will need you to create the key RESEND_API_KEY (Resend API key). I add the values in Autoploy myself; you only need their names. The platform: Connect to my Autoploy MCP server, call get_authoring_guide to read the authoring guide, and build the automation with the Autoploy SDK contract. Model every yes/no fork as a condition step with truthful labeled branches, keep every external side effect idempotent and keyed, and deploy it with deploy_automation. Before you build: Repeat the plan back to me in plain English and ask follow-up questions about anything unclear or ambiguous. Do not guess. Ask me for each key by name when it is time, and never ask me to paste a key anywhere except my own secure setup.
7-day free trial on every plan. You pick your plan at signup, and nothing is charged before day 7.