Skip to main content

This is my last effort before looking for an alternative to Zapier.

We have an issue where occasionally the State will not be populated to Salesforce even though it’s included in the incoming data. 

 

I know the field is mapped correctly because it works 95% of the time.

 

The Zap works like this.

  1. A Hubspot Form is created
  2. The email is used to search for an existing contact in Salesforce. If there is no match a new contact record is created using the form submission fields, including the state.
  3. A new record related to the contact, called inquiries, is then created with form specific details, like comments but it also includes the address information.

In these few cases, the State is populated on the form and does populate in the Inquiries record but not the Salesforce contact record. It then requires the person processing leads to check the inquiries and populate the state from the inquiry record which is not a feasible solution.

 

Side note - I’ve submitted three tickets to Zapier since 8/19 to address this issue and received to response. I’ve checked both the Junk and Spam filters. I’m hoping that someone in the community can shed some light on this issue.

 

CSU-00094

Hi @Heather Y 

Perhaps you can post screenshots of how your Zap steps are configured along with examples of where the Zap works and does not work.

Make sure to check your Zap Runs history details for the DATA IN/OUT for each step to help troubleshoot the issue: https://zapier.com/app/history/

Thanks Troy,

I have checked the run history for these outliers and the successful completions and can not determine where there are any differentiators.

The images below are low res. I put them in a google folder

https://drive.google.com/drive/folders/1HIAUmFvyiVZrzrFO7uGX7BLqjeYhUe-N?usp=sharing

 

Here is a screenshot of the run history where the state doesn’t populate.

 Here is the same form where the State does populate correctly

 

Hi @Heather Y 

Article: https://zapier.com/help/create/basics/search-for-existing-data-in-zaps

For Step 3 shown in the screenshots it’s a Salesforce Find/Create Record.

My guess for the discrepancies is that in some cases it’s finding and returning an existing record and in other cases it’s not finding an existing record thus creating a new record.

The search results (DATA OUT) will include a field _zap_search_was_found_status that you can use in later steps of the Zap.

 

 

 

 

Hi Troy,

I think you might have solved the mystery. Thank you so much for shedding some light on this field and it’s usefulness.

Thank you!!!

 

Terms & Conditions