Integrations Error Message Guide

We know what you must be thinking: Oh no! I’m seeing an error with my configuration, what should I do?

Don’t panic! We can help you out. Take a look at the tables below that will outline what errors you might see, what they mean, and how we can fix them.

  

Marketo 

  • Clone program action is not selected: This means that you have not set up a trigger to tell Splash when to create a program in Marketo. If you don’t do this, the integration will not fire. To fix this, select a trigger for the action, "Clone Program". Pro Tip: You can select multiple triggers, if you'd like!
    Image_2020-03-18_at_10.07.20_AM.png

  • No base Program is selected: This means that you have not chosen a base program to act as a template for cloning your Marketo programs. To fix this, enter in your base program under the “Marketo Base Program” section of the configuration:
    Image_2020-03-18_at_10.04.34_AM.png

  • No program channel status mappings are set: This means that you have not mapped your Splash statuses to represent your Marketo program member statuses. To fix this, map the statuses that you want to sync over to Marketo under the "Program Channel Status Mapping" section.
    Image_2020-03-18_at_10.16.37_AM.png

  • No email address is mapped in the Lead field mappings: Since "email address" is a unique identifier in Splash, this information needs to be sent over to Marketo to differentiate your leads. To fix this, add "email" as a field under the "Lead Field Mapping" section:
    Image_2020-03-18_at_10.23.36_AM.png

  • Both batch and real time sync triggers are enabled in the same config: This particular message is more of a warning saying the configuration is sending information over to Marketo in two different ways (Real-time sync and Batch sync). Typically, you only need one method to send information over. With both Real-time and Batch selected, you might run the risk of maxing out on the number of API calls your team is permitted to make. The top row is the real time sync and the row below it is the batch push. To fix, unselect one of these fields, so that Splash is only relying on the other.
    Image_2020-03-18_at_10.25.26_AM.png

  • Please check authentication credentials. Unable to get Access token: This means that your integration is not authenticated properly. Please double-check to make sure your Munchkin Account ID, Client ID, and Client Secret are correct.

  • Required authentication credentials are missing: This means that you're missing one of the three fields needed to authenticate your configuration (i.e. Munchkin Account ID, Client ID, and Client Secret). Please make sure that all three of these fields are filled in with accurate information.

  • No program name template is set with valid dynamic tags in place: This means that your program naming convention field is empty. To fix this, define your desired program naming convention in this field. Pro Tip: Use the "View Dynamic tags" hyperlinked text to see a list of unique data that we can pull directly from the event you're creating!
    Image_2020-03-18_at_10.37.53_AM.png

 

 

Bluejeans

  • Whoops! We're having trouble sending requests to Bluejeans: This message displays if an error occurs when transmitting data to BlueJeans as a result of a BlueJeans issue. Try to re-save the configuration. If you get stuck, reach out to the Splash Support team, and we'll give you a hand!

  • The Client Secret provided above is not valid: This means that the Client Secret you entered into Splash is incorrect. Please check that it's copied correctly from Bluejeans settings: Admin > Events > OAuth access > APP secret.

  • The Client ID provided is not valid: This means that the Client ID you entered into Splash is incorrect. Please check that it's copied correctly from Bluejeans settings: Admin > Events > Oauth access > App Key.

  • The current user's email does not exist in this BlueJeans account. Please check the account in your Enterprise: This means that the email address that you're using to authenticate the configuration is not a valid Bluejeans user. Please create a Bluejeans account for this email address, or use a different email address that is connected to a valid Bluejeans account. 

 

  

Eloqua

  • The credentials provided for the Eloqua authorization are invalid: This means that the configuration is not authenticated correctly. Please re-authenticate the integration using the Re-Auth from the top right of this configuration.
    Screen_Recording_2020-03-18_at_10.45_AM.gif

  • Invalid access token: This means that the access token used to authenticate the configuration is invalid. Please re-authenticate the integration using the Re-Auth from the top right of this config.
    Screen_Recording_2020-03-18_at_10.45_AM.gif

  • Could not fetch remote fields: This means that Splash cannot find your Bluejeans fields. Please re-authenticate the integration using the Re-Auth from the top right of this config.
    Screen_Recording_2020-03-18_at_10.45_AM.gif

 

 

  

Greenhouse

  • The API key provided is valid, but does not have sufficient permissions set in Greenhouse. This means that the Harvest API key does not have the correct permissions in Greenhouse to sync data between Splash <> Greenhouse. Please see the Harvest API Credential Permissions page in the Greenhouse Dev Center, and enable. For a detailed list of which permissions are required, check out our Greenhouse Integration Guide.
    Image_2020-03-18_at_11.55.57_AM.png

  • Whoops! We're having trouble sending requests to Greenhouse: This message displays if an error occurs when transmitting data to Greenhouse as a result of a Greenhouse issue. Try to re-save the configuration. If you get stuck, reach out to the Splash Support team, and we'll give you a hand!

  • The API key provided above is unauthorized to make changes in Greenhouse. This means that the Harvest API key does not have the correct permissions in Greenhouse to sync data between Splash <> Greenhouse. Please check that it's copied correctly from the Harvest API Credentials page in the Greenhouse Dev Center. For a detailed list of which permissions are required, check out our Greenhouse Integration Guide.
    Image_2020-03-18_at_11.55.57_AM.png

  • The Greenhouse user for that email doesn't seem to exist: This means that the email address that you're using to authenticate the configuration is not a valid Greenhouse user. To fix this, try a different email address. If you get stuck, reach out to the Splash Support team, and we'll take a look!
    Image_2020-03-18_at_10.52.46_AM.png

  • Please enter the email address of the Greenhouse user to act on behalf of when adding prospects and candidates via the API: This means you have not yet selected a user from the "User" to add prospects and candidates via the API. Please select a user to utilize the integration.
    Image_2020-03-18_at_10.52.46_AM.png

 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.