How it works
A webhook is a message Stripe sends when something changes, such as a payment or subscription. Connect those messages to a Zite workflow to update your business system even after the customer leaves your app. The workflow uses your connected Stripe account to check payment details. With Stripe webhooks, you can:- Update an order after a confirmed payment
- Keep subscription and renewal records current
- Adjust membership access after a subscription change
- Notify your team about a failed payment
- Send customer confirmations once payment is verified
How to integrate Stripe webhooks into your app
1
Connect to Stripe webhooks
Connect Stripe, then ask Zite to create a webhook workflow and show its URL. In Stripe, open Workbench → Webhooks and select Create an event destination.Choose events from Your account, select Webhook endpoint, and paste the Zite URL. Use the same test or live environment as your Zite connection.
2
Describe your use case
Tell Zite which events matter and what should happen. For example, “When a payment succeeds, check its details in Stripe, match it to the order, mark the order paid, and send one confirmation.”Ask Zite which event types to select in Stripe and to ignore unrelated or repeated notifications. Include any membership rules for renewals, failed payments, and cancellations.
3
Test and publish
Send a sample event in the matching test environment so Zite can check the received data. Publish the workflow while keeping Stripe in Test Mode, then make a test payment or subscription change and check Workflow Runs and the resulting records.Repeat a delivery to check for duplicate actions; a received sample alone doesn’t prove the workflow ran. Confirm the live connection and destination before accepting real payments.
Common use cases
With Stripe webhooks, you can create workflows like:- Order Confirmations: Mark verified purchases paid and notify the customer
- Membership Renewals: Update subscription records after renewal
- Cancellation Updates: Apply your access rules when a subscription ends
- Payment Follow-ups: Flag failed payments for the customer or your team
Important notes
- Private URL: Anyone with the Zite webhook URL can trigger the workflow. Keep it private; the standard setup has no Stripe signing-secret field.
- Verify before acting: Ask Zite to look up the payment or subscription through your Stripe connection and check it matches the intended customer, order, amount, and status before granting access or fulfilling an order.
- Repeat deliveries: Stripe can send the same notification more than once and can deliver events out of order. Ask Zite to prevent duplicate actions and check the current status in Stripe.
- Find your workflow: In the editor, open Workflows → Webhooks. Check that the trigger is active and Stripe has the current URL.
- Troubleshooting: Compare Stripe’s event deliveries with Zite’s run history. Share the failure and expected result with Zite; see the webhook guide for more help.
Need help with this integration? Contact support@zite.com.