Easy Content Updates with Webhooks

Easy Content Updates with Webhooks

Discover how to use webhooks to keep your CRM, sales team, and other systems up to date with content alerts

Typically, it’s really difficult to know what content is being used – who on your team is sharing what and who out there in the world is engaging with it.

Storing your go-to-market assets in Google Drive, Sharepoint, and other file systems doesn’t do much to organize content let alone allow you to track it. But, with Content Camel, we’ve extended our ability to organize content, track engagement, and report on analytics with a series of integrations into your external systems.

With the introduction of webhooks, you can now send content alerts to your CRM, sales team, or other systems when content is created, updated, or engaged with.

webhooks for content alerts

Content alerts and webhooks

Webhooks are a technical, but super simple concept in practice. Basically, when an event happens in Content Camel, we can send a message to another system. It’s that straightforward. And the message that we send, can contain all the information you need to do something in that external system, like:

  • Create a new lead in your CRM when a prospect downloads a case study
  • Update a contact record when a salesperson shares a datasheet and the contact views the one-pager. Or update the opportunity in your CRM (like Salesforce or Hubspot)
  • Enroll a customer in a sequence when a new product asset is engaged with
  • Send a message to Slack new a new asset is added to the marketing content library

The benefit of webhooks are that you’re able to integrate them in the best way that makes sense for you and the organization. We’ve kept it open and flexible, so that we can learn more about your top needs and use-cases and craft even deeper experiences right out of the box. For now, you can take advantage of the following webhook events:

  • Asset created
  • Asset updated
  • Recipient engaged with asset or site

And all easy to set up in your account settings.

An example: Connecting Content Camel to a CRM (Pipedrive)

We have a really simple workflow for our webhook integration with our CRM. When one of the Content Camel sales team shares an asset or site with a prospect using personalized sharing, then that triggers the “recipient viewed” event. We use Zapier as our go between to connect that Content Camel notification event to Pipedrive, our CRM. So, that links our sales enablement content library with our opportunities in our CRM.

Here’s a quick rundown, and then some pictures and details of the setup:

  • The asset or site exists in Content Camel, our marketing and sales asset library
  • We have webhook notifications configured (easy!)
  • Sales rep sends out a personalized sharing link to a prospect
  • Prospect views the asset or site
  • Content Camel sends a webhook event. We have this connected to Zapier, but it could be your system of choice (or multiple systems!)
  • Zapier catches the event and sends the event to Pipedrive, our CRM
  • The Zapier -> Pipedrive integration updates the opportunity with the event details
  • We can then get a real time update in the Deal/Opportunity view in Pipedrive for what assets and sites are being engaged with based on shares to those contacts

Asset exists in Content Camel, the sales enablement content library

The starting point is having a single asset (pdf, deck, link - like one pager, case study, or intro presentation) in Content Camel. This is the asset that the sales rep will share with the prospect.

asset in Content Camel
Asset in Content Camel

The webhook is configured in Content Camel

This is easy – just pop in the URL of the system you want to send the event to. This is a one time configuration and not something that needs to be set up again and again.

webhook configuration
Webhook configuration

The user – typically a sales rep or marketer or customer success manager – shares the asset with a recipient

A personalized link for the recipient (typically a prospect or customer) is created. This is a unique link that is tracked by Content Camel.

sharing an asset
Sharing an asset

The recipient views the asset

When the recipient views the asset, Content Camel sends a webhook event. This is the event that we’re going to catch and send to Pipedrive.

recipient views the asset
Recipient views the asset

Zapier is set up to catch the webhook event and send it to Pipedrive

We use Zapier as our go-between to catch the webhook event and send it to Pipedrive. This is a simple setup in Zapier, and we’ll show you how to do it.

Zapier setup
Zapier setup

And it’s really simple. We catch the hook:

catch the hook
Catch the hook

and then we map the item shared to field to the email field in our CRM and look up the contact, the open deal, and then we update the deal in our CRM.

Oh, and finally, we send the notification to our team via Slack!

CRM is updated with the content event details

The result is that the CRM is updated with the content viewed event details. This is the view in Pipedrive, our CRM, where we can see the details of the asset that was shared and the recipient that viewed it.

Pipedrive CRM deal view
Pipedrive CRM deal view

What will you connect?

We’re excited to see what you’ll connect with webhooks and what you’ll do with these content notifications. We’ve made it easy to set up and easy to use. And we have more direct integrations to tools like Hubspot and Salesforce coming in this area, so definitely let us know what you’re looking to accomplish!

Ready to take advantage of content notifications?

Track engagement with Content Camel