Square events, straight into Slack
Every new payment, refund, or dispute — posted to Slack the moment it happens. No $20+/month automation plan just to move one webhook.
Why not just use Slack's built-in options? Even where Square offers some form of Slack integration, it's often tied to one account, limited in which events it covers, or more than you need. ZestyGlue is a dedicated, always-on feed of exactly the events you choose, for $9/month instead of a full automation-platform subscription.
What it looks like
ZestyGlue
Square — Payment.Created
42.50 USD
status: COMPLETED
A real Square event, shown as ZestyGlue formats it for Slack.
Setup — about two minutes
- Create the connector. In ZestyGlue, start a new Square → Slack connector. You'll get a unique webhook URL right away.
- Point Square at it. In the Square Developer Dashboard, go to your app → Webhooks → Add Endpoint, paste in your ZestyGlue webhook URL, and select the event types you want.
- Copy the Signature Key. Square shows a Signature Key for your webhook subscription — paste that into ZestyGlue's connector setup so every event can be verified as genuinely from Square.
- Point Slack at ZestyGlue. Create a Slack app (or reuse one) → Incoming Webhooks → Add New Webhook to Workspace, pick the channel, and copy the URL into ZestyGlue.
Under the hood: Square signs its webhook using both your endpoint's URL and the request body together — if you ever change your ZestyGlue connector's URL, update the endpoint URL in Square's dashboard to match, or verification will fail.
Events you can forward
payment.created
payment.updated
refund.created
dispute.created
Questions
Is my Square Webhook Signature Key safe with ZestyGlue?
It's encrypted at rest with Fernet symmetric encryption before it ever touches disk, it's never logged, and it's never displayed again in the dashboard after you enter it — only a masked placeholder is shown.
Does this work with Square's sandbox/test environment?
Yes — point a sandbox webhook subscription at the same connector while testing, then switch to your production Signature Key when you go live.
Can I track disputes separately from regular payments?
Yes — subscribe to dispute.created as its own event type alongside payment.created if you want disputes called out distinctly.
Does this need Slack admin approval?
No app installation is required on Slack's side — an Incoming Webhook is just a URL generated once. No OAuth review, no admin approval flow.
What happens if my ZestyGlue subscription lapses?
Events are silently dropped rather than causing errors on Square's side — Square never sees a failure response, so it won't retry aggressively or flag your webhook as broken. Your dashboard will simply stop showing new events until you resubscribe.