Best answer

Follow Up Boss error: “Got 400 calling POST https://api.followupboss.com/v1/events, expected 2xx.”

  • 22 June 2022
  • 7 replies
  • 568 views

I keep getting the error below when running this Zap. 

“Got 400 calling POST https://api.followupboss.com/v1/events, expected 2xx.”

I’m trying to connect new emails from gmail to Follow Up Boss Contacts. I am using the Zapier Email Parser to send the information through Zapier to my Follow Up Boss CRM to create new contacts.

I am getting the following error:

 

Any ideas?

icon

Best answer by jesse 28 June 2022, 23:34

View original

7 replies

Userlevel 7
Badge +14

Hi @mnchris 

Good question.

Please post screenshots with how your Zap steps are configured in order for us to have context, thanks.

This post has been edited by a moderator to remove personal information. Please remember that this is a public forum and to remove any sensitive information prior to posting.

 

 

Userlevel 7
Badge +14

@mnchris

This looks like an incorrectly mapped variable.

 

Looks like some values aren’t being properly parsed from the email template

You may want to consider using a more robust email parsing app such as Mailparser: https://zapier.com/apps/mailparser/integrations

 

 

Very interesting, since it is a very simple email to parse. If Zapier Parser can’t parse this email format, it is worthless to even offer it as an option.

Userlevel 7
Badge +14

@mnchris

The Zapier Email Parser is not the most robust and can depend on how it was configured/trained to do email parsing.

It’s a free option so take that as you may.

Userlevel 7
Badge +9

Hey @mnchris So sorry for the trouble here! I want to confirm that the issue you’re seeing is likely due to what Troy was mentioning:

 

@mnchris

This looks like an incorrectly mapped variable.

 

Troy is also correct in that if you’re needing a more robust parsing solution, something like Mailparser would be the way to go. However, if you have an email with a very simple and consistent format, then you’re right, the Email Parser should be able to handle this. Have you tried running through the steps in this article to see if that helps parse the correct data? Let us know!

Reply