Log Stripe payments to a Google Sheet
When a Stripe payment succeeds, add a row to your Google Sheet and send a Telegram receipt, once per payment.
What it does, step by step
- Read the Stripe event and its amount.
-
Decide whether the Stripe payment actually succeeded.
- yes goes to "Append a Sheet row"
- no goes to "Skip"
- Add the payment as a new row in the Google Sheet.
- Send a short receipt for the payment on Telegram.
- The payment did not succeed, 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: Log payments to a spreadsheet or database. When a payment succeeds, add a row to a spreadsheet or database and send a receipt to your team chat, once per payment. This is for engineers and non-technical builders alike. How it behaves: 1. Runs when Stripe posts a payment event to the automation. 2. Read the Stripe event and its amount. 3. If did the payment succeed, then go to "Append a Sheet row", otherwise go to "Skip". 4. Add the payment as a new row in the Google Sheet. 5. Send a short receipt for the payment on Telegram. 6. The payment did not succeed, so do nothing. The tools: - Stripe (for "Where do your payments come from?"). I will need you to create the key STRIPE_WEBHOOK_SECRET (Stripe signing secret). I add the values in Autoploy myself; you only need their names. - Google Sheets (for "Where should each payment be recorded?"). I will need you to create the key GOOGLE_SHEETS_TOKEN (Google Sheets access token), provide the setting GOOGLE_SHEETS_SPREADSHEET_ID (Google Sheets spreadsheet id). I add the values in Autoploy myself; you only need their names. - Telegram (for "Where should the receipt be sent?"). I will need you to create the key TELEGRAM_BOT_TOKEN (Telegram bot token), provide the setting TELEGRAM_CHAT_ID (Telegram chat id). 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.