Handle Stripe webhooks without running a server
Tell your assistant what should happen when Stripe sends an event. ClickRuntime gives you the endpoint URL, verifies the Stripe-Signature header, ignores repeat deliveries and runs your code.
- When
- Each incoming event
- Uses
- Stripe, Slack
- 16:20✓ Stripe checkouts → #sales · SucceededLast run16:20 · $490 posted
Can Claude or ChatGPT handle Stripe webhooks?
Not directly: Stripe sends webhooks to an HTTPS endpoint that must answer every time, and an assistant isn't a server. With ClickRuntime connected, Claude, ChatGPT or another assistant creates an automation with a trigger link you add in Stripe as the endpoint. ClickRuntime checks the Stripe-Signature header, drops repeat deliveries, and runs the script for each event.
Why the assistant can’t do this on its own
- Stripe needs an endpoint that's always up. A chat is only active while you type.
- Signatures must be checked against your endpoint secret, which has to be stored somewhere safe, not pasted into a conversation.
- Stripe retries deliveries, so you need memory of which events were already handled. ClickRuntime gives each automation state and a stable event id.
Set it up from your AI assistant
The same steps work in ChatGPT, Claude, Cursor and any assistant that supports MCP connectors.
- Step 1Connect ClickRuntime to your assistantAdd ClickRuntime as a connector (MCP server) in ChatGPT, Claude, Cursor or another MCP client, using https://clickruntime.com/api/mcp. You sign in with Google or email; there is no API key to copy. This is done once per assistant.
- Step 2Paste the promptStart a new chat and paste: “Create a ClickRuntime automation: when Stripe sends checkout.session.completed, post the customer email and amount to #sales in Slack. Check the Stripe signature and handle each event only once.” Change the details (times, channels, addresses) to yours.
- Step 3Read the draftThe assistant restates what will happen, asks for anything missing, such as your timezone or which channel to post to, and saves a draft automation. A draft never runs on its own, so nothing happens until you agree.
- Step 4Connect accounts and save keysThe assistant gives you the trigger link. In Stripe, go to Developers → Webhooks, add it as an endpoint for checkout.session.completed, and copy the signing secret. Save it in the ClickRuntime dashboard in the trigger link's signature settings (provider Stripe), or as STRIPE_WEBHOOK_SECRET. It also asks you to connect Slack for notifications and pick the channel.
- Step 5Test itSend a test event from Stripe's webhook page, or use `stripe trigger checkout.session.completed` with the Stripe CLI. The assistant looks at the stored event, confirms the signature passed, and checks the Slack message.
- Step 6Turn it onThe assistant tells you what will run, when, and which services it will contact, then asks your permission to turn it on. From then on it runs on ClickRuntime's servers, and you can close the chat.
- Step 7Check it in the ClickRuntime dashboardEvery delivery shows as an incoming event with whether the Stripe signature passed, the run it started and its result. If your code had a bug, fix it with your assistant and replay the stored events. Stripe doesn't have to resend anything.
“Create a ClickRuntime automation: when Stripe sends checkout.session.completed, post the customer email and amount to #sales in Slack. Check the Stripe signature and handle each event only once.”
Connector setup for each assistant: ChatGPT, Claude, Claude Code, Cursor, and other assistants.
What the assistant writes
A typical script for this job. Yours matches your pages, accounts and wording, and you can read every version in the ClickRuntime dashboard.
- `verify.stripe` checks the signature against the raw body with a 5-minute tolerance. Turning on Stripe signature checks for the trigger link does the same before the script runs.
- Stripe's event id is stored after handling, so retries and replays don't post twice.
- Only fields Stripe actually sends in checkout.session.completed are used; the assistant checks them against a stored test event.
Trigger link, not a schedule
Use the trigger link. Stripe pushes events as they happen, and each event is one run.
Use a schedule only for summaries, such as a daily revenue total from Stripe's API. That can be the same automation's @on_trigger handler.
Limits
- Each delivered event is one run, so subscribe the endpoint only to the event types you use.
- Runs have a time limit; long work such as generating reports should run on a schedule instead.
- Stripe expects a quick 2xx response. ClickRuntime accepts the event and stores it, so a failed run can be replayed later.
Troubleshooting
Every event fails the signature check.
The secret is from a different endpoint or from test mode. Each Stripe endpoint has its own signing secret; copy the one for this endpoint and save it again.
Stripe shows failed deliveries.
Check the endpoint URL is the trigger link exactly, with nothing added. The event list in the ClickRuntime dashboard shows whether anything arrived.
Some payments are missing in Slack.
The endpoint may not be subscribed to that event type, or test and live mode are mixed. Ask your assistant to list recent incoming events and compare.
What you can add next
The first version is rarely the last. Because the automation is a Python script with memory, AI and any API available, you grow it by asking your assistant for the change. Each change is a new version, and a failed deploy never replaces the working one.
- Any app or API
Log each payment as a row in a Google Sheet
“Add to my Stripe checkouts automation: also add a row to my Payments sheet with date, email, amount and currency.”
- Multi-step logic
Handle refunds and failed payments in the same automation
“Change my Stripe checkouts automation so it also handles charge.refunded and invoice.payment_failed, posting each to #billing with the reason.”
- Memory between runs
Keep a running monthly revenue total and include it in each post
“Change my Stripe checkouts automation so each Slack post also says the total for this month so far.”
- Schedules
A daily revenue summary at 18:00
“Add to my Stripe checkouts automation: every day at 18:00, post the day's total and number of payments to #sales.”
- Built-in AI
Summarise refund reasons into themes each week
“Add to my Stripe checkouts automation: every Friday, email me a short summary of this week's refund reasons grouped by theme.”
- Any app or API
Tag the customer in HubSpot when they pay
“Add to my Stripe checkouts automation: when a checkout completes, set the HubSpot contact with that email to customer.”
- Trigger links
Accept Shopify orders through a second trigger link into the same channel
“Create a second automation like my Stripe checkouts one for Shopify orders/create, posting to the same #sales channel.”
Questions about handle stripe webhooks
Can Claude handle Stripe webhooks?
Yes, with ClickRuntime. Claude writes the handler and ClickRuntime gives you an always-on endpoint that checks the Stripe signature and runs it for each event.
Do I need a server for Stripe webhooks?
No. The automation's trigger link is the endpoint. ClickRuntime receives the event, stores it and runs your script.
How is the signature checked?
With Stripe's signing secret, either by the trigger link before the script runs or in the script with verify.stripe, against the raw body.
What if Stripe sends the same event twice?
The platform deduplicates deliveries, and the script also stores the Stripe event id so a retry or replay is skipped.
Can I replay an event after fixing a bug?
Yes. Stored events can be replayed from the ClickRuntime dashboard or by asking your assistant.
What does it cost?
One run per event. The free plan includes 250 runs a month with webhooks included.
Other use cases
Scheduled tasks in ChatGPT and Claude
“Create a ClickRuntime automation: every weekday at 9, fetch yesterday's orders from our Shopify store and post the total to #sales in Slack.”
See the use case →Run code every hour
“Create a ClickRuntime automation: every hour, check our public API's /health endpoint and Slack #alerts if it returns anything but 200.”
See the use case →Webhook automation
“Create a ClickRuntime automation: when someone submits our Typeform, add their answers to a message in #leads.”
See the use case →Cron jobs without a server
“Create a ClickRuntime automation: every night at 2am UTC, call POST https://api.example.com/tasks/reindex with my ADMIN_TOKEN and email me if it doesn't return 200.”
See the use case →AI agent automations
“Create a ClickRuntime automation: every morning at 8, summarize new GitHub issues labelled 'bug' on our repo and post them to #eng.”
See the use case →Monitoring and alerts
“Create a ClickRuntime automation: every 5 minutes, check https://api.example.com/health and Slack #oncall if it fails twice in a row.”
See the use case →Stateful automations
“Create a ClickRuntime automation: every hour, check this product page and email me only when the price drops below the lowest price you've seen.”
See the use case →AI triage and summaries
“Create a ClickRuntime automation: every 15 minutes, label new support emails as billing, bug or other and post billing ones to #billing.”
See the use case →Website change alerts
“Create a ClickRuntime automation: every hour, check https://acme.com/pricing. Only look at the pricing table, not the whole page. When it changes, email me a short summary of what changed. Don't email me when nothing changed.”
See the use case →Price drop alerts
“Create a ClickRuntime automation: every 2 hours, check the price on https://shop.example.com/products/monitor-27. Email me when it drops below $280. Tell me only once per drop, and include the lowest price seen so far.”
See the use case →Uptime checks
“Create a ClickRuntime automation: every 5 minutes, check https://app.example.com/health. It's down if the status isn't 200, it takes longer than 5 seconds, or the body doesn't contain "ok". After 2 failures in a row post to #ops in Slack, and post again when it's back up with how long it was down.”
See the use case →RSS feed alerts
“Create a ClickRuntime automation: every 30 minutes, check https://www.postgresql.org/news.rss. Post each new item to #eng in Slack with its title, link and a one-line summary. Never post the same item twice. On the first run, don't post old items.”
See the use case →Job post alerts
“Create a ClickRuntime automation: every 2 hours, check the Greenhouse job boards for the companies acme and betaco. Email me new jobs that are product design roles open to remote work in Europe. Include title, location and link. Never send the same job twice.”
See the use case →Brand mention alerts
“Create a ClickRuntime automation: every 30 minutes, search Reddit and Hacker News for "Acme CRM". Post each new mention to #mentions in Slack with the title, link and a label: question, complaint, praise or other. Never post the same thread twice.”
See the use case →Daily Slack message
“Create a ClickRuntime automation: every weekday at 9:00 Europe/Berlin, post to #team in Slack: a good-morning line, the number of open issues labelled Bug in our Linear team ENG, and the 3 oldest ones with links.”
See the use case →Daily news digest
“Create a ClickRuntime automation: every day at 7:30 Europe/London, collect new items from these feeds: <feed URLs>. Pick the 5 most important for someone following AI policy in the EU, and email me a digest with a two-sentence summary and link for each. Don't include anything I was sent before.”
See the use case →Weekly metrics to Google Sheets
“Create a ClickRuntime automation: every Monday at 7:00 America/New_York, add a row to the KPIs tab of my sheet “Company metrics” with the week start date, last week's Stripe revenue (succeeded charges minus refunds), number of new customers and number of refunds.”
See the use case →Morning briefing
“Create a ClickRuntime automation: every weekday at 7:00 Europe/Lisbon, read today's events from my work Google Calendar, get today's forecast for Lisbon, and email me a short briefing: the weather in one line, each meeting with time and who's in it, what I should prepare, and my free blocks of 30 minutes or more.”
See the use case →Slack channel summary
“Create a ClickRuntime automation: every weekday at 17:30 America/Chicago, read today's messages and thread replies in #product, and post to #product-digest a summary with three parts: decisions made, open questions, and action items with who owns them.”
See the use case →Inbox summary each morning
“Create a ClickRuntime automation: every weekday at 7:30 America/Los_Angeles, read the emails that arrived in my Gmail inbox since the last summary. Email me a summary in three groups: needs a reply, FYI, and newsletters or notifications. One line per email with the sender. Skip anything I already read.”
See the use case →Form submissions to Google Sheets
“Create a ClickRuntime automation: when someone submits my Typeform contact form, add a row to the Leads tab of my Leads spreadsheet with the date, name, email, company and message. Check the Typeform signature so only real submissions are added.”
See the use case →Form leads to your CRM
“Create a ClickRuntime automation: when my website form posts a lead (name, email, company, message), create or update the contact in HubSpot by email, set lifecycle stage to lead, and add the message as a note on the contact.”
See the use case →React to GitHub events
“Create a ClickRuntime automation: when a new issue is opened in acme/app, read the title and body and add one label: bug, feature or question. Check GitHub's webhook signature.”
See the use case →Sort Gmail automatically
“Create a ClickRuntime automation: every 15 minutes, look at new messages in my Gmail inbox and add one label: Invoice, Customer, Newsletter or Needs reply. Email me straight away when a customer message sounds urgent.”
See the use case →Recurring reminders
“Create a ClickRuntime automation: on the last weekday of every month at 10:00 London time, post “Reminder: send this month's invoices” to #finance in Slack.”
See the use case →Stale pull request reminders
“Create a ClickRuntime automation: every weekday at 9:30 Berlin time, find pull requests in acme/app and acme/api that are not drafts, have been open more than 24 hours and have no review yet. Post them to #eng in Slack with the title, age, author and requested reviewers. Post nothing if there are none.”
See the use case →Scheduled social posts
“Create a ClickRuntime automation: every 15 minutes, read my Post queue sheet (columns: When, Text, Status). Publish each row whose When has passed and whose Status is empty to my LinkedIn profile, then set Status to the post link.”
See the use case →Sync data between apps
“Create a ClickRuntime automation: every 30 minutes, find records in my Airtable Customers table that changed since the last run, and create or update the HubSpot contact with the same email, copying name, company and plan.”
See the use case →Summarise customer feedback
“Create a ClickRuntime automation: every Monday at 9:00, read the rows added to my Feedback sheet since last time (columns: Date, Source, Text), group them into up to 6 themes with a count and one short quote each, and post it to #product in Slack.”
See the use case →Daily standup in Slack
“Create a ClickRuntime automation for our async standup: every weekday at 9:30 Berlin time, post “Standup: what did you do yesterday, what's next, anything blocking?” in #team. At 12:00, read the replies in that thread and post a short summary in the thread, listing blockers first and who hasn't replied.”
See the use case →
Set up your first automation in ChatGPT or Claude
Free plan. No credit card.