- Prerequisites
- Building an Integration
- Setting Up Authentication
- Setting Up Triggers & Actions
- Publishing Integration
- How To Authenticate Your Application Using The API Key Method
- How to Set-Up the Integration Based on Auth Type Bearer Token
- How To Authenticate Your Application Using OAuth 2.0
- How To Authenticate Your Application Using Basic Auth
- How To Authenticate Your Application Using The JWT Bearer Method
Webhook URL Update After Rebranding to OttoKit
As part of our recent rebranding, SureTriggers is now officially known as OttoKit. Along with this new identity, we’ve updated everything across the platform — including the logo, theme, colors, and most importantly, the webhook URLs.
This document explains what has changed with the webhook URLs and how it affects your existing workflows (spoiler: it doesn’t 😉).
What Has Changed?
With the rebranding to OttoKit, all URLs that previously contained suretriggers.com have now been updated to use ottokit.com instead.
This includes:
- Webhook URLs generated by the Core App Webhook
- Webhook URLs from manually created webhook-based workflows (e.g., Paddle, Gumroad, etc.)
- Register Webhooks (e.g., ActiveCampaign, SureCart, etc.)
These URLs are used when you want to trigger workflows in OttoKit from external applications.
What is a Webhook?
If you’re new to webhooks — a webhook is a special URL that you can plug into other apps to send data to OttoKit whenever something happens in that app. For example:
- A customer is created in Paddle
- A form is submitted in another platform
- A new record is created in a third-party tool
When that event occurs, the external app “calls” the webhook, and OttoKit immediately picks it up and runs your configured workflow.
Examples of Webhook URLs
Here’s a comparison of the old and new webhook URLs before and after rebranding:
Before Rebranding (SureTriggers):
- Core App Webhook:
https://webhook.suretriggers.com/suretriggers/3c11ed19-71a9-49c0-8616-552ddd9511b6 - Manual Webhook (e.g., Paddle):
https://webhook.suretriggers.com/paddle/04cd9f9b-415a-49da-8ce5-591ce9fce8dd
These URLs contained suretriggers.com — which was tied to the old brand.
After Rebranding (OttoKit):
- Core App Webhook:
https://webhook.ottokit.com/ottokit/3c11ed19-71a9-49c0-8616-552ddd9511b6 - Manual Webhook (e.g., Paddle):
https://webhook.ottokit.com/paddle/3c11ed19-71a9-49c0-8616-552ddd9511b6
Now, the webhook domain has been updated to reflect the new brand — just ottokit.com instead of suretriggers.com. That’s the only change. The structure of the webhook path and IDs remains exactly the same.
Will This Affect My Existing Workflows?
No, it will not affect them at all.
If you have already created workflows using the older webhook URLs (with suretriggers.com), they will continue to work without any problems. We’ve ensured full backward compatibility — which means:
- You don’t have to update anything immediately.
- Workflows using old webhook URLs will still receive data and run as expected.
Can I Update to the New Webhook URLs?
Yes, you can update them — but it’s completely optional.
If you want to keep your system consistent with the new OttoKit branding, you can update the webhook URLs in your third-party apps by simply replacing the domain part:
suretriggers.com → ottokit.com
For example:
https://webhook.suretriggers.com/suretriggers/…
becomes
https://webhook.ottokit.com/ottokit/…
That’s it! The webhook path and the unique ID remain unchanged, so the update is quick and straightforward.
Summary
- SureTriggers is now OttoKit
- Webhook URLs have changed from suretriggers.com to ottokit.com
- Old webhook URLs will continue to work
- You can update to new URLs if you prefer consistency
- No workflows will break due to this change
We hope this clears everything up! If you still have any questions, feel free to contact our support team.
We don't respond to the article feedback, we use it to improve our support content.