Introduction
Companies often rely on multiple platforms and integrations to establish a great marketing and sales process. Using Showpad to create the best buyer experience, it can be a timesaver to pass on specific information to your other marketing and sales platforms. Creating automated workflows saves time for sales and marketing teams by allowing them to stay in the same application. Showpad offers a way to automate specific actions related to sharing activity: webhooks.
TL;DR
- Subscribe to events? Use the Admin App or API to create webhook subscriptions
- Receive notifications? Showpad sends JSON payloads to your specified endpoint when events occur
- Verify requests? Use the signature key to validate incoming webhooks
When to use webhooks
| CRM Integration | Marketing Automation | Analytics & Reporting | Custom Workflows |
|---|---|---|---|
| Update deal stages when content is shared or viewed. | Trigger campaigns when prospects engage with Shared Spaces. | Track content engagement and course completions in real-time. | Build custom automations based on any supported event. |
Prerequisites
- Plan: Ultimate with Enterprise add-on | Advanced | Expert
- Permissions: Administrator access to Showpad's Admin App
- Authentication: Valid OAuth 2.0 access token (learn more)
What you'll learn
- How webhooks deliver real-time notifications when events occur in Showpad
- Which events are available for subscription (shares, views, Shared Spaces, course completions)
- How to manage subscriptions via the Admin App or API
- How Showpad handles retries for failed notifications
Events
Events are generated when a specific action happens in Showpad. The Payload Reference describes all of the events available for subscription in the Schemas section.
Retries
Showpad initiates a request to a specified endpoint and waits for a response:
| Response Code | Showpad Action | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| 2xx HTTP response code | The notification was successful. | ||||||||
| 4xx HTTP response code | The notification will be deemed unsuccessful, but no further attempts will be made. | ||||||||
| 5xx HTTP response code | The notification will be considered unsuccessful and a retry will be attempted. A maximum of three retries will be sent according to the following schedule:
|
Next steps
- Create webhook subscriptions via the Admin App or API
- Understand notification payloads and event data
- Verify webhook signatures to secure your endpoint
Was this page helpful?