Managing data feels like being the conductor of an orchestra at times. There's a lot of noise that needs to work together to tell a story. Splash helps make sure you're always in sync.

This article explores how to integrate your internal systems with Splash to connect your event data and automate your team's workflow.

Available Splash integrations

Each Splash integration is completely configurable, allowing for optimal functionality within the connected system. 

We offer the following native integrations:

• Eloqua Campaigns
• Eloqua Contacts
• Eloqua Custom Objects
• Greenhouse Candidates and Prospects
• Guidebook
• HTTP Request
• HubSpot Contacts
• HubSpot Timeline
• Incoming Webhook
• Marketo
• ON24 Webinars
• Salesforce AppExchange
• Salesforce Pardot Campaigns
• Salesforce Pardot Form Handler
• Salesforce Pardot Prospects
• Salesforce Sales Cloud
• Slack
• Zapier
• Zoom Webinars

While our native integrations offer the ability to connect with leading sales CRMs, marketing automation platforms, and applicant tracking systems, we also offer the ability to create custom integrations for any of your preferred systems. 

Creating a custom integration

Not seeing your preferred system listed above? Set up a custom integration through one of the following options:

• HTTP Request
• Incoming Webhook

Each of these options provides a different value, so which one you choose is entirely dependent on what you're looking to accomplish. We'll go through these integrations in more detail below to help you find what you're looking for. 

HTTP Request

Our HTTP Request integration is our go-to solution when you need to push Splash data into another system that isn't one of our native integrations. This versatile integration only requires an endpoint, meaning it could be used for any specific platform your team uses for data processing. Since the HTTP Request is only a one-way data flow for pushing information from Splash into another system, it doesn't offer bi-directional functionality. That said, this option will require some developer resources to implement.

Here's how we've seen HTTP Request used:

• Pushing data into external CRMs (ex: Microsoft Dynamics 365)
• Sending data to a data lake (raw data storage center) or data warehouse like RedShift or Heap
• Sharing registration data for virtual event platforms across tools
  

Incoming Webhook

The Incoming Webhook integration can only be customized to anonymize, unsubscribe, or resubscribe guests in Splash. This option requires some technical resources - specifically someone with access to make API calls.

Using a connected application 

Many applications develop and maintain a connection to Splash, allowing users to take advantage of Splash events and registration information. In these instances, setup and configuration is done directly in these systems and will be managed outside of Splash. 

Below are some examples of these applications. Note: not every connected application may be listed. 

• Boomset
• Pathable
• Zapier

If you need to connect Splash to numerous systems, tools, and platforms (ex: Gmail, Google Docs, Excel, MailChimp, Facebook, etc.), we recommend using Zapier. Since Zapier does all the heavy lifting for you, this connected application is helpful if you have little to no developer resources available.

Here's how we've seen Zapier used:

• Sending messages about RSVP updates to Microsoft Teams
  
• Posting guest registration data to Google Sheets
• Sending emails from MailChimp

Not sure which of our solutions is best for you? Reach out to our team and we'll be happy to point you in the right direction.