Connections

Orders, failed payments and form submissions, sent by the service they happen in. No code.

A connection lets a service tell Snekot when something happens in it. You paste one address into the service, and what it sends becomes events: in the feed, in charts, and on your phone.

Service What arrives
Stripe Orders, subscriptions, renewals, failed payments, refunds, disputes
Paddle Orders, subscriptions, renewals, failed payments, refunds
Polar Orders, subscriptions, renewals, failed payments, refunds
WooCommerce Paid orders, refunds, failed orders, new customers
Gumroad Sales and renewals
Tally Form submissions
Typeform Form submissions

Connecting a service

  1. In the app open Setup, Connections, Connect a service, choose the service and press Get its address. The address is shown only then, so keep that open.
  2. Paste the address into the service as its webhook address. Where to find that is below.
  3. Most services then show a signing secret. Copy it into the field under the address and save. If you closed it first, choose Add secret on the connection.

Every request is checked against that secret, so nobody else can post as the service. Stripe, Paddle, Polar and WooCommerce always sign, and nothing from them is accepted until the secret is saved. For Gumroad, Tally and Typeform signing is optional; turn it on if you can. Once a secret is saved, a request without a matching signature is refused.

Service Where the address goes The secret
Stripe Developers, Webhooks, Add destination. Choose snapshot events, not thin ones The destination’s signing secret, whsec_…
Paddle Developer tools, Notifications, New destination The destination’s secret key, pdl_ntfset_…
Polar Settings, Webhooks, Add endpoint, format Raw The secret you set or generate there
WooCommerce Settings, Advanced, Webhooks. Add three webhooks with the same address, one for each topic: Order created, Order updated, Customer created One secret, typed into all three
Gumroad Settings, Advanced, Ping endpoint The signing secret for pings, if you turn signing on
Tally The form, Integrations, Webhooks The signing secret, if you set one
Typeform The form, Connect, Webhooks The secret, if you set one

For Stripe, these events are the ones to send: checkout.session.completed, checkout.session.async_payment_succeeded, checkout.session.async_payment_failed, invoice.paid, invoice.payment_failed, customer.subscription.created, customer.subscription.deleted, charge.refunded and charge.dispute.created. Others are answered and ignored.

WooCommerce sends an order every time it changes, and each topic gives something different. Order created and Order updated together give paid orders, whenever the payment lands; Order updated also gives refunds and failed orders; Customer created gives new customers. An order is counted when WooCommerce marks it paid, not when it is placed: one waiting for a bank transfer, or pending at the payment provider, becomes an event when the money is in, and a cash-on-delivery order when you complete it. Shipping an order later, or editing it, is not a second sale.

Gumroad’s Ping endpoint sends sales and the later charges of a membership. It signs them with X-Gumroad-Signature when signing is on. Refunds, cancellations and disputes are sent only to an address subscribed to them through Gumroad’s API (a “resource subscription”), and Gumroad does not sign those. Snekot reads them if they arrive, but a connection with a secret saved refuses them, so use a second connection without a secret for them. Amounts from Gumroad are in US dollars whatever currency the product is listed in, because that is what Gumroad sends.

What the events look like

Payments from every service take the same names, in the payments channel, so one chart covers them all:

Event When
Order paid A one-time payment, or the first payment of a subscription (tagged kind: one-time or subscription)
Subscription started A subscription was created, paid or on trial
Subscription renewed A later payment of a subscription
Subscription cancelled A subscription ended
Payment failed A charge or renewal did not go through
Refund Money was returned
Dispute opened A customer’s bank questioned a charge

A new WooCommerce customer is Customer signed up in the signups channel. Form submissions are Form submitted in the forms channel.

Each payment carries tags: amount, currency, source, and product where the service names one. A chart of Order paid by the tag source shows where your sales come from.

What is not kept

No names, email addresses, postal addresses or card details, and no form answers. An event’s person is the service’s own id for the customer, such as Stripe’s cus_…, so a customer’s events line up without Snekot knowing who they are.

Good to know

  • One happening, one event. A single sale makes a service send several messages; one of them is counted and the rest are ignored. The first payment of a subscription is an order, not also a renewal.
  • One sale, one notification. Selling a subscription records two things, the payment (Order paid) and the subscription (Subscription started), so you can chart both. Only the payment notifies your phone. A subscription that starts as a trial has no payment, so there the start is what notifies.
  • Partial refunds. A refund’s amount is what was returned that time. When a Stripe charge has been refunded more than once, refunded_so_far carries the running total.
  • Sent twice, counted once. Services repeat a message when they are unsure it arrived. A repeat is recognised for four days.
  • Test mode. Events from Stripe’s test mode, and Gumroad’s test pings, are recorded with the tag test, so you can try a connection before real money moves. They never notify your phone. They do count against your month’s events like any other, so leave a test-mode webhook switched off when you are done trying.
  • Your allowance. Events from connections count against the month like any other. Past the limit they are held like any other, and at twice it they are refused and the connection says so. See Limits.
  • A wrong address. A request to an address that is not a connection is refused, and a sender that keeps trying wrong addresses is turned away for a minute.
  • Pausing and removing. A paused connection answers the service and records nothing. Removing one makes its address stop working at once.
  • A service that is not listed can still post through Zapier, Make or n8n.