What's in it for you
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. Through webhooks, you can build event-based and custom-built integrations for your organization. Events in Showpad trigger webhooks that can be used to perform actions in your integrations and other, custom middleware platforms.
A webhook contains information about the event that has occurred on the Showpad platform and sends it to another integration platform like Azuqua, Zapier, Mulesoft,... or a custom-built middleware. This middleware platform in its turn executes a programmed action. This can be logging share information to a CRM platform, adding custom objects to marketing automation platforms, and posting messages on an internal communication platform. These are only a few examples and the possibilities are endless. You are in the designer seat of creating that perfect automation process.
Key features
- Save time for sales and marketing teams by creating automated workflows
- Prevent sales and marketing from jumping between applications
- Provide a more complete sales and marketing infrastructure
- Automate actions and connect multiple integral platforms
- Execute predefined actions when events occur in Showpad
- Create webhooks for shared, viewed, reshared content, created Shared Spaces, user added to a Shared Space
You need this to succeed
- Ultimate subscription to Showpad
- Administrator access to Showpad's Online Platform
The quick way to awesomeness
- Sign in to Showpad's Online Platform
- Open the Admin Settings page of the Online Platform
- Find Webhooks in the Integrations section
- Select one of the 5 actions that apply to your automation:
- Sharing
- Visit of shared files
- Reshare
- Creation of a Shared Space
- User added to a Shared Space
- Add a webhook by clicking the + icon
- Select the HTTP method GET or POST, which defines how events are delivered to the webhook URL of the third-party platform
- Add the webhook URL and confirm
- Monitor the events by clicking the eye icon
- Standard HTTP response codes show you the event status.
Do this step by step
Using webhooks, there are 5 available events available you can use to create your automation:
- Sharing: when an email share is sent to a recipient
- Visit of shared files: when a recipient visits the page containing the shared files
- Reshare: when a recipient reshared the shared files with another person
- Creation of a Shared Space: when someone creates a Shared Space. If this webhook receives a 5XX response, it repeats the webhook request with a maximum of 3 retries.
- User added to a Shared Space: when a new user is added to a Shared Space. If this webhook receives a 5XX response, it repeats the webhook request with a maximum of 3 retries.
Let's see how it's done in detail:
- Sign in to Showpad's Online Platform
- Open the Admin Settings page of the Online Platform
- Find Webhooks in the Integrations section
- Select one of the 5 previously described actions that apply to your automation. Sharing, Visit of shared files, Reshare, creation of a Shared Space, user added to a Shared Space.
In this example, we use the Sharing option. - To see a sample of what we send to the other middleware platform, click Sample Body.
- Add a webhook by clicking the + icon.
- Select the HTTP method GET or POST, which defines how events are delivered to the URL of the other platform.
- Add the middleware URL that is used to accept webhook actions and confirm.
- The number of events is reflected in the # events column.
- Monitor the events by clicking the eye icon or delete the existing method.
- Map the action that needs to be executed in your middleware platform, using the identifiers in the sample body.
- Standard HTTP response codes show you the event status. We use the standard HTTP response codes to show that it was successfully received or not. (200 = OK.)
